diff --git a/docs/MultiISP.xml b/docs/MultiISP.xml index 5fe940cba..e799362e2 100644 --- a/docs/MultiISP.xml +++ b/docs/MultiISP.xml @@ -119,7 +119,7 @@ ISP. as in the following diagram. - + @@ -342,6 +342,33 @@ may try to use those stale files to determine the gateway address. + If Shorewall is unable to detect the gateway, it is likely + because you are using a DHCP client that Shorewall doesn't + natively support. You can work around that issue by using the + findgw extension + script. + + For example, these examples from Mika Ilmaranta, work with + RHEL7-based systems with nmcli: + + nmcli --terse --fields IP6.GATEWAY device show ${1} | cut -f2- -d':' # IPv6 + +nmcli --terse --fields IP4.GATEWAY device show ${1} | cut -f2- -d':' #IPv4 + + + This one from PGNd works on OpenSuSE running wicked: + + svc_status=$( systemctl is-active wickedd-dhcp4.service ) + +if [ $svc_status == 'active' ]; then + data="/var/lib/wicked/lease-${1}-dhcp-ipv4.xml" + if [ -f $data ]; then + gateway=$( xml_grep 'gateway' $data --text_only ) + echo $gateway + fi +fi + The GATEWAY may be omitted (enter '-') for point-to-point links. @@ -2480,7 +2507,7 @@ exit 0 on ursa that I will describe here. Below is a diagram of our network: + fileref="images/Network2008a.png"/> The local wired network in my office is connected to both gateways and uses the private (RFC 1918) network 172.20.1.0/24. The Comcast @@ -2651,7 +2678,7 @@ wlan0 192.168.0.0/24 The network is pictured in the following diagram: - +
IPv4 Configuration