Subject: Re: TCP / IP stack bug ??
From: nathan r. hruby (nhruby@arches.uga.edu)
Date: Tue Nov 20 2001 - 14:45:48 MST
On Tue, 20 Nov 2001, Ken Schweigert wrote:
> Laurent,
>
> I had a similar problem with a Dual-500 and YDL1.2, although I'm not
> sure if it was the same PHYID as this. Someone on this list advised
> me to try one of the, then beta, kernels by Ben H. It worked
> perfectly for me. I would recommend downloading one of the latest
> kernels and give that a shot. You could also try installing the
> kernel source, building the gigabit interface options as modules,
> and trying one of those. There are only four options, so it shouldn't
> take too long to find one that might work.
>
I think that the GigE interface isn't yet supported? I think that I read
this on the YDL site. Try setting the media type to 100..
-n
> HTH
>
> --
> -Ken Schweigert
> OSX Haiku:
>
> handfull of your hair
> just upgraded your os?
> must be OSX.
>
>
>
> On Tue, Nov 20, 2001 at 06:21:15PM +0100, Laurent Crinon wrote:
> > Hello,
> >
> > I just installed ydl2.0 on a itanium powerbookG4,
> > built-in network adapter is reported as
> > ---
> > eth0 PHY ID: 0x004061e3
> > eth0: Warning ! Unknown PHY ID 0x004061e3 !
> > Link state change, phy_status: 0x782d
> > full_duplex: 0, speed: 10
> > ---
> >
> > and kernel is:
> > Linux toto 2.2.19-1i #1 Mon May 14 18:42:16 MDT 2001 ppc unknown
> >
> > ifconfig reports the nice paragraph:
> > eth0 Link encap:Ethernet HWaddr 00:03:93:01:DB:80
> > inet addr:172.27.0.45 Bcast:172.27.63.255 Mask:255.255.192.0
> > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> > RX packets:1810 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:1848 errors:0 dropped:0 overruns:0 carrier:0
> > collisions:0 txqueuelen:100
> > Interrupt:41
> >
> > route -n reports:
> > Kernel IP routing table
> > Destination Gateway Genmask Flags Metric Ref Use
> > Iface
> > 172.27.0.0 0.0.0.0 255.255.192.0 U 0 0 0 eth0
> > 0.0.0.0 172.27.3.4 0.0.0.0 UG 0 0 0 eth0
> >
> > there is no ipchains entries:
> > [root@localhost /root]# ipchains -L
> > Chain input (policy ACCEPT):
> > Chain forward (policy ACCEPT):
> > Chain output (policy ACCEPT):
> >
> > if I ping inside my lan it's ok:
> > [root@localhost /root]# ping -n 172.27.0.8
> > PING 172.27.0.8 (172.27.0.8) from 172.27.0.45 : 56(84) bytes of data.
> > 64 bytes from 172.27.0.8: icmp_seq=0 ttl=128 time=225 usec
> > 64 bytes from 172.27.0.8: icmp_seq=1 ttl=128 time=166 usec
> >
> > if I ping outside my lan (my lan is behind a very simple masquerading
> > gateway that never caused any trouble to any machine apart this linuxppc)
> > [root@localhost /root]# ping -n 137.194.2.16
> > PING 137.194.2.16 (137.194.2.16) from 0.0.0.0 : 56(84) bytes of data.
> >
> > --- 137.194.2.16 ping statistics ---
> > 15 packets transmitted, 0 packets received, 100% packet loss
> >
> > there is 100% packet loss and notice the ``from address'' is 0.0.0.0
> > !!!!
> >
> > And if I try
> > [root@localhost /root]# traceroute -n 137.194.2.16
> > traceroute to 137.194.2.16 (137.194.2.16), 30 hops max, 38 byte packets
> > 1 172.27.3.4 0.424 ms 0.126 ms 0.120 ms
> > 2 * * * 0.787 ms 0.769 ms 0.776 ms
> > ...
> >
> > The traceroute runs properly.
> >
> > Is this a bug in the TCP/IP stack of linuxppc (version 2.2.19-1i) or
> > is the built-in ethernet adapter no very well supported?
> >
> > Laurent Crinon
>
-- ...... nathan hruby - nhruby@arches.uga.edu computer support specialist department of drama and theatre http://www.drama.uga.edu/ ......
This archive was generated by hypermail 2a24 : Tue Nov 20 2001 - 14:59:01 MST