Kevin Old wrote:
On Wed, 10 Nov 2004 13:58:07 +0100, Alexander Apprichsomehow i fixed it. i don't know how but i reinstalled the card, set it to use dhcp etc at least 10 times last night with no luck, booted fc3 today and now its working like a charm. weird.... i can't explain what caused it.
<a.apprich@xxxxxxxxxxxxxxxxxxxx> wrote:
Kevin Old wrote:
On Wed, 10 Nov 2004 11:15:52 +0100, Alexander Apprich <a.apprich@xxxxxxxxxxxxxxxxxxxx> wrote:
Can you elaborate on "using dhclient"? I'm having the same problem asketil hage wrote:
Have you tried using dhclient when eth0 was up?updated from fc2 to fc3 from cd's.
had some serious boot trouble after restart, but disable the nvidia module fixed that.
now i can't get eth0 to work.
(i had firestarter installed before upgrade).
here's what i found: When i set ip manually, the eth0 card get active, but nothing works, can't ping my gateway or anything else. it doesn't matter if firestarter is started or stopped. with ifconfig i see the right addresses configured.
when i try to use dhcp(i have a dhcp server)the card just get inactive.
it seems that there is something in my box blocking all contact to the lan.
Ketil with trying to connect to a network.
Just execute dhclient, and if eth0 is up and a dhcp server is availible eth0 get its network config assigned. Older RedHats < 8 used to have pump which did allmost the same.
If dhclient doesn't work it's probably because a firewall is blocking
DHCP.
Ok, it must be the firewall, but I have it disabled. I've verified this by the "/sbin/service iptables status" which reports "Firewall is stopped".
Under "Security" (in the Gnome menu, not sure where) it shows that the firewall is disabled and SELinux is disabled.
brrrrr my box is haunted ;)
kh
