ts-7000
[Top] [All Lists]

[ts-7000] TS-ETH2 problem

To:
Subject: [ts-7000] TS-ETH2 problem
From: "Rekcut_Nod" <>
Date: Wed, 09 Feb 2011 22:54:11 -0000
I am having problems with the TS-ETH2 board.  At boot-up, I load
the drivers for the board, and that seems to work fine:

modprobe -o ts-eth2-1 ax88796b iobase=0x11e00000 mem=0x300 irq=40
AX88796B: MAC ADDRESS  00 d0 69 43 36 ea
eth1: AX88796B found at 0x300, using IRQ 40.
modprobe -o ts-eth2-2 ax88796b iobase=0x11e00000 mem=0x340 irq=40
AX88796B: MAC ADDRESS  00 d0 69 43 36 eb
eth2: AX88796B found at 0x340, using IRQ 40.

But, when I attempt to ping another computer using a cross-over cable from one 
of the ports of the card it doesn't work.  To verify that there is nothing 
wrong with the cable, routing table, or interface configuration, I attempted to 
do the exact same thing with eth0 from the main board, and it works fine.  Here 
is my procedure:

[1] Bring up eth0 with a local IP address
ts7000:~# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:d0:69:43:39:b8
          inet addr:192.168.0.10  Bcast:192.168.0.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:571 errors:0 dropped:0 overruns:0 frame:0
          TX packets:5 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:81137 (79.2 KiB)  TX bytes:1151 (1.1 KiB)
[2] Inspect the route
ts7000:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref Use Iface
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0   0 eth0
[3] Connect to another machine on the same subnet with a cross-over cable
[4] test the connection
ts7000:~# ping 192.168.0.9
PING 192.168.0.9 (192.168.0.9) 56(84) bytes of data.
64 bytes from 192.168.0.9: icmp_seq=1 ttl=64 time=3.37 ms
64 bytes from 192.168.0.9: icmp_seq=2 ttl=64 time=0.773 ms
64 bytes from 192.168.0.9: icmp_seq=3 ttl=64 time=0.433 ms
[5] Now, bring eth0 down and bring eth1 up instead with the same address
ts7000:~# ifconfig eth1 192.168.0.10 netmask 255.255.255.0 up
AX88796B: The media mode is autosense.
ts7000:~# ifconfig
eth1      Link encap:Ethernet  HWaddr 00:d0:69:43:36:ea
          inet addr:192.168.0.10  Bcast:192.168.0.255  Mask:255.255.255.0
          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:40 Base address:0x300
[6] Inspect the route
ts7000:~# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref Use Iface
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0   0 eth1
[7] Connect to another machine on the same subnet with a cross-over cable
ts7000:~# eth1 Link mode : 100 Mb/s  Duplex mode.
error occurred! Drop this packet!!
error occurred! Drop this packet!!
[8] Test the connection
ts7000:~# ping 192.168.0.9
PING 192.168.0.9 (192.168.0.9) 56(84) bytes of data.
>From 192.168.0.10 icmp_seq=1 Destination Host Unreachable
>From 192.168.0.10 icmp_seq=2 Destination Host Unreachable
>From 192.168.0.10 icmp_seq=3 Destination Host Unreachable

I have no firewall set:
ts7000:~# iptables -L
ip_tables: (C) 2000-2006 Netfilter Core Team
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

The only difference seems to be that when the TS-ETH2 interface is brought up 
there is this message, "AX88796B: The media mode is autosense.", which does not 
appear when eth0 is brought up on the main board.  Also, when the port on the 
TS-ETH2 is connected to the other machine on the sub-net, it gives the message, 
"Link mode : 100 Mb/s  Duplex mode.  error occurred! Drop this packet!!".  I 
suspect these two messages are related (i.e. the port waits to see if it should 
be 100Mb/s or 10Mb/s, full or half, and then decides when connected), but I 
don't know what the error is all about.  I looked at the driver source 
(ax88796b.c) for that error, and there is a comment:
/*Check for bogosity warned by 3c503 book: the status byte is never
written.  This happened a lot during testing! This code should be cleaned up 
someday.*/

Has anyone else experienced this problem and possibly found a work-around?

Thanks,
Don




------------------------------------

Yahoo! Groups Links

<*> To visit your group on the web, go to:
    http://groups.yahoo.com/group/ts-7000/

<*> Your email settings:
    Individual Email | Traditional

<*> To change settings online go to:
    http://groups.yahoo.com/group/ts-7000/join
    (Yahoo! ID required)

<*> To change settings via email:
     
    

<*> To unsubscribe from this group, send an email to:
    

<*> Your use of Yahoo! Groups is subject to:
    http://docs.yahoo.com/info/terms/

<Prev in Thread] Current Thread [Next in Thread>
  • [ts-7000] TS-ETH2 problem, Rekcut_Nod <=
Admin

Disclaimer: Neither Andrew Taylor nor the University of NSW School of Computer and Engineering take any responsibility for the contents of this archive. It is purely a compilation of material sent by many people to the birding-aus mailing list. It has not been checked for accuracy nor its content verified in any way. If you wish to get material removed from the archive or have other queries about the archive e-mail Andrew Taylor at this address: andrewt@cse.unsw.EDU.AU