Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 10 Oct 2008 09:18:36 +0700 (ICT)
From:      Olivier Nicole <on@cs.ait.ac.th>
To:        derek@computinginnovations.com
Cc:        freebsd-questions@freebsd.org
Subject:   Re: Multiple NICs routing question
Message-ID:  <200810100218.m9A2Ia29057708@banyan.cs.ait.ac.th>
In-Reply-To: <6.0.0.22.2.20081009073538.02524488@mail.computinginnovations.com> (message from Derek Ragona on Thu, 09 Oct 2008 07:36:49 -0500)
References:  <20081009131623.M34013@gwdu60.gwdg.de> <6.0.0.22.2.20081009073538.02524488@mail.computinginnovations.com>

next in thread | previous in thread | raw e-mail | index | archive | help
>I've a server box with four NICs addressing different subnets:
>
>NIC1:   one class c subnet of same class b network
>NIC2:   another class c subnet of same class b network
>NIC3:   local unrouted network
>NIC4:   local unrouted network
>
>In the current configuration I use a default gateway (and no routing 
>daemon) in the subnet addressed by NIC1. Now of course, if a client in an 
>arbitrary different class c subnet contacts the server using the ip 
>address of NIC2, it gets a reply from NIC1.

You should give more details about your configuration.

If any client on the class B on NIC2 can contact your server, you must
configure the NIC for the class B.

The routing stack will take charge of excluding the class C on NIC1
from the class B on NIC2.

It's very bad that the client that connects via the NIC2 has a subnet
of class B and that the NIC2 is configured for class C only.

If you configure:

NIC1 192.168.1.1 255.255.255.0
NIC2 192.168.2.1 255.255.0.0

Client 192.168.127.23 255.255.0.0

it should work.

Olivier



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200810100218.m9A2Ia29057708>