ISA rtl8019

[PaulWeaver]

I'm Trying to set a box up with this card, its a right bugger. I've got the right IO and IRQ, and installed ne properly. I can bring up the interface (eth1) with a static ip. However thats it. It seems to forget to talk to anything. It seems to work as far as the hub, the lights flash when I try to ping out, but thats it. I cant ping any other machine and they cant ping this one.

It could be a hardware problem (faulty card) I guess.

lefkas:~# ./ne2k-diag
Checking the ethercard at 0x300.
Receive alignment error counter (0x30d) is ff
Passed initial NE2000 probe, value 00.
Station Address PROM 0: 00 00 00 00 21 21 e7 e7 3d 3d dd dd 20 20 20 20
Station Address PROM 0x10: 20 20 20 20 20 20 20 20 20 20 20 20 57 57 57 57
NE2000 found at 0x300, using start page 0x40 and end page 0x80.
The current MAC stations address is 00:00:21:E7:3DD.
This is a RTL8019AS chip in jumperless PnP mode.
The current settings are: IRQ 12 (enabled, I/O address 0x300,
The transceiver is set to 10baseT or coax, selected on 10baseT link beat,
The chip is set to half duplex.
The EEPROM settings are: IRQ 12, I/O address 0x300, PnP mode.
The transceiver is set to 10baseT or coax, selected on 10baseT link beat,
The chip is set to half duplex.

I'd go get a nice pci rtl8139 but the shop's shut

Theres nothing wrong with the network settings in general (eth0 is up and works fine), modprobe's fine.

[Schotty]

I have a shitload of RTL cards here in hell, aka WORK. I havent had really any probs using them (OpenBSD, RedHat, SuSE). One thing I would reccomend checking over is your routes. Do you have a default gateway setup? that would most certainly forbid you from going online. Second, whatabout pinging another host on the lan? How does that turn out? One other thing that stung me a few times -- check your subnets masks. Yes plural. Check to see that all machines on the lan are set to whatever subnet you actually want. For example, most of us will only need a Class C network. So if you use a 255.255.255.0 or FFFFFF00, make sure that each NIC has that in there.

I dont know how proficient you are in networking & troublshooting, but if I confused the hell out of ya, feel free to let me know.

[PaulWeaver]

I'm guessing the problem is somewhere in layer 3, as the card seems to work fine with the hub or xover to my laptop.


ahha, go to get pizza out of oven, while pinging the broadcast address

64 bytes from 192.168.1.5: icmp_seq=311 ttl=255 time=0.3 ms
64 bytes from 192.168.1.5: icmp_seq=312 ttl=255 time=0.3 ms
64 bytes from 192.168.1.2: icmp_seq=197 ttl=255 time=116053.4 ms (DUP!)
64 bytes from 192.168.1.5: icmp_seq=313 ttl=255 time=0.3 ms
64 bytes from 192.168.1.5: icmp_seq=314 ttl=255 time=0.3 ms
64 bytes from 192.168.1.2: icmp_seq=198 ttl=255 time=117053.9 ms (DUP!)
64 bytes from 192.168.1.5: icmp_seq=315 ttl=255 time=0.3 ms
64 bytes from 192.168.1.5: icmp_seq=316 ttl=255 time=0.3 ms
64 bytes from 192.168.1.2: icmp_seq=199 ttl=255 time=118050.1 ms (DUP!)
64 bytes from 192.168.1.5: icmp_seq=317 ttl=255 time=0.3 ms
64 bytes from 192.168.1.5: icmp_seq=318 ttl=255 time=0.3 ms
64 bytes from 192.168.1.5: icmp_seq=319 ttl=255 time=0.3 ms
64 bytes from 192.168.1.5: icmp_seq=320 ttl=255 time=0.3 ms
64 bytes from 192.168.1.5: icmp_seq=321 ttl=255 time=0.3 ms
64 bytes from 192.168.1.2: icmp_seq=200 ttl=255 time=122052.6 ms (DUP!)
64 bytes from 192.168.1.5: icmp_seq=322 ttl=255 time=0.3 ms

so there is a connection, just a very laggy, dropping out one.

323 packets transmitted, 323 packets received, +83 duplicates, 0% packet loss
round-trip min/avg/max = 0.2/15444.8/129840.1 ms

Anything?

[Schotty]

check the cable or card/hub ports. what I mean is, it looks like the sinal is getting messed up from your PCI/ISA slot to the next PC's PCI/ISA slot. Could be either card or the port(s) on the hub.

Since you seem to think its just that card, I would try moving it one slot over in your PC. that may help -- fried ISA slots happen. Or even a different port on the hub/switch. The 3Com and Linksys 48 port hubs here pop a port every now and then.

And sorry to possibly insult your intelligence I havent talked to you much while here. If at all.... I dont like confusing people, so thats why I asked.

Good luck, let me know what happens too.

[PaulWeaver]

I found the problem. It didnt like 0x300 as a resource. 0x320 was taken, but once I changed to 0x340 it worked no problem. I have no idea why - as nothing is using 0x300.

Eitherway it all works. Now to get a decent firewall script running

[Schotty]

cool!