PIONEERS Living the Ubuntu Dream

[Jay Deal]

One of the arrows got too close to the wagon and I chickened out........

Seriously, I actually went back to Centos 6.5 (which works very nicely on the D610, thank you). Biggest issue, Avantfax is hopelessly stuck in 2010 and as I tried to load HylaFax/AvantFax into Ubuntu 14.04 it (AvantFax) didn't make it 5 seconds before the first few dependencies wouldn't load. While HylaFax did appear to load successfully, the Avantfax shell/interface is mandatory for me (at least) - looks like that will have to be missing from future IncredibilePBX builds unless someone decides to update Avantfax or at least the script that builds it.

 

[BeerCan]

Got mine working for the most part. Ram and disk amounts do not show up on the status screen. I don't think that affects call quality

 

[wardmundy]

Once the dust settles, I'll work on a more rational way to display this stuff without actually counting spaces.

 

[jeff.h]

I got so wrapped up in the other builds I never got back to this one. I'll spin up a droplet and start using it for my personal system.

 

[jeff.h]

Which iptables file do I need to edit to allow my remote connections? /etc/iptables/rules.v4 or rules.v4.ubuntu14 or both?

 

[wardmundy]

rules.v4

 

[jeff.h]

Ok thanks. Is there a TM3 for Ubuntu and I missed it? The regular TM3 gives errors about the target file it needs to modify.

 

[wardmundy]

It's already baked in.

 

[jeff.h]

Hmmmm ok, can I just ignore this then?

The following services have been enabled for name.domain.net:
ALL Services
sed: can't read /etc/sysconfig/iptables: No such file or directory
If there's an error in enabled services, run del-acct and try again.
* Loading iptables rules... [ OK ] * IPv6...
sed: can't read /etc/sysconfig/iptables: No such file or directory
No IPtables problems found.

 

[wardmundy]

jeff.h Shouldn't be doing that. Try: service iptables restart. If that doesn't do it, try: /etc/init.d/iptables restart

 

[wardmundy]

jeff.h: Went back and took a look at the Ubuntu build. The iptables-restart piece was not finished, but I'll get it this week. If you're getting those errors running add-ip or del-acct, then it sound like you may have overwritten the Ubuntu stuff with the CentOS stuff in Incredible PBX 3. I'll get you a fresh copy in a day or two. We're headed out of town at the moment.

 

[jeff.h]

OK sounds good. I had just spun up a new droplet and used the instructions from here http://nerdvittles.com/?p=9713 so I am not sure what happened. Have fun on your trip!

 

[wardmundy]

jeff.h: OK. Here are the missing pieces. Just copy the attached tarball into /root and issue the following commands. Then reboot. After that, use iptables-restart whenever you make a change to the iptables setup, and it will check for and fix any detected errors. Let me know if it smokes.

cd /root
tar zxvf iptables-ubuntu.tar.gz
rm -f iptables-ubuntu.tar.gz
mv iptables-restart /usr/local/sbin
# comment next two lines if you've previously run this install
sed -i 's|exit 0|/usr/local/sbin/iptables-restart\nexit 0|' /etc/rc.local
sed -i 's|exit 0"|#exit 0"|' /etc/rc.local
echo "*/10 5-22 * * * root /root/ipchecker > /dev/null 2>&1" >> /etc/crontab

 

[jroper]

Hi

I'm not sure for Ubuntu 14, but for 12.04, rc.local is not executable by default, you may want to check this.

Joe

 

[wardmundy]

Hi

I'm not sure for Ubuntu 14, but for 12.04, rc.local is not executable by default, you may want to check this.

Joe

Thanks, Joe. Works in 14, but I'll need to figure it out for the Raspberry Pi and BeagleBone Black: sysv-rc-conf

 

[jeff.h]

jeff.h: OK. Here are the missing pieces. Just copy the attached tarball into /root and issue the following commands. Then reboot. After that, use iptables-restart whenever you make a change to the iptables setup, and it will check for and fix any detected errors. Let me know if it smokes.

cd /root
tar zxvf iptables-ubuntu.tar.gz
rm -f iptables-ubuntu.tar.gz
mv iptables-restart /usr/local/sbin
sed -i 's|exit 0|/usr/local/sbin/iptables-restart\nexit 0|' /etc/rc.local
sed -i 's|exit 0"|#exit 0"|' /etc/rc.local

OK tried that ./add-fqdn still does not work, but ./add-ip does.

-bash: ./add-fqdn: No such file or directory

Oh and it doesn't create an ipchecker file either

 

[wardmundy]

Wanted to get the kinks out first. Will add ipchecker and add-fqdn later today.

To test what you have add an IP address with add-ip. Then find it in /etc/iptables/rules.v4 and change the IP address to something like myfakefqdn.incrediblepbx.com. Then: iptables-restart. What it should do is highlight the error with the line number, comment out the rule, and then restart IPtables without the offending rule.

 

[jeff.h]

Wanted to get the kinks out first. Will add ipchecker and add-fqdn later today.

To test what you have add an IP address with add-ip. Then find it in /etc/iptables/rules.v4 and change the IP address to something like myfakefqdn.incrediblepbx.com. Then: iptables-restart. What it should do is highlight the error with the line number, comment out the rule, and then restart IPtables without the offending rule.

******** 10-SECOND WARNING ALERT ***********
IPtables FQDN problem on line: 136
The unresolvable FQDN is `myfakefqdn.incrediblepbx.com.
This rule will be temporarily disabled to allow IPtables to start.
Check and correct line 136 in /etc/iptables/rules.v4.
******** 10-SECOND WARNING ALERT ***********

* Loading iptables rules...
* IPv4...
* IPv6...
[ OK ]
IPtables problems noted above were temporarily fixed.
Fix the problems identified in /etc/iptables/rules.v4
IPtables now running without the offending rules(s).
root@ubuntu:/etc/iptables#

 

[wardmundy]

jeff.h: If iptables -nL and status both show everything working after iptables-restart, then we have liftoff.

 

[jeff.h]

Heh.... would love to test, but DO appears to be down right now. I can't login to my account. Will test as soon as its back up.