On Tue, Nov 05, 2002 at 10:09:16AM +0100, Jonas Sonntag wrote:
> hi list
>
> i'm looking for a little advice here.
> i've got a fbsd server conected to the internet via rl0. there are about 30
> workstation in 192.168, fbsd does nat for, those are connected via rl1.
> now, on rl1, behind nat there's also a win2k server in here which should
> soon get connected to the internet, too (being accessible from the
> internet). i don't want to plug the win2k server next to the fbsd box into
> our isp's router. this way i'd had to set up an extra firewall on the win2k
> box, instead i'd like all connection to and from the internet with the win
> server to go through my existing ruleset on the fbsd box, leaving the win
> server on the inside interface rl1.
> just assiging one of the official ip's to the win box didn't work, so i was
> doing some reading and found out that bridging seemed to be the way to go.
> now i wonder: those how-to's say it's not nescessary to assign an ip to both
> interfaces, but i definitly still need an ip from the 192.168 subnet on the
> inside interface. just as the win2k box still needs to stay accessible with
> it's 192.168 adress.
> so...is it possible this way, or would it be far smarter to plug a third nic
> into the fbsd box only for bridging ?
Hi,
another solution would be to redirect the traffic from the fbsd box to the
win2k server. If you want the win2k server to have an external ip of its own
you can add an ip alias to your fbsd box and then redirect all traffic to this
ip to the win2k server.
Thats probably the easiest solution.
greets,
tom
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-questions" in the body of the message
