Re: IPFW - Two External Interfaces

2006-05-19 Thread Andrew White
your rules don't forward ping to isp2, only port 80 ... try 00400 divert 8869 ip from any to any in via bge1 00450 divert 8868 ip from any to any in via em0 00500 check-state #Check for internal_system port 80 traffic 0600 skipto 900 from $internal_system to $remote_system 80 keep-state #Se

Re: IPFW - Two External Interfaces

2006-05-17 Thread Dennis Olvany
ISP 1 [192.168.2.254] | | [bge1:192.168.2.1] FIREWALL[bge0:10.0.0.1]---[10.0.0.2]internal_system [em0:192.168.1.1] | | [192.168.1.254] ISP 2 Actually, if you bridge the NICs, you may be able to get something going as r

Re: IPFW - Two External Interfaces

2006-05-16 Thread Dennis Olvany
PFS IT wrote: I am complicating the use of IPFW... Here is a pretty ascii picture. I drawed it meself. ISP 1 [192.168.2.254] | | [bge1:192.168.2.1] FIREWALL[bge0:10.0.0.1]---[10.0.0.2]internal_system [em0:192.168.1.1] | |

Re: IPFW - Two External Interfaces

2006-05-16 Thread Atom Powers
On 5/16/06, PFS IT <[EMAIL PROTECTED]> wrote: I am attempting to use IPFW (and either IPNAT or natd) to do the following: I have two connections to the outside world coming in to my firewall. em0 has a static ip and is going to a bridged DSL connection, then bge1 has a static ip and is going to

IPFW - Two External Interfaces

2006-05-16 Thread PFS IT
I am attempting to use IPFW (and either IPNAT or natd) to do the following: I have two connections to the outside world coming in to my firewall. em0 has a static ip and is going to a bridged DSL connection, then bge1 has a static ip and is going to a a few bonded DS1s. bge0 goes to my internal n