search for: find_interface_address

...dited my shorewall/masq file as such: eth0 eth1 12.34.56.78 or should it be? eth0 10.0.0.0/24 12.34.56.78 First, is this all that is necessary to properly start using SNAT? I was unsure whether I should use ADD_SNAT_ALIASES=yes also or instead or not. Second, if I have ETH0_IP=`find_interface_address eth0` in my params file, I can have eth0 eth1 $ETH0_IP in the masq file, correct? The commented help in the params file doesn''t name masq as one of "the other configuration files." Third, using SNAT didn''t seem to make any difference. Any other suggestions?...

Hello Shorewall list, I''m a happy Shorewall user since a few years now and everything works fine for me except one thing that I try to implement since a week, the multi-isp. I''ve downloaded the 2.4.0 Stable release yesterday and tried the RC2 since a week. My config is a Debian running a kernel 2.4.27 home made with the CONNMARK.diff patch applied I''m using 2 ISP,

I''ve installed Shorewall 3.0.5 on a Debian Sarge box, and I''m attempting to route internet traffic through a couple of ISPs, and I''ve come up against some problems. The first is that one of my links is a pppoe connection to a wireless modem, and I can''t configure it to have a static IP address... therefore I can''t see how I can set up the two

I have two feeds, one with a static IP and one with a dynamic IP. How can I configure a Multi-ISP setup with the dynamic IP, or can I? I don''t think the gateway will change, just the interface IP. -- Chris Mason NetConcepts (264) 497-5670 Fax: (264) 497-8463 Int: (305) 704-7249 Fax: (815)301-9759 UK 44.207.183.0271 Cell: 264-235-5670 Yahoo IM: netconcepts_anguilla@yahoo.com --

...40 RES=0x00 SYN URGP=0 Nov 28 18:16:24 all2all:REJECT:IN=eth0 OUT= SRC=192.168.0.8 DST=203.113.232.72 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=38322 DF PROTO=TCP SPT=33669 DPT=9176 WINDOW=5840 RES=0x00 SYN URGP=0 interfaces: net ppp0 - dhcp,routefilter,norfc1918 loc eth0 detect params: ppp0_ip=`find_interface_address ppp0` policy: ############################################################################### #SOURCE DEST POLICY LOG LEVEL LIMIT:BURST #loc net ACCEPT # If you want open access to the Internet from your Firewall # remove the comment from...

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**

...qt ip rule del fwmark 1 + echo qt ip rule del fwmark 1 + eval qt ip rule del fwmark 1 ++ qt ip rule del fwmark 1 ++ ip rule del fwmark 1 + ensure_and_save_command ip rule add fwmark 1 table 1 + eval ip rule add fwmark 1 table 1 ++ ip rule add fwmark 1 table 1 + echo ip rule add fwmark 1 table 1 ++ find_interface_addresses eth0 ++ ip -f inet addr show eth0 ++ grep inet ++ sed ''s/inet //;s/\/.*//;s/ peer.*//'' + for address in ''$(find_interface_addresses $interface)'' + run_and_save_command qt ip rule del from 200.173.215.82 + echo qt ip rule del from 200.173.215.82 + eval qt ip rul...