Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 24 Oct 1996 16:09:58 +0200
From:      roberto@keltia.freenix.fr (Ollivier Robert)
To:        freebsd-hackers@freebsd.org (freebsd-hackers)
Subject:   Re: Is this network possible with FreeBSD ???
Message-ID:  <199610241409.QAA26627@keltia.freenix.fr>
In-Reply-To: <326F4584.2F7E@degnet.baynet.de>; from Darius Moos on Oct 24, 1996 09:31:32 %2B0000
References:  <199610231333.IAA09985@brasil.moneng.mei.com> <326F4584.2F7E@degnet.baynet.de>

next in thread | previous in thread | raw e-mail | index | archive | help
According to Darius Moos:
> 1. The router is a KA9Q-ISPA-router, not capable of bridging.
> 2. The machines on the private company network (192.168.3.x) need
>    a gateway (the FreeBSD-box) and this gateway should be the
>    WWW-server, WWW-proxy and SMTP-server. I was told, the gateway
>    (the FreeBSD-box) has to have a IP in the private company network
>    (192.168.3.x), because they are all Windows machines and Windows
>    needs this (i don't know if Windows does it really need).

I don't think it is needed. Just put a default route to 192.168.3.104 on
every machine on the 100 Mb network and use another C-class for the
FreeBSD. The only way where it could matter is if the FreeBSD was also
a Samba server (SMB can't be routed).

> 3. ifconfigs for the FreeBSD-box:
>       ifconfig ed0 inet 1.2.3.253 netmask 0xffffff00
>       ifconfig ed0 inet 192.168.3.1 netmask 0xfffffc00 alias

Hmmm, why 0xfffffc00 ? That makes it a /22 network. If you plan to use 4
C-class network, why not put 192.168.3.103 on one end and 192.168.2.103 on
the other end of the router ? What I don't understand is why you split a
C-class network in half...

-- 
Ollivier ROBERT    -=- The daemon is FREE! -=-    roberto@keltia.freenix.fr
FreeBSD keltia.freenix.fr 2.2-CURRENT #25: Tue Oct 15 21:13:57 MET DST 1996



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