FreeBSD routing between 2 interfaces

freebsd at freebsd at
Tue Sep 30 20:37:47 PDT 2003

Yes I realize about the 10.0... and 192.168.... not being routed matter.
Previosly I always setup the network but never run out of IP address in
the same range(192.168.0.*). It happened this time. Therefore I created
the 192.168.1.* network but now it wont route. I can use NAT for that
purpose but that would defeat communication between the 192.168.1.* and
192.168.0.* networks(there are a bunch of ftp and samba file/print servers
in the 1.* network).

I mean if I use nat:
192.168.0.* Connect > 192.168.1.* = No success
192.168.0.* < Connect 192.168.1.* = Success

> On Tuesday, 30 September 2003 at 21:33:43 -0400,
> freebsd at wrote:
>> Dear FreeBSD users,
>> I urgenly need to connect 192.168.1.* network to the internet. What
>> am I doing wrong?
> You're assuming it's possible.  It's not.  Addresses in the range
> 192.168.x.x are explicitly not routed.  See RFC 1918
> ( for further
> details.
> You're not very clear about your router, but I assume it does NAT for
> you: to connect an RFC 1918 network to the Internet, you need to use
> some form of Network Address Translation (NAT).  Theoretically, you'd
> need to do the same at the junction between the 192.168.0.x and
> 192.168.1.x networks, though you might be able to fake things by
> choosing 23 bit net masks.  If this doesn't mean anything to you,
> don't ask.
> Greg
> --
> When replying to this message, please copy the original recipients.
> If you don't, I may ignore the reply or reply to the original recipients.
> For more information, see
> See complete headers for address and phone numbers.
> NOTE: Due to the currently active Microsoft-based worms, I am limiting
> all incoming mail to 131,072 bytes.  This is enough for normal mail,
> but not for large attachments.  Please send these as URLs.

More information about the freebsd-questions mailing list