Michael W. Ryan on Tue, 20 Jun 2000 09:47:11 -0400 (EDT) |
On Tue, 20 Jun 2000, Michael C. Toren wrote: > I'm a little confused about your network layout, though. You have: > > router <-> 192.168.1.0/25 <-> linux <-> 192.168.1.128/25 <-> end user > > Is that correct? If so, give the router an IP address in 192.168.1.0/25 > for the ethernet link it's going to share with the linux box, have the > linux box default route to the router's IP on that segment, and on the > router, staticly route 192.168.1.128/25 to the linux box's IP in > 192.168.1.0/25. That takes care of the "router being able to figure it > out" bit. > > What I don't quite understand, though, is how you are going to translate > the RFC1918 space into space allocated to you by your upstream? Is the > router doing NAT for 192.168.1/24? Does the linux box have another IP > address on the 192.168.1.0/25 ethernet segment which it will be > masquerading the 192.168.1.128/25 addresses behind? As I mentioned early in my explanations, I've replaced our real network address with "192.168.1". We have a regular class C network. I'm just not giving the address, given that we don't currently have a firewall in place. :) Michael W. Ryan, MCP, MCT | OTAKON 2000 mryan@netaxs.com | Convention of Otaku Generation http://www.netaxs.com/~mryan/ | http://www.otakon.com/ No, I don't hear voices in my head; I'm the one that tells the voices in your head what to say. ______________________________________________________________________ Philadelphia Linux Users Group - http://plug.nothinbut.net Announcements - http://lists.nothinbut.net/mail/listinfo/plug-announce General Discussion - http://lists.nothinbut.net/mail/listinfo/plug
|
|