[CentOS] Problems with D-Link DGE-530T and skge module on Centos 4.3

Wed Sep 6 20:59:59 UTC 2006
David Nalley <davidn at KeyMarkinc.com>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1


I am running Centos 4.3 with the 2.6.9-42.EL.jwltest.156 kernel (to get
the skge module) 
The card is recognized, and I can see traffic when I utlilize wireshark
in promiscuous mode including attempts at responding to ARP requests.

  9.608260 DellPcba_b8:d7:63 -> Broadcast    ARP Who has 172.20.15.25?
Tell 172.20.15.27
  9.608281 D-Link_87:55:06 -> DellPcba_b8:d7:63 ARP 172.20.15.25 is at
00:15:e9:87:55:06

However, no icmp traffic passes, and the pinging host acts as if it
can't find the address. Even after supposedly responding to the ARP
traffic it still shows no TX packets. 



      ifconfig output:
      eth2      Link encap:Ethernet  HWaddr 00:15:E9:87:55:06
                inet addr:172.20.15.25  Bcast:172.20.15.255
Mask:255.255.255.0
                inet6 addr: fe80::215:e9ff:fe87:5506/64 Scope:Link
                UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
                RX packets:520 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:50348 (49.1 KiB)  TX bytes:0 (0.0 b)
                Interrupt:11
       
      dmesg | grep eth2 output:
      skge eth2: enabling interface
      skge eth2: Link is up at 1000 Mbps, full duplex, flow control none
      eth2: no IPv6 routers present
      device eth2 entered promiscuous mode
      device eth2 left promiscuous mode
      (promiscuous mode is a result of using tshark)



      [root at jupiter2 ~]# route
      Kernel IP routing table
      Destination     Gateway         Genmask         Flags Metric Ref
Use Iface
      68.XXX.XXX.0    *               255.255.255.128 U     0      0
0 eth0
      172.20.15.0     *               255.255.255.0   U     0      0
0 eth2
      default         68.XXX.XXX.XXX  0.0.0.0         UG    0      0
0 eth0 


Any suggestions welcome. 

Thanks,

David Nalley
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (MingW32)

iD8DBQFE/zY/U7rV35qFz0QRAhp9AJsGpASubdklwHnAmL5YbJHB+OJCcgCgl3Kp
c1/3G1krkmtr47uoNytp5Qo=
=PF4g
-----END PGP SIGNATURE-----