Date: Mon, 14 Feb 2000 10:35:19 -0700 From: "Duke Normandin" <01031149@3web.net> To: <cjclark@home.com> Cc: <freebsd-questions@FreeBSD.org> Subject: Re: Routed and public IPs Message-ID: <00e601bf7712$2f090460$f19ec5d1@webserver>
next in thread | raw e-mail | index | archive | help
On Sunday, February 13, 2000 10:12 PM Crist J. Clark wrote: >Well, if you want it to run as a bridge, first thing you need to do is >stp thinking about routing the public IPs all together. OK, if you >have a registered numbers, a.b.c.0/24, and the unregistered, >10.0.0.0/24 (it's shortest to write), this is how your IPs will end up >looking, > } > Internet }--[router]--[a.b.c.1:firewall:10.0.0.254]--+ > } | > | > | > _________________........____________________|_____........ > | | | | > [a.b.c.2:] [a.b.c.3:] ........ [10.0.0.1:] [10.0.0.2:] ........ > [ hostA ] [ hostB ] ........ [ host1 ] [ host2 ] ........ > >Like this. The machines with registered IPs on the internal LAN will >actually require no new configuration, nor does the router. Since the >firewall bridges, the router is still their gateway. Although I'm not involved in this thread, directly or indirectly, I want to thank you for such a great reply. I can't believe you and Ruslan et al -- I'm green with envy. I've saved this thread for future reference, however would you mind defining for me (in laymen's terms) the concept of bridge(4)ing? Something like: "bridging is using a box to bridge a gap between (public & private IPs??) or ?? ". I don't want your info to go to waste on this newbie, so I thought I'd ask. Tia... -duke To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00e601bf7712$2f090460$f19ec5d1>