I'm putting all wires on the same swirch for testing.
eth0 is a sis embedded card (good one).
dealing with dhcp I see that request arrives to the board but the offers never
appears on client. system clean no iptables rules, just dhcpd.
00:04.0 Ethernet controller: Silicon Integrated Systems [SiS] SiS900 PCI Fast
Ethernet (rev 91)
00:09.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
compatible 10/100 Ethernet (rev 40)
00:0a.0 Ethernet controller: Davicom Semiconductor, Inc. 21x4x DEC-Tulip
compatible 10/100 Ethernet (rev 40)
uLinuxIV ~ # ifconfig eth0 192.168.3.1
uLinuxIV ~ # ping -c 1 192.168.3.3
PING 192.168.3.3 (192.168.3.3) 56(84) bytes of data.
64 bytes from 192.168.3.3: icmp_seq=1 ttl=64 time=1.14 ms
--- 192.168.3.3 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 1.141/1.141/1.141/0.000 ms
uLinuxIV ~ # ifconfig eth0 down
uLinuxIV ~ # modprobe tulip
uLinuxIV ~ # dmesg | tail -n 10
Linux Tulip driver version 1.1.15 (Feb 27, 2007)
tulip0: MII transceiver #1 config 1000 status 782d advertising 01e1.
eth1: Davicom DM9102/DM9102A rev 64 at Port 0xe400, 00:60:6e:70:1f:b1, IRQ 17.
tulip1: MII transceiver #1 config 1000 status 782d advertising 01e1.
eth2: Davicom DM9102/DM9102A rev 64 at Port 0xe800, 00:60:6e:70:1f:d5, IRQ 18.
uLinuxIV ~ # ifconfig eth1 192.168.3.1
uLinuxIV ~ # ping -c 1 192.168.3.3
PING 192.168.3.3 (192.168.3.3) 56(84) bytes of data.
Aborted
uLinuxIV ~ # ifconfig eth1 down
uLinuxIV ~ # ifconfig eth2 192.168.3.1
uLinuxIV ~ # ping -c 1 192.168.3.3
PING 192.168.3.3 (192.168.3.3) 56(84) bytes of data.
Aborted
uLinuxIV ~ #
I'm gonna try with rc7-git4 and 2.6.24
--
Gustavo Guillermo P?rez
Compunauta uLinux
http://www.compunauta.com
Gustavo Guillermo P?rez wrote:
> I'm putting all wires on the same swirch for testing.
> eth0 is a sis embedded card (good one).
> dealing with dhcp I see that request arrives to the board but the offers never
> appears on client. system clean no iptables rules, just dhcpd.
> I'm gonna try with rc7-git4 and 2.6.24
Please do.
Also, try the 'dmfe' driver, as it was written specifically for these chips.
Jeff
El Viernes, 28 de Marzo de 2008, escribi?:
> Gustavo Guillermo P?rez wrote:
> > I'm putting all wires on the same swirch for testing.
> > eth0 is a sis embedded card (good one).
> > dealing with dhcp I see that request arrives to the board but the offers
> > never appears on client. system clean no iptables rules, just dhcpd.
> >
> > I'm gonna try with rc7-git4 and 2.6.24
>
> Please do.
>
> Also, try the 'dmfe' driver, as it was written specifically for these
> chips.
So, with dmfe driver went fine [rc7-g4] same with tulip nothing
uLinuxIV ~ # rmmod tulip
uLinuxIV ~ # modprobe dmfe
uLinuxIV ~ # dmesg | tail -n 3
dmfe: Davicom DM9xxx net driver, version 1.36.4 (2002-01-17)
eth1: Davicom DM9102 at pci0000:00:09.0, 00:60:6e:70:1f:b1, irq 17.
eth2: Davicom DM9102 at pci0000:00:0a.0, 00:60:6e:70:1f:d5, irq 18.
uLinuxIV ~ # ifconfig eth0 192.168.1.1
uLinuxIV ~ # ping -c 1 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.176 ms
--- 192.168.1.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.176/0.176/0.176/0.000 ms
uLinuxIV ~ # ifconfig eth0 down
uLinuxIV ~ # ifconfig eth1 192.168.1.1
uLinuxIV ~ # ping -c 1 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.176 ms
--- 192.168.1.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.176/0.176/0.176/0.000 ms
uLinuxIV ~ # ifconfig eth1 down
uLinuxIV ~ # ifconfig eth2 192.168.1.1
uLinuxIV ~ # ping -c 1 192.168.1.2
PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data.
64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.176 ms
--- 192.168.1.2 ping statistics ---
1 packets transmitted, 1 received, 0% packet loss, time 0ms
rtt min/avg/max/mdev = 0.176/0.176/0.176/0.000 ms
I'll gonna try now with 2.6.24.4
> Jeff
>
>
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to [email protected]
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
Gustavo Guillermo P?rez
Compunauta uLinux
http://www.compunauta.com