Well, apparantly, this is more than just the forwarding issue
and may not be the forwarding at all. I've been informed that
since we changed the IP of the PC from 10.10.100.95 to
10.10.150.26, now when they try to log to the linux machine
the PC just sits for about a minute or so. When I changed
the IP back to 10.10.100.95, there was no time delay on
login. So Once I get this problem corrected, then maybe
the below scenario will work. I'm not using DNS on that
system, I think my netmask may not be accurate.
Thanks for the replies to the first part.
As a side question. Does anyone know what software is
needed to establish a ppp connection vs a slip connection
on a DU 3.2c rev O/S.
Thanks
George Gallen
ggallen_at_slackinc.com
-----Original Message-----
From: George Gallen [mailto:ggallen_at_slackinc.com]
Sent: Thursday, August 26, 1999 11:27 AM
To: 'tru64-unix-managers_at_ornl.gov'
Subject: Networking issue
Below is network topology for our slip
connection to our remote warehouse.
2100 <-| ---(tu0) 10.10.150.30
3.2c |----(sl0) 10.10.150.25 <-slip-> 10.10.150.24 (sl0) ---|-> Linux
2.2.6
10.10.150.29 (eth0)---|
10.10.150.26 (ethernet)->W95 PC
On the linux machine, ipforwarding is turned on, with no filtering
so it "should" be forwarding all packets from sl0 <--> eth0. But it
doesn't seem to be doing so...The DEC machine is not functioning as
a router, but rather I setup static routes for the IP's I want to
use on the remote network (specifically 10.10.150.26).
On the DEC end.
default 10.10.1.1 UG 0 8539 tu0
10 10.10.150.30 U 37 452251 tu0
10.10.150.24 10.10.150.25 UH 2 23967 sl0
10.10.150.26 10.10.150.24 UGH 0 20 sl0
10.10.150.29 10.10.150.24 UGH 0 3 sl0
localhost localhost UH 6 17514 lo0
On the Linux end.
Destination Gateway Genmask Flags Metric Ref Use
Iface
default 10.10.150.29 255.255.255.255 UGH 0 0 0
eth0
10.10.150.30 10.10.150.25 255.255.255.255 UGH 0 0 0
sl0
10.10.150.25 10.10.150.24 255.255.255.255 UGH 0 0 0
sl0
10.10.150.26 10.10.150.29 255.255.255.255 UGH 0 0 0
eth0
localnet * 255.255.0.0 U 0 0 0
eth0
loopback * 255.0.0.0 U 0 0 0
lo
The PC, uses 10.10.150.29 as it's gateway with a 255.255.0.0 netmask.
all systems have recently (within 24hr) been rebooted.
Traceroute from the DEC to the PC on the Linux's ethernet
# traceroute 10.10.150.26
traceroute to 10.10.150.26 (10.10.150.26), 30 hops max, 40 byte packets
1 10.10.150.24 (10.10.150.24) 187 ms 180 ms 180 ms
2 *
What I can do..From the DEC. I can ping 10.10.150.24 & 10.10.150.29 (the
sl0 & eth0 addresses of the linux machine). From the Linux machine, I
can ping 10.10.150.25 & 10.10.150.30 (the sl0 & tu0 address of the DEC
machine). From the remote PC, I can ping 10.10.150.24 & 10.10.150.29
(the
sl0 & eth0 addresses of the linux machine).
When I ping the 10.10.150.26, I can see the TD light blinking on the
modem
so I know it's using the sl0, but it never gets replies. :(
Just as when I ping 10.10.150.30 (or 10.10.150.25) from the PC, I get
request timed out.
What my end result I want to have work is, have the Linux machine
forward
all packets from it's sl0 <--> eth0 and the DEC NOT forward from it's
sl0
to it's tu0 (for security reasons). I don't need ip masq, as the remote
network will never see the internet, just the DEC.
Is there anything drastically wrong, esp on the DEC end?
Thanks
George Gallen
ggallen_at_slackinc.com
Received on Thu Aug 26 1999 - 18:03:01 NZST