Hi Matt
> Sorry about the numbers there I added them as I was planning to write an
> explanation of each then decided it probably wasn't required and forgot
> to remove them.  Oh well they serve as identifiers if anyone has any
> further queries related to them.
No problem, and what you've done here does I think help a lot.

I will have to pull my courage together and actually do it now! (this is 
all on the one-and-only internet access for the site and there are 
external servers here, so being down at all is to be avoided... )

Best regards,
Ruth

>
> On 04/03/13 23:09, Matt Joyce wrote:
>> Hi Ruth, I will answer as best I can the parts I'm familiar with for
>> you.  I used to have a static /28 subnet with a prior ISP so I have
>> experience with some of these points.
>>
>> With the default server your questions lead me to believe that you are
>> presuming that you cannot keep on having shorewall take over the routers
>> job here and preform the same job, every NAT rule is separate and can
>> either specify an IP address or specify and IP and port such that you
>> can easily have some odd ports go to one location and the remainder go
>> to a default endpoint.  The way to go about this in shorewall would be
>> about the order you place the rules in the file, with a few exceptions
>> noted in the documentation (like tcrules) iptables rules are first match
>> wins, this means if you wrote your shorewall rules like this it would work.
>>
>> 1 DNAT        net            loc:IP1            tcp            25
>>          -                &netiface
>> 2 DNAT        net            loc:IP2            tcp            80
>>          -                &netiface
>> 3 DNAT        net            loc:DEFIP        -                -
>>            -                &netiface
>>
>> You can use the IP instead of &ifname if you prefer it simply expands to
>> the primary IP address on ifname which is useful if there is any chance
>> that the IP address could change or just for readability.  Do note the
>> ordering is important when any of these rules match the packet is done
>> so you need your most specific/highest priority rules first and lower
>> priority wide defaults last.
>>


-- 
Software Manager & Engineer
Tel: 01223 414180
Blog: http://www.ivimey.org/blog
LinkedIn: http://uk.linkedin.com/in/ruthivimeycook/



------------------------------------------------------------------------------
Everyone hates slow websites. So do we.
Make your web apps faster with AppDynamics
Download AppDynamics Lite for free today:
http://p.sf.net/sfu/appdyn_d2d_feb
_______________________________________________
Shorewall-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/shorewall-users

Reply via email to