search for: find_first_interface_address

...tcpflags,routeback lan2 eth3 detect tcpflags,routeback masq: # INTERFACE SUBNET ADDRESS eth0 $ETH0_IP 217.100.100.10 eth2 $ETH2_IP 217.132.100.100 eth0 eth1 eth2 eth3 params: ETH0_IP=$(find_first_interface_address eth2) ETH2_IP=$(find_first_interface_address eth0) providers: #NAME NUMBER MARK DUPLICATE INTERFACE GATEWAY OPTIONS COPY ISP1 1 1 main eth0 217.100.100.254 track,balance eth1 ISP2 2 2...

I''m planning a multi isp setup and cafully read the documentation. One thing that bothers me is the masq file. The example uses a single ip address on each public interface. I have multiple addresses on both public interfaces (16 on one and 64 on the other). I''m a bit confused about what to put in the masq file in this situation. Any insights would be appreciated. Ronald --

Hi, I''ve to restart shorewall when my dynamic IP was changed from my ISP. Of course i can with a shell script do it automatically, but the question is still there.. why ? mess-mate -- "I understand this is your first dead client," Sabian was saying. The absurdity of the statement made me want to laugh but they don''t call me Deadpan

...h0 SRC=71.203.146.136 DST=68.87.74.162 LEN=70 TOS=0x00 PREC=0x00 TTL=64 ID=0 DF PROTO=UDP SPT=32769 DPT=53 LEN=50 I set my rules, policy, masq, interfaces, etc according to the basic two-interface firewall howto, and used an FAQ to configure my firewall as follows: /etc/shorewall/params: ETH0_IP=`find_first_interface_address eth0` /etc/shorewall/rules: # # Local Rules SSH/ACCEPT loc $FW Ping/ACCEPT loc $FW # DNS DNS/ACCEPT loc $FW # DHCP SERVER ACCEPT loc net UDP 67 ACCEPT loc net TCP 67 # DHCP CLIENT ACCEPT loc net...

I''ve upgraded a 3-interface system from 2.0.8 to 3.2.6 on Debian, and I''m not able to make DNAT work anymore. If someone could offer a suggestion of where to look to fix this, it would be very much appreciated. Problem Summary: If I set DETECT_DNAT_IPADDRS=Yes, then I can''t access anything on my DMZ via DNAT. If I set DETECT_DNAT_IPADDRS=No, then **EVERYTHING**

I''ve upgraded a 3-interface system from 2.0.8 to 3.2.6 on Debian, and I''m not able to make DNAT work anymore. If someone could offer a suggestion of where to look to fix this, it would be very much appreciated. Problem Summary: If I set DETECT_DNAT_IPADDRS=Yes, then I can''t access anything on my DMZ via DNAT. If I set DETECT_DNAT_IPADDRS=No, then **EVERYTHING**

Hi All, As you probably all know :-) I''m trying to do the multi-isp thing. I''ve resolved my last issue with the route_rules as suggested by Tom and Jerry suggested. Lately I have been seeing "transient" (I say transient because the problem will persist for a while and then magically clear itself up some number of minutes later) situations where my gateway will log: