netfilter.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: George Botye <gybotye@gmail.com>
To: netfilter@vger.kernel.org
Subject: Re: Basic routing
Date: Sat, 04 Oct 2014 09:50:45 +0100	[thread overview]
Message-ID: <542FB4E5.4030902@gmail.com> (raw)
In-Reply-To: <m0ni81$v7l$1@ger.gmane.org>


On 04/10/14 02:24, John Smithee wrote:
> John Smithee wrote, On 10/04/2014 03:10 AM:
>> Hi,
>>
>> I've 2 NICs on a machine, both attached to seperate networks
>> (192.168.68.0/24 and 192.168.69.0/24). I'm trying to set up a
>> basic gateway (or routing?) between the two networks.
>>
>> The first network has a gateway to other networks behind it,
>> it can reach all networks well, incl. the first network.
>>
>> The second network can reach the first, but reaching anything
>> beyond (ie. the other networks behind the first network) is
>> somehow not possible.
>>
>> Only IPv4 is used, and IP forwarding on the machine is enabled (ie.
>> net.ipv4.ip_forward=1 in /etc/sysctl.conf).
>>
>> Is this a classical routing issue or has this to be done via iptables?
>>
>> I rather would like to keep the original IPs in the packet headers,
>> ie. not use NAT, and also not use bridging.
>> How can this be done?
>
>
> Here's some more info:
>
>
> # /etc/network/interfaces
> auto lo
> iface lo inet loopback
>
> auto eth0
> allow-hotplug eth0
> iface eth0 inet static
>   address   192.168.68.22
>   netmask   255.255.255.0
>   broadcast 192.168.68.255
>   gateway   192.168.68.254
>
> auto eth1
> allow-hotplug eth1
> iface eth1 inet static
>   address   192.168.69.22
>   netmask   255.255.255.0
>   broadcast 192.168.69.255
>
>
>
> # route
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    
> Use Iface
> default         192.168.68.254  0.0.0.0         UG    0 0        0 eth0
> link-local      *               255.255.0.0     U     1 0        0 eth0
> 192.168.68.0    *               255.255.255.0   U     1 0        0 eth0
> 192.168.69.0    *               255.255.255.0   U     0 0        0 eth1
>
>
>
> Pinging the external gateway (192.168.68.254) from eth0 works fine,
> but not from eth1:
>
> # ping -I eth1 192.168.68.254
> PING 192.168.68.254 (192.168.68.254) from 192.168.69.22 eth1: 56(84) 
> bytes of data.
> From 192.168.69.22 icmp_seq=1 Destination Host Unreachable
> From 192.168.69.22 icmp_seq=2 Destination Host Unreachable
> From 192.168.69.22 icmp_seq=3 Destination Host Unreachable
> ^C
> --- 192.168.68.254 ping statistics ---
> 5 packets transmitted, 0 received, +3 errors, 100% packet loss, time 
> 4022ms
>
>
>
> -- 
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> .
>
Hi,

Drawing always helps you... :-)

         eth0                                                   eth1
|                                                          |
           V                                                        V
--------------------- ---------------------
| 192.168.68.0 |        <---???--->       | 192.168.69.0 |
--------------------- ---------------------

Please imagine what happen with packet addressed to 192.168.68.254 in 
192.168.69.0/24.
(I suggest read this http://www.tldp.org/LDP/nag2/nag2.pdf)

Regards, George

  reply	other threads:[~2014-10-04  8:50 UTC|newest]

Thread overview: 45+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-10-04  1:10 Basic routing John Smithee
2014-10-04  1:24 ` John Smithee
2014-10-04  8:50   ` George Botye [this message]
2014-10-04  1:34 ` Neal Murphy
2014-10-04  2:52   ` John Smithee
2014-10-04  3:05     ` Dennis Jacobfeuerborn
2014-10-04  5:02     ` Neal Murphy
2014-10-04  7:04     ` John Lister
2014-10-04 11:06       ` John Smithee
2014-10-04 13:56         ` Thomas Bätzler
2014-10-04 15:07           ` John Smithee
2014-10-04 17:44             ` John Smithee
2014-10-05 15:41               ` John Lister
2014-10-06  9:41               ` André Paulsberg
  -- strict thread matches above, loose matches on Subject: below --
2008-11-02 16:15 Basic Routing Daniel L. Miller
2008-11-02 17:03 ` Rob Sterenborg
2008-11-02 18:43   ` Daniel L. Miller
2008-11-02 19:53     ` Rob Sterenborg
2008-11-03  1:59       ` Daniel L. Miller
2008-11-02 20:04     ` Grant Taylor
2008-11-02 20:51     ` Grant Taylor
2008-11-03  1:52       ` Daniel L. Miller
2008-11-03  2:34         ` Grant Taylor
2008-11-03 19:29           ` Daniel L. Miller
2008-11-03 19:39             ` Daniel L. Miller
2008-11-03 20:26               ` Grant Taylor
2008-11-05  0:00                 ` Daniel L. Miller
2008-11-05  5:21                   ` Rob Sterenborg
2008-11-05 15:56                     ` Grant Taylor
2008-11-05 18:22                       ` Rob Sterenborg
2008-11-05 18:30                         ` Grant Taylor
2008-11-05 19:49                           ` Rob Sterenborg
2008-11-05 15:24                   ` Grant Taylor
2008-11-03 23:40               ` Amos Jeffries
2008-11-04 23:13             ` Grant Taylor
2008-11-04 23:53               ` Daniel L. Miller
2008-11-05 12:24                 ` John Haxby
2008-11-05 17:31                   ` Grant Taylor
2010-09-20 21:40                     ` Daniel L. Miller
2010-09-20 23:41                       ` Jan Engelhardt
2010-09-21  3:34                       ` Grant Taylor
2008-11-05 17:17                 ` Grant Taylor
2008-11-02 19:06   ` Grant Taylor
2008-11-03 10:54     ` Pascal Hambourg
2008-11-03 16:35       ` Grant Taylor

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=542FB4E5.4030902@gmail.com \
    --to=gybotye@gmail.com \
    --cc=netfilter@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).