3c507 weird?

3c507 weird?

Post by John Paul Morris » Fri, 25 Nov 1994 03:57:59

Is the 3c507 a screwy card or is it just the alpha driver? (It's a
relative of the Intel EtherExpress, so it's probably a brain damaged
card) I've found that I have to use a smaller mtu (1000 instead of
1500) and perhaps I should make it smaller still.

For a while I thought I had an mtu problem with the router on the
other end of a 56k link, but other machines on our radio club's
ethernet work OK with mtu 1500, including the router on our side of
the 56k net. I had problems with tcp connections locking up on the
3c507 machine when the mtu was 1500 (I was running Linux 1.1.47, now
upgraded to 1.1.64, but I haven't tried it with a 1500 mtu yet).

Then I noticed problems on the local ethernet with ping. I would try
ping -s 992 -c 100 and then:

3c507 linux 486-25 to 3c509 windows for workgroups 486-25
        45-50% packet loss!

(I can reduce the ping size further, down do around 950 approximately,
and pings then get get 0% loss)

3c507 linux 486-25 to 8bit Depca card, linux 386SX-16
        0 % packet loss

8bit Depca linux 386SX-16 to Windows for Workgroups 486-25
        0 % packet loss

(If you haven't seen a DEC Depca card before, it's a hoot: full length
8 bit card that gets very toasty. Pretty solid driver though...)

The Windows 3.11 machine has the latest Microsoft TCP/IP stack; but I
think it's using the original 3c509 driver; perhaps that needs
updating. Linux 1.1.64/65 on the other machines.

Would the 3c507 work better in a slower machine? Perhaps I should play
musical ethernet cards and see if things are better (timing/driver
differences) if I move the ethernet cards around.

BogoMIPS Research Labs  --  bogosity research & simulation  --  VE7JPM  --



1. Weird Ping, weird FTP, weird Telnet... HELP!!!

Can anyone diagnose this for me?

I'm in the process of building up a firewall but at some stage I musta
messed up and am now getting really weird results.

This is the results of a ping from to (the box
which will become the fireawall).

PING ( from : 56(84) bytes of
64 bytes from icmp_seq=0 ttl=225 time=0.7ms
64 bytes from icmp_seq=1 ttl=225 time=80001.0ms
64 bytes from icmp_seq=2 ttl=225 time=160000.9ms
64 bytes from icmp_seq=3 ttl=225 time=240000.8ms
64 bytes from icmp_seq=4 ttl=225 time=320000.8ms
64 bytes from icmp_seq=5 ttl=225 time=400000.7ms
64 bytes from icmp_seq=6 ttl=225 time=480000.7ms


--- ping statistics ---
509 packets transmitted, 8 packets received, 98% packet loss
round-trip min/avg/max = 0.7/280000.7/560000.6 ms

This also happens when I do it from other machines behind the firewall
but I was very surprised when it did it when pinging itself.

Theres a pattern of 80000ms increments between successful pings...
Can't figure out whats wrong though.

If I try to telnet or FTP, I have to wait for an eternity b4 the login
prompt appears after the initial "connected" msg. But once I login
there is no problem using the console or transferring files. Same
thing for other machines to So the network is "working"
but its waiting for something.

Has anyone had this happen to them b4 and manage to solve it?

Any help appreciated


2. machine crashed where do I start to fix it

3. Weird, weird, weird issue ....

4. Samba Configuration Problem

5. Weird, really weird???

6. KDE 2.0 and killustrator (why gets KDE 1...)?

7. Anyone using 3C507 (3Com EtherLink 16)?

8. SSI problem when viewing in netscape

9. 3c507 ethernet driver crashes

10. eth0 and 3Com 3c507 NIC card

11. 3C507 Problems

12. 3Com 3c507?

13. eth0 and 3Com 3c507 NIC card