Hi all,
Right after boot i do:
# /sbin/ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:40:F4:6F:B4:90
inet addr:192.168.123.202 Bcast:192.168.123.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:5533 (5.4 Mb) TX bytes:1404 (1.3 Kb)
Interrupt:9 Base address:0x4000
it is set up to receive DHCP.
can't ping gateway (which has its route in output of "#/sbin/route -n")
then i do
# service network restart
Shutting down interface eth0: [ OK ]
Shutting down loopback interface: [ OK ]
Setting network parameters: [ OK ]
Bringing up loopback interface: [ OK ]
Bringing up interface eth0:
Determining IP information for eth0...PING 192.168.123.254 (192.168.123.254)
56(84) bytes for data.
...2 x 100% packet loss
failed [FAILED]
# /sbin/ifconfig eth0
gives the same output as above. except for one missing line
"inet addr:192.168.123.202 Bcast:192.168.123.255 Mask:255.255.255.0"
#/sbin/route -n
doesn't have a default route anymore
Any sugestions on how to get my network working?
Network setup works, windoze and MacOS are using systems use this setup.
Cheers,
Jeroen
> -----Original Message-----
> From: fedora-list-bounces@xxxxxxxxxx
> [mailto:fedora-list-bounces@xxxxxxxxxx] On Behalf Of Jeroen Tiebout
> Sent: Saturday, April 03, 2004 5:46 PM
> To: 'For users of Fedora Core releases'
> Subject: RE: Determining IP information for eth0 failed
>
> Hi Jeff, all,
>
> Thx for the reply, see text for comments,
>
> Cheers,
> Jeroen
>
> > >Hi Jeroen (lol), hi all,
> > >
> > >Fishy stuff.
> > >I have the same issue, similar config Core 1 on a Sony
> Vaio PCG-C1VE,
> > >xircom pcmcia eth adapter (lunix
> > >status: newbie)
> > >
> > >Tried adding the sujested lines in
> > >'/etc/sysconfig/network-scripts/ifcfg-eth0', issue stands
> > >
> > >
> > What did you add there?
> > The adapter is configured by DHCP so minimal information is used in
> > that file.
> -----------------------------------------------------
> I added (and deleted)
> check_link_down() {
> return 1;
> }
> in '/etc/sysconfig/network-scripts/ifcfg-eth0'
> -----------------------------------------------------
> >
> > >-------------------
> > >DHCP: i should get all info, ip, subnet, dns, and gateway.
> > >This works. The ip eth0 receives is from the pool gw, dns
> > and subnet are ok.
> > >The laptop even shows up in the dhcp client list of the
> (US robotics
> > >-cheapo, but working)router.
> > >In the dhcp client list the hostname shown for the laptop
> is: "25924
> > >8242:136" (Can i change this?)
> > >
> > >
> > Change that on the DHCP server end.
> -----------------------------------------------------
> Ok, thx
> -----------------------------------------------------
> >
> > >everything is looking great so far
> > >When i try to ping my gateway, i get "Destination host unreachable"
> > >*I think dhcp packets are sent using UDP, apparently that
> > works, could
> > >it be a problem with icmp or tcp?
> > >
> > >When i boot the laptop i get an error when it tries to
> > initialize the
> > >network interface.
> > >something like "xircom_cb eth0 not present, delaying
> initialisation"
> > >-I use a xircom pcmcia adater as i have no network on board.
> > >*During startup pcmcia is initialised after eth0 fails to
> initialise.
> > >
> > >
> > >
> > I have mentioned this before, and your line above says it.
> > The sequence of starting the services is at fault here.
> > Since pcmcia services are not by default started until after the
> > network is started you see this failure.
> > If you go into /etc/rcX.d and change the sequence of these services
> > starting the problem with failing to start the network will
> be fixed.
> -----------------------------------------------------
> nice,
> How do i know which X in rcX.d to change (1 or 4 or 5 or
> doesnt it matter?) Do i change sequence just by renaming files:
> K90network -> K96network
> K96pcmcia -> K90network?
> -----------------------------------------------------
> >
> > As far as the ping failing, have you verified the eth0 adapter is
> > initialized and running.?
> > "serivce network restart" as root will handle that usually if not
> > already up.
> >
> -----------------------------------------------------
> The GUI said it is active... (?) how can i be sure?
> 'service network restart' fails on bringing up eth0... so i
> guess thats my problem
> -----------------------------------------------------
> > >thats one to chew on, i have been anyhow.
> > >
> > >Cheers,
> > >Jeroen
