debian user

in a previous post, i asked this question but not sure if an answer
was found ...


i am trying to set up a network in my office at work.

+---------------+ +---------------+
| 192.168.1.100 |-----| 192.168.1.1 |
| 255.255.255.0 | | 255.255.255.0 | +---------------+
+---------------+ | 10.20.1.158 |---| 10.20.4.48 |
| 255.255.0.0 | | 255.255.0.0 |
+---------------+ +---------------+

the 192.168.1.100 machine can ping the 192.168.1.1 and 10.20.1.158
interface but not the 10.20.4.48 interface. the 10.20.1.158 interface
can ping the 10.20.4.48 interface.

my routing table is as follows:

dest gateway genmask flags metric ref use iface
192.186.1.0 * 255.255.255.0 u 0 0 0 eth1
10.20.0.0 * 255.255.0.0 u 0 0 0 eth0
default 10.20.4.48 0.0.0.0 ug 0 0 0 eth0

any suggestions as to what i am doing wrong?

--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

antony gelberg

Not turning on IP routing? cat /proc/sys/net/ipv4/ip_forward. If it's
0, routing is off.

I suppose TDW for this is to set ip_forward=1 in /etc/network/options.
What this does is effectively echo 1 > /proc/sys/net/ipv4/ip_forward

A

--
Please don't CC me. Also _please_ read the following before posting:
Documentation - http://www.debian.org/doc/
FAQ - http://www.debian.org/doc/FAQ/
Install manual (i386) - http://www.debian.org/releases/stable/i386/install


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

debian user

right ... forgot about that. when i ping 10.20.4.48 from 192.168.
1.100, the requests time out. this tells me that there is a route
to the host ... if this matters. anyway, i am still unable to reach
10.20.4.48 from 192.168.1.100.

anything else?


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

debian user

right ... forgot about that. when i ping 10.20.4.48 from 192.168.
1.100, the requests time out. this tells me that there is a route
to the host ... if this matters. anyway, i am still unable to reach
10.20.4.48 from 192.168.1.100.

anything else?


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

debian user

At Friday, 2 January 2004, Debian User <debian-user@zerocrossings.

because the 10.20.x.x network is a private network, don't i need
masquerading? i am thinking this b/c the 192.168.1.100 machine does
not flag 'no route to host' so it must know where to send the packets.
the gateway (10.20.4.48) must not be sending the packets to the
192.168.x.x net correct?

--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

debian user

At Friday, 2 January 2004, Debian User <debian-user@zerocrossings.

because the 10.20.x.x network is a private network, don't i need
masquerading? i am thinking this b/c the 192.168.1.100 machine does
not flag 'no route to host' so it must know where to send the packets.
the gateway (10.20.4.48) must not be sending the packets to the
192.168.x.x net correct?

--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

debian user

At Friday, 2 January 2004, Debian User <debian-user@zerocrossings.


routing table is/was fine ... turned out to be iptable rules that
were not masking the 192.168.1.100 address from the 10.20.x.x private
net.


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

debian user

At Friday, 2 January 2004, Debian User <debian-user@zerocrossings.


routing table is/was fine ... turned out to be iptable rules that
were not masking the 192.168.1.100 address from the 10.20.x.x private
net.


--
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org

kevin mark

echo 'ip_forward=yes' > /etc/network/options
as root. this turns on ip forwarding. This allow packects to be
sent to the next computer and beyond.
My info says that 192.168.1.100 can only send to a host on its
network -- any thing 192.168.1.x. But you set the default
gateway to 10.20.x.x which it can not get to.
Also, I ususally add a '-host' entry to the routing table.
so,
'route add default gw 192.168.1.1'
fixes the route on host1
then on the gateway1 machine:
'route add default gw 10.20.4.48'
to help packets go to gateway2 if needed.
(and of course do the ip_forward thing)

-Kev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQE/9d8fAWAAuqdWA9cRAgZiAJ9TRaiFff7SCwHs9S8URuWbQJpX/QCfUHki
lJ+uzdo+CesCztP136igwY8=
=X2w+
-----END PGP SIGNATURE-----

kevin mark

echo 'ip_forward=yes' > /etc/network/options
as root. this turns on ip forwarding. This allow packects to be
sent to the next computer and beyond.
My info says that 192.168.1.100 can only send to a host on its
network -- any thing 192.168.1.x. But you set the default
gateway to 10.20.x.x which it can not get to.
Also, I ususally add a '-host' entry to the routing table.
so,
'route add default gw 192.168.1.1'
fixes the route on host1
then on the gateway1 machine:
'route add default gw 10.20.4.48'
to help packets go to gateway2 if needed.
(and of course do the ip_forward thing)

-Kev

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQE/9d8fAWAAuqdWA9cRAgZiAJ9TRaiFff7SCwHs9S8URuWbQJpX/QCfUHki
lJ+uzdo+CesCztP136igwY8=
=X2w+
-----END PGP SIGNATURE-----