Hi There,
Network with W9X clients?.... If yes adjust the allowed frame types on
the W9X clients, it tries to do more than one.
Kees
On Thu, 20 Apr 2000, Chris Pimlott wrote:
> I have a FORE PCA200E ATM card. We use LAN Emulation, so my
> interface device (after atmsigd, ilmid and zeppelin are started) is
> lec0. When I have only tcp/ip networking going, ifconfig looks like this:
>
> lec0 Link encap:Ethernet HWaddr 00:20:48:08:C7:9B
> inet addr:129.22.238.211 Bcast:129.22.255.255 Mask:255.255.0.0
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:77 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3904 Metric:1
> RX packets:66 errors:0 dropped:0 overruns:0 frame:0
> TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
>
> When ipx_configure --auto_interface=on is set, and I ifconfig lec0
> for tcp/ip, I start getting a lot of these messages:
>
> Apr 20 14:38:35 moebius kernel: IPX: Network number collision ca008137
> Apr 20 14:38:35 moebius kernel: lec0 EtherII and lec0 802.3
> Apr 20 14:38:35 moebius kernel: IPX: Network number collision ca008137
> Apr 20 14:38:35 moebius kernel: lec0 EtherII and lec0 802.2
> Apr 20 14:38:35 moebius kernel: IPX: Network number collision ca008137
> Apr 20 14:38:35 moebius kernel: lec0 EtherII and lec0 SNAP
>
> over and over. ifconfig looks like this:
>
> lec0 Link encap:Ethernet HWaddr 00:20:48:08:C7:9B
> inet addr:129.22.238.211 Bcast:129.22.255.255 Mask:255.255.0.0
> IPX/Ethernet II addr:CA008137:00204808C79B
> IPX/Ethernet SNAP addr:00204808C79B
> IPX/Ethernet 802.2 addr:00204808C79B
> IPX/Ethernet 802.3 addr:00204808C79B
> UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
> RX packets:236 errors:0 dropped:0 overruns:0 frame:0
> TX packets:1 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:100
>
> lo Link encap:Local Loopback
> inet addr:127.0.0.1 Mask:255.0.0.0
> UP LOOPBACK RUNNING MTU:3904 Metric:1
> RX packets:66 errors:0 dropped:0 overruns:0 frame:0
> TX packets:66 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:0
>
> After a variable amount of time like this, with the network number
> collision errors, my machine will "crash". It becomes unresponsive at the
> keyboard and mouse, and I cannot switch virtual consoles nor to or from X
> Windows. If I am at console at the time, I see a very fast stream of
> gibberish (as if cat'ing a binary). /var/log/messages from this time also
> contains gibberish with no unusual message before this other than the
> repeated Network number collision errors. I have experienced this in both
> 2.2.14 (with ATM patch 0.59) and 2.3.99-pre5 (with ATM patch 0.76).
>
> I realize setting ipx_configure --auto_interface=on will stop the
> IPX interfaces from being automatically being created on ifconfig, and
> subsequently get rid of the problem, but somehow I don't the crash was
> intended. Additional information is, of course, available on demand.
>
> Chris Pimlott
>
> Linux moebius.student.cwru.edu 2.3.99-pre5 #1 Sun Apr 16 23:36:26 EDT 2000
> i686 unknown
> Kernel modules 2.3.10
> Gnu C 2.95.2
> Binutils 2.9.5.0.31
> Linux C Library 2.1.3
> Dynamic linker ldd: version 1.9.11
> Procps .
> Mount 2.10f
> Net-tools 2.05
> Kbd command
> Sh-utils 2.0g
> Modules Loaded soundcore ipx af_packet sd_mod nls_iso8859-1
> nls_cp437 vfat fat serial isa-pnp lec fore_200e ide-scsi scsi_mod
>
>
> -
> To unsubscribe from this list: send the line "unsubscribe linux-net" in
> the body of a message to [EMAIL PROTECTED]
>
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
