Re: Routing table drops packets via ppp0

From: Greg Folkert (greg_at_gregfolkert.net)
Date: 10/21/03

  • Next message: Clive Menzies: "Re: update in sid has killed gnome-terminal" 
    To: Debian User <debian-user@lists.debian.org>
Date: Tue, 21 Oct 2003 09:57:14 -0400

    On Tue, 2003-10-21 at 03:39, Mark Devin wrote:
    > I am having some trouble getting routing to work properly on a box with
    > three network connections. One, eth0, is connected to a router and is
    > the default gateway. Another, ppp0 (eth1 - ADSL) is connected to a
    > private network on the 192.168.17.0/24 address range. The third is a
    > standard LAN (eth2) on 192.168.2.0/24.
    >
    > From the debian box, I can ping other machines connected via the ADSL
    > modem via ppp0. I can also ping machines on the internet via eth0 from
    > this box. In addition, any machine on the Office LAN can connect to
    > machines on the internet.
    >
    > However, if a machine on the office LAN tries to connect to a machine on
    > the 192.168.17.0/24 network, the packets disappear somewhere in the
    > debian box. I can see the packets coming in with tcpdump but then they
    > disappear. The debian box does not try to route them at all.
    >
    > Note that I have switched off all firewalling and switched ip_forwarding
    > on in the kernel.
    >
    > The problem is related to the ADSL - ppp0 interface. The routing rules
    > look OK. I can ping from the debian box via ppp0 to hosts on the
    > connected network. However, if I ping from the office LAN, the packets
    > do get to the debian box OK, but it doesn't route them out ppp0. It
    > just seems to drop them. There is nothing in the logs to indicate any
    > errors. The packets just disappear.
    >
    > The setup looks like this:
    >
    > Internet
    > |
    > x.x.47.224/27 Router x.x.47.225
    > |
    > eth0| x.x.47.226
    > |
    > #------------# (eth1 -ppp0 ADSL)
    > # Debian Box #--192.168.17.2-->x.x.16.78-->192.168.17.0/24
    > #------------#
    > |
    > eth2| 192.168.2.1
    > |
    > |
    > Office LAN (192.168.2.0/24)
    >
    > The routing table looks like:
    > # route -n
    > Destination Gateway Genmask Flag Met Ref Use Iface
    > x.x.16.78 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0
    > x.x.243.224 0.0.0.0 255.255.255.224 U 0 0 0 eth0
    > 192.168.2.0 0.0.0.0 255.255.255.0 U 0 0 0 eth2
    > 192.168.17.0 x.x.16.78 255.255.255.0 UG 0 0 0 ppp0
    > 0.0.0.0 x.x.243.225 0.0.0.0 UG 0 0 0 eth0

    Silly question:

    Are you running a routing daemon? 

    -- 
greg, greg@gregfolkert.net
REMEMBER ED CURRY! http://www.iwethey.org/ed_curry
My elbow sockets sharpen pencils when you pass by on divine fumes of
industrial combustion.



    -- 
To UNSUBSCRIBE, email to debian-user-request@lists.debian.org 
with a subject of "unsubscribe". Trouble? Contact listmaster@lists.debian.org
  • Next message: Clive Menzies: "Re: update in sid has killed gnome-terminal"

    Relevant Pages

    • Re: Routing table drops packets via ppp0
      ... >>three network connections. ... >> From the debian box, I can ping other machines connected via the ADSL ... I can see the packets coming in with tcpdump but then they ... > Are you running a routing daemon? ...
      (Debian-User)
    • Re: Routing with 2 ISP
      ... I had a small network with one ISP and firewall. ... I will add the second routing table named "adsl" and configure routing ... Also, unless you have nothing but machines and people you trust on all these little subnets, have the external ISP connections on NICs not reachable from the private machines without going through your firewall. ...
      (Fedora)
    • Routing table drops packets via ppp0
      ... three network connections. ... private network on the 192.168.17.0/24 address range. ... From the debian box, I can ping other machines connected via the ADSL ...
      (Debian-User)
    • Re: Traffic NOT moving through the correct network interface?
      ... and the key is in the routing table. ... inbound connections to automatically use this port for the corresponding ... No matter where the packet they are ... How could the network software know what inbound packet spawned them? ...
      (alt.os.linux)
    • Re: Multiple internet connections routing.
      ... >> I have two internet connections for my network. ... Let's say ISP1 is the default ISP. ... Now, when ISP1 fails, the routing should now start through ISP2 ...
      (comp.os.linux.networking)