FC3 new install...network problems

[Cr0n_J0b]

I'm in a very bad way. I'm on my 4th install of FC3 with no end in sight.

The latest problem is with my network. I have 3 interfaces, eth0(internet), eth1 and eth2 (both on internal network). Everything was fine, then i ran yum and updated all of my packages. I have almost everything installed on this system. After the update, the ip address from eth1 moved to eth2, and eth0 and eth1 went inactive.

I thought..easy...I went into the gnome sysconfig for networking and activated the cards, and straightened out the addresses...saved...saved again...closed...opened the network config again, verified that everything stuck...and finally checked ifconfig. all the interfaces were fine.

I then rebooted...

when the system came back up, everything went back to being messed up. Eth0 offline, eth1 offline and eth2 setup with the wrong address.

I've had this type of network problem with RH for years...like 5 years. with one config tool not working with another etc. along the way I never learned the manual approach to setting up the ip settings. I should have...

I tried setting things up with IPCONFIG but nothing sticks.

any help would be appreciated.

thanks

[Cr0n_J0b]

So, I just finished my last painful reinstall and...it turns out that the problem comes from the first RedHat update. I just installed FC3 fresh...ran the updates and I have the same problems again. eth0 and eth1 no longer show up in ifconfig...the address from eth1 moved to eth2.

the strange part is that I can still access the internet...which is on eth0.

here is ifconfig and route.


eth0 Link encap:Ethernet HWaddr 00:0A:E6:E9C:B5
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16217 errors:0 dropped:0 overruns:0 frame:0
TX packets:76 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:994114 (970.8 KiB) TX bytes:8489 (8.2 KiB)
Interrupt:10 Base address:0x2c00

eth1 Link encap:Ethernet HWaddr 00:40:F4:A8:75:95
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:88 errors:0 dropped:0 overruns:0 frame:0
TX packets:52 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:14227 (13.8 KiB) TX bytes:5588 (5.4 KiB)
Interrupt:11 Base address:0x2e00

eth2 Link encap:Ethernet HWaddr 000:F0:30:0E:A6
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:117 errors:1 dropped:0 overruns:0 frame:0
TX packets:125 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12976 (12.6 KiB) TX bytes:16512 (16.1 KiB)
Interrupt:10 Base address:0x4f80

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2149 errors:0 dropped:0 overruns:0 frame:0
TX packets:2149 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:2684776 (2.5 MiB) TX bytes:2684776 (2.5 MiB)

route:


Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 0 0 0 eth2
default 192.168.1.211 0.0.0.0 UG 0 0 0 eth2


As you can see, eth1 and eth0 are gone....at least from the route.

Can anyone tell me how to manually reconnect my addresses and activate the interfaces.

[strikeforce]

Have a look under /etc/sysconfig/network-scripts/

You will find the following or should find the following files these are the ones that should be altered because on a reboot it'll stick.

ifcfg-eth0
ifcfg-lo
These are the network scripts files that get called at bootup just edit them and post if you still have problems.

[Cr0n_J0b]

I can fix the problem by going into the gui network tools. I think they are sysconfig-network-gui or something like that...I pulled them from the GUI menu. anyway, I fix it, and the check the etc/sysconfig/network-scripts/ifcfg-eth0 etc... and they show fine...I can run ifconfig and everything looks fine...then after the reboot they go right back to being messed up!

I can't tell you how frustrating this is!!

[strikeforce]

post your ifcfg file here maybe its something in that. I've never had that issue before so I have no idea.

[Cr0n_J0b]

I've reloaded the OS again...this is like number 5. My plan is to load only the most critical patches...one at a time....and find out which one is causing the problem.

I'm loading the new kernel update now, so ...only 143 to go.

i'll post the ifcfg files when this finishes

thanks

[natbrazil]

hi
sounds like i have a similar problem, just installed fc3, went fine, activated my one nic card and got on net just fine, but upon reboot it doesn't reconnect to internet. this will be important as it'll be a remote server rebooted remotely, LOL! I checked the network setup and it IS set to activate upon reboot.

I have one nic, one network device named eth0:1 and it is set to activate when computer starts, but it doesn't. When I manually activate it, my net connection is fine.

How do I troubleshoot this to determine why it doesn't activate upon reboot?

Here is my ifconfig info, before and after manual activation

[root@localhost ~]# ifconfig
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2620 errors:0 dropped:0 overruns:0 frame:0
TX packets:2620 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3039384 (2.8 MiB) TX bytes:3039384 (2.8 MiB)

[root@localhost ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:BA:B0:0C:60
inet6 addr: fe80::250:baff:feb0:c60/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:120 (120.0 b) TX bytes:2931 (2.8 KiB)
Interrupt:193 Base address:0x2000

eth0:1 Link encap:Ethernet HWaddr 00:50:BA:B0:0C:60
inet addr:216.153.214.234 Bcast:216.153.214.255 Mask:255.255.255.192 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:193 Base address:0x2000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2620 errors:0 dropped:0 overruns:0 frame:0
TX packets:2620 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3039384 (2.8 MiB) TX bytes:3039384 (2.8 MiB)


Thx all

[strikeforce]

Check what is running at startup. It might be that you have to do what I had to do which is create your own firewall script so that you can 'force' it to start up. I still havent' found a solution to this the only way I've fixed it is to run my firewall script at startup its a wierd bug because all the decisions and tools I've used don't seem to help.

I'm not sure what I've done to cause it as well but sof far noone I know has solved this.