Re: ethernet routing

From: Debian User (debian-user_at_zerocrossings.com)
Date: 01/03/04

  • Next message: Kenneth Jacker: "Re: USB 2 Sony Microvault Problems" 
    Date: Fri, 02 Jan 2004 18:10:33 -0500
To: debian-user@lists.debian.org


    Kevin Mark wrote:
    On Fri, Jan 02, 2004 at 10:46:06AM -0500, Debian User wrote:
  
    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?
    
    Hi,
	first do:
	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
    i ended up loading the iptables modules ... guess they were not loaded by default. i spent some time llisting the forwarding rules and it works. when i pinged from 192.168.1.100 to an address on 10.20.x.x, there was not a report of _no route to host_. by this, i figured that the routing table was good enough.
    -- To UNSUBSCRIBE, email to debian-user-request@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Kenneth Jacker: "Re: USB 2 Sony Microvault Problems"

    Relevant Pages

    • Re: AIX 1.3 Failures and Fables
      ... DESTINATION GATEWAY FLGS REFCNT USE INTERFACE ... Is my interpretation of the AIX 1.3 #man route correct? ... Manually manipulates the routing tables. ... Is the destination host or network. ...
      (comp.sys.ibm.ps2.hardware)
    • Re: AIX 1.3 Failures and Fables
      ... I don't know if 1.3 has SMIT or its equivalent but there should be some way to add a default gateway which is your router. ... Is my interpretation of the AIX 1.3 #man route correct? ... Manually manipulates the routing tables. ... Is the destination host or network. ...
      (comp.sys.ibm.ps2.hardware)
    • Re: AIX 1.3 Failures and Fables
      ... I don't know if 1.3 has SMIT or its equivalent but there should be some way to add a default gateway which is your router. ... is: route add 1.2.3.4 gateway ... Manually manipulates the routing tables. ... Is the destination host or network. ...
      (comp.sys.ibm.ps2.hardware)
    • Re: DECWindows SET/DISPLAY & CREATE/TERM/DETACH problem on Alphaserver DS10L
      ... So we have a default route. ... Maybe what is happening is that because of the way routing is setup the ... DHCP client failed to configure interface WE1 ... INTERnet ACP Created INTERnet interface: ...
      (comp.os.vms)
    • Re: Wireless laptop roaming through various access points
      ... Whichever interface has the default route pointing to it, ... It is possible to assign more than one default gateway in the ... What needs to change is the ARP table, which maps the MAC address to ...
      (alt.internet.wireless)