Problems with network

Problems with network

Post by Kari Telaran » Mon, 17 Mar 1997 04:00:00



I try to build a network between 3 machines. (286/12, 486/120 and P90).
286: 3c501 etherlink card, DOS, IP 192.0.0.3
486: 3c501 etherlink card, Linux 2.0.28 (SlackWare), IP 192.0.0.1
P90: NE2000 clone (PnP disabled), Linux 2.0.27 (RedHat) and Win 95, IP
     192.0.0.2

But any of these machines won't respond to PING or Telnet. I can grap P90's
packets on 486 and so (using tcpdump),
but if i try to PING P90 on 486, all packets will be lost + P90 prints te
following message (many times):
"eth0: bogus packet size=36928, status=0x21 nxpg=0xdd
 eth0: next frame inconsistency, 0xdd"
(this happens _only_ when i try to ping P90 on 486)
What could be wrong?

--

 
 
 

Problems with network

Post by Gary Hest » Mon, 17 Mar 1997 04:00:00



>I try to build a network between 3 machines. (286/12, 486/120 and P90).
>286: 3c501 etherlink card, DOS, IP 192.0.0.3
>486: 3c501 etherlink card, Linux 2.0.28 (SlackWare), IP 192.0.0.1

      ^^^^^
Get rid of the 3C501s. *Nobody* recommends using them any more. You can
get new NE2000 clones for $25 or less, or used 3C503, 3C507, SMC8013 and
SMC8216 cards for $10 or so. I picked up a SMC8216 Combo for $7.50 once.

You'll find things work *much* better.

Gary

--

   The Chairman of the Board and the CFO speak for SCI. I'm neither.
The Sultan of Brunei "has four Gulfstream IVs, three Airbuses, two Boeing
747s and one 767". (Forbes FYI)   I'm available for adoption, Sultan.

 
 
 

1. Iproute2 problem across networks using NAT and 2 internal networks

Hi all,
Here's the deal. I have a machine that faces the internet and has an
internal network and a DMZ. I am using iproute to NAT an ip from
public to private.

ip route add nat 4.4.4.4 via 10.1.1.1
ip rule add from 10.1.1.1 nat 4.4.4.4

Everything works fine with the preceding route and rule when talking
to the machine from the internet. The problem is that when a machine
in the internal network, say 10.1.2.1, talks to the 10.1.1.1 machine
in the DMZ, the replies get natted to 4.4.4.4, instead of replies with
the src address of 10.1.1.1. The idea is to have these ip's not get
natted when going in between the DMZ and Internal Network. Thus, the
replies come from 10.1.1.1. I toyed around with using multiple routing
tables but got nowhere. Please advise.

Internet -----|Firewall|---DMZ--- 10.1.1.1 (NAT 4.4.4.4)
                  |
                  |          
           Internal Network
                  |
                  |
              10.1.2.1

Internet to DMZ is working fine with NAT.
Internal Network, 10.1.2.1 talking to 10.1.1.1, replies come from
4.4.4.4
I need replies to come from 10.1.1.1.

TIA for any guidance.

2. PPP server using diald, mgetty or dip?

3. Problem with network(connecting to internet via local network)

4. External Floppy via Parallel Port?

5. modprobe / module problem w/ network drivers (but network works)

6. Help with HD >1024 Cyls

7. Network problem: SIOCADDT: Network is unreachable

8. Broadcast message on local subnet

9. network problem - local network setup

10. PPP Problem or network problem?

11. problem with networking

12. Problems with network printing