Re: ethernet routing

From: Kevin Mark (kmark+debian-user_at_pipeline.com)
Date: 01/02/04

  • Next message: Paul Morgan: "Re: printer icon" 
    Date: Fri, 2 Jan 2004 16:14:07 -0500
To: debian-user@lists.debian.org

    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
            
             

    


    -- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Paul Morgan: "Re: printer icon"

    Relevant Pages

    • Point-to-Point interfaces and routing
      ... I have found to myself strange behaviour and difference between routing to IPs on ngX, ... So now I can ping ip on tun0, ... interface: tun0 ...
      (freebsd-net)
    • Re: Network FUBAR
      ... because you said the interface was up and in the routing table. ... I *have* seen a system come up with only one network card, ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx ...
      (Debian-User)
    • Routing problem
      ... from B I can ping all interfaces on A and C. ... >From C I can only ping B's 10.1.1.9 interface. ... B's routing table: ... Active Routes: ...
      (microsoft.public.win2000.networking)
    • Re: Modem and NIC Gateway
      ... routing table looks thus. ... but i still can't ping 172.21.0.1 from a client. ... To UNSUBSCRIBE, email to debian-user-REQUEST@xxxxxxxxxxxxxxxx with a subject of "unsubscribe". ...
      (Debian-User)
    • Re: in.c autoadding prefix route
      ... > case that there is a route already, we leave it alone and add the new address ... PING 10.0.16.111: 56 data bytes ... You should add routing of interface address itself to ... To unsubscribe, ...
      (freebsd-arch)
    Loading