search for: findgw

...New Features in Shorewall 4.2.10 1) Shorewall''s suppport for dynamic gateways on interfaces managed by dhclient works on OpenSuSE systems but not on some other distributions. In order to generalize support for learning the gateway for dynamic interfaces, a new ''findgw'' extension script (user exit) has been added. The exit will be invoked in a function that has a single argument: $1 = <name of an interface> If the function can determine the gateway for the passed interface, it should write the gateway to standard out. Her...

.../shorewall/firewall script has the function detect_dynamic_gateway that detects the gateway based on the leases file. The code in the function is: detect_dynamic_gateway() { # $1 = interface local interface interface=$1 local GATEWAYS GATEWAYS= local gateway gateway=$(run_findgw_exit $1); if [ -z "$gateway" ]; then gateway=$( find_peer $($IP addr list $interface ) ) fi if [ -z "$gateway" -a -f ${VARLIB}/dhcpcd/dhcpcd-${1}.info ]; then eval $(grep ^GATEWAYS= ${VARLIB}/dhcpcd/dhcpcd-${1}.info 2> /dev/null) [ -n &q...

I think we discussed this in the past and I floated a hack at the time, but I don''t recall any real resolution. I want to see if time has solved my problem or if it still exists. My scenario is that I have two ISPs, one of which uses DHCP. Because I have two ISPs, history has shown that allowing the provisioning script for the interface to plumb a default route is troublesome and

...Shaping traffic bound for your local net flow=dst These will cause a ''flow'' to consists of the traffic to/from each internal system. 2) In order to generalize support for learning the gateway for dynamic interfaces, a new ''findgw'' extension script (user exit) has been added. The exit will be invoked in a function that has a single argument: $1 = <name of an interface> If the function can determine the gateway for the passed interface, it should write the gateway to standard out. Her...

While troubleshooting my MultiISP box, I suspect I might have found either a bug or an incompatibility with CentOS 5.2. In prog.header (function detect_dynamic_gateway), Shorewall tries to look for: /var/lib/dhcp/dhclient-${1}.lease However (at least under CentOS 5 - unknown about other OSes), this should be: /var/lib/dhclient/dhclient-${1}.leases (different path, and "leases"

Hi, I have a multi-isp configuration both on ppp interfaces. As one of them is 32Mbit/s and the other is 8Mbit/s , I have a weight setting of 4 to 1 as in the following providers file entries: vdsl 1 0x10000 - ppp1 - track,balance=4 adsl 2 0x20000 - ppp0 - track,balance=1 I would also like to have fallback between them so that if one is

...onfigured with a broadcast address. 2) Due to a syntax ambiguity arising from the new dynamic zone implementation, ''shorewall show dynamic'' produced no output. It now shows the contents of the dynamic blacklist as in earlier Shorewall releases. 3) The ''findgw'' script produced an error if VERBOSITY > 0. ---------------------------------------------------------------------------- K N O W N P R O B L E M S R E M A I N I N G ---------------------------------------------------------------------------- None. -------------------...

...onfigured with a broadcast address. 3) Due to a syntax ambiguity arising from the new dynamic zone implementation, ''shorewall show dynamic'' produced no output. It now shows the contents of the dynamic blacklist as in earlier Shorewall releases. 4) The ''findgw'' script produced an error if VERBOSITY > 0. ---------------------------------------------------------------------------- K N O W N P R O B L E M S R E M A I N I N G ---------------------------------------------------------------------------- None. -------------------...