Network Port Issue...

[womble1]

Here is an odd one...
At boot time only one network port is activated.
The other is disabled..
Indeed in ifconfig (on a terminal session) you can only see eth1 and the loop back interfaces.
In webmin you can only see the two...
and yet asterisk (FReepbx) see's eth1 and applies the g729 codec licenses to that interface...
so they don't work....
Great...
Anyone know how to delete an interface that is deleted ?
I tried to recreate it in webmin, but it say's the interface does not exist...
Great...

 

[Bitnetix]

Can you output the results of this command, please:

find /etc/sysconfig/network-scripts/ifcfg* -ls -exec cat {} \;

And then go read http://downloads.digium.com/pub/telephony/codec_g729/README and see the General Notes section to see if any of these notes apply to you.

 

[womble1]

Odd it's not enabled at boot time…

51250001 4 -rw-r--r-- 2 root root 195 Nov 15 2009 /etc/sysconfig/network-scripts/ifcfg-eth1
BOOTPROTO=none
NAME=""
GATEWAY=192.168.100.1
HWADDR=00:06:4F:68:5A:E7
DEVICE=eth1
NETMASK=255.255.255.0
MTU=1500
BROADCAST=255.255.255.255
IPADDR=192.168.100.108
NETWORK=192.168.100.0
ONBOOT=yes
51250181 4 -rw-r--r-- 2 root root 117 Jun 29 10:06 /etc/sysconfig/network-scripts/ifcfg-etho
NAME=""
BOOTPROTO=none
DEVICE=etho
NETMASK=0.0.0.0
MTU=""
BROADCAST=0.0.0.0
IPADDR=0.0.0.0
NETWORK=0.0.0.0
ONBOOT=no
51249999 4 -rw-r--r-- 2 root root 136 Nov 15 2009 /etc/sysconfig/network-scripts/ifcfg-lo
BOOTPROTO=none
NAME=loopback
DEVICE=lo
NETMASK=255.0.0.0
MTU=""
BROADCAST=127.255.255.255
IPADDR=127.0.0.1
NETWORK=127.0.0.0
ONBOOT=yes

 

[Bitnetix]

It's not enabled because the file is called ifcfg-etho instead of ifcfg-eth0 (note the "oh" instead of a "zero"). So if you want it on, you need to rename the file. If you want it off, delete it, and then reregister your g729 license.

 

[womble1]

OK Deleted that but you can see in PBX …
eth0

 

[Bitnetix]

What happens when you type "ifconfig eth1"? Does it show up? If so, then your kernel thinks that it exists. You'll have to get rid of it from your modules, then.

Check out cat /etc/modules.conf and see if you have an alias for eth0 and eth1. If you have an eth1 alias, then remove that line from the modules.conf file and reboot. If not, then something else is going on.