[Shorewall-users] Public IP issues
teastep at shorewall.net
Tue Sep 7 14:17:15 PDT 2004
-----BEGIN PGP SIGNED MESSAGE-----
Andrew Niemantsverdriet wrote:
| My problem must be a routing issue.
| Just to clarify I can still use masq for the private IP's so my masq
| file would look like this:
| eth0 10.1.0.0/24 public IP here
|>| Also as a bonus question, I currently have:
|>| LAN<===>router1<--T1 Line-->router2<===>Shorewall<--->Internet
|>| LAN and router1 all have a 10.1.0.0/24 address
|>| router2 and the Shorewall local interface have a 10.0.0.0/24 address
|>| How should I split up my new public /24 block so that everything has a
|>| public IP?
| Thanks for your suggestion with this. One thing that should be noted is
| a server is going to be added in the near future that is going to sit on
| the same hub the router 2 and Shorewall loc zone is connected to. It
| would be nice to have 6 or so public IP's on the router 2 side of the
| T1. Hope that makes sense.
Sure -- just make sure that you align the block of addresses so that you
can handle them with a single route (/29).
Tom Eastep \ Nothing is foolproof to a sufficiently talented fool
Shoreline, \ http://shorewall.net
Washington USA \ teastep at shorewall.net
PGP Public Key \ https://lists.shorewall.net/teastep.pgp.key
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
-----END PGP SIGNATURE-----
More information about the Shorewall-users