PIAF 1.7.5.5 Networking issues

[DGrant303]

Hi -

I have been running Trixbox for many years now and have finally had enough! I really want to switch to PIAF and tried installing yesterday but had problems. Ended up re-installing Trixbox but really, really want to move to PIAF permanently!

The install went great and everything seemed good. The first thing I did was update and install modules under Module admin. I noticed the download and install process took a very long time - much longer than Trixbox.

Then after testing the system, I noticed the networking kept disconnecting every couple of minutes and my PIAF was not connected any longer. After a couple of minutes, it would come back.

I set up netconfig as static IP. I have subnet set correctly and default gateway and nameserver set correctly. I tried a couple of different settings in nameserver. First, I used my router's IP address and then switched it to my ISP's DNS1. Neither showed any signs of improvement.

I installed the patches and fixes but nothing seemed to help.

I've been running Trixbox for many years in this same networking environment and never had a day of problems.

Anyone every heard of this or have any suggestions??

Any help would be greatly appreciated.

David

 

[The Deacon]

Have you looked in your /var/log/message log to see if your NIC is flapping or you're having any other network related issues?

Another thing to check is that when your box loses connectivity, do you still have a link light on the back of the NIC? Have you tried replacing the cable?

It's weirdly funny that when you went back to do the Trixbox install that it worked...

 

[gzpxyj]

I would disable the default trunks in the system since it has wrong information on userid and password. I just installed the new piaf and has no problem. Also check the email for the root to see if there is anything wrong reported.

 

[wardmundy]

Try reinstalling and leave DHCP-assigned IP address in place. See if it works reliably then. That will tell us whether the static IP setup is the problem. Welcome!

 

[wb5psv]

I'm having a similar issue - had been using PIAF previously with 192.168.1.100, then upgraded to latest Silver version on my new Atom box. DHCP works fine. Static does not - seems to be the DNS..I'm using the very same settings I used before...and my router is all set-up for 192.168.1.100, so I'm trying to fix...will check out the log suggestion.

Fixed - I forgot to uncomment and re-install the correct local network IP in the /etc/asterisk/sip_custom.conf per these instructions...life is good again, my Netgear WPN824 is a pain to change settings

 

[blanchae]

Have you guys tried Webmin - Networking - Network Configuration to show what it is reporting? You can verify/configure your NIC settings, default gateway, host file and DNS server settings. This would be a good place to start.

 

[bobtimms]

I setup 2 systems - both have had problems setting a static ip. One a laptop following the Pbiaf setup instructions (laptop) has worked through reboots and shutdowns after some persistant netconfig setups. The other (desktop) will not retain the ip under idle - much less reboots and shutdowns - it seems to loose everything. Is there a file that I can verify that the correct entrys are being made - it kind of seems like it works initially but there is no record of the changes.

 

[DGrant303]

Bobtimms, this is the problem that I was having. When I assigned a static IP address to the box, it would flake out and loose connection about eveyr 10 or 15 seconds. Very unstable and I have since re-installed Trixbox for production purposes but would really like to make the switch to piaf but not under these circumstances.

 

[wardmundy]

This isn't voodoo. If you are determined not to use WebMin, then here are the places to look for problems...

/etc/resolv.conf - Stores your DNS servers. If you want to use Google's: 8.8.8.8 and 8.8.4.4. Otherwise, just enter the IP of your router/firewall:

nameserver 192.168.0.1

/etc/sysconfig/network-scripts/ifcfg-eth0 - Stores your eth0 setup and should look something like this:

DEVICE=eth0
ONBOOT=yes
BOOTPROTO=static
NETWORK=192.168.0.0
IPADDR=192.168.0.50
NETMASK=255.255.255.0
GATEWAY=192.168.0.1

/etc/sysconfig/network - Should look like this:

NETWORKING=yes
NETWORKING_IPV6=no
HOSTNAME=pbx.local

/etc/asterisk/sip_custom.conf - Stores your public IP address and your local subnet and should look something like this:

externip=193.70.244.123
localnet=192.168.0.0/255.255.255.0

service network restart - To restart your network


amportal restart - To restart Asterisk


If you have a second NIC, then use WebMin. Otherwise, the above will get you going assuming your network card is supported by CentOS 5.5 and is reliable.

If you need more help, click Search above and look for resolv.conf.

If you're unclear what your entries for any of the above should be, read some of these other threads.

If none of this makes any sense, stick with DHCP and make an entry in your firewall/router that tells it to reserve this dynamic IP address for your server using the MAC address of the network card. Type ifconfig and look for the MAC address in HWaddr under eth0. We always do this incidentally. And we do it for one simple reason... it's easy!

 

[blanchae]

The second nic is very similar to eth0's config:


/etc/sysconfig/network-scripts/ifcfg-eth1 - Stores your eth1 setup and should look something like this:

DEVICE=eth1
ONBOOT=yes
BOOTPROTO=static
NETWORK=192.168.1.0
IPADDR=192.168.1.51
NETMASK=255.255.255.0
GATEWAY=192.168.1.1

You can also add the broadcast statement in:

BROADCAST=192.168.1.255

 

[blanchae]

There is one more file to look at that sometimes adds the default gateway address that could be confusing things:

/etc/sysconfig/network <= this is a file not a directory

I still suggest using Webmin to configure your network at this point.