More corrections to Tuomo's Example

This commit is contained in:
Tom Eastep 2011-03-02 07:13:14 -08:00
parent e4e574605e
commit d7fb4e8ed9

View File

@ -1201,7 +1201,7 @@ Comcast 192.168.4.0/24 | ip -4 route add 1
default
nexthop dev ppp1 weight 2
nexthop dev ppp0 weight 1
lillycat: #ip <command>route ls provider 1</command>
lillycat: #ip <command>route ls table 1</command>
144.77.167.142 dev ppp0 proto kernel scope link src 144.177.121.199
192.168.5.0/24 via 192.168.4.2 dev eth0
192.168.4.0/24 dev eth0 proto kernel scope link src 192.168.4.223
@ -1291,7 +1291,7 @@ shorewall 2 2 - eth0 192.168.1.254 track,balance=2,optional<
<para>Tuomo Soini describes the following issue when using
USE_DEFAULT_RT=Yes.</para>
<para>He has a /27 network (let.s call it 70.90.191.0/27 from his
<para>He has a /27 network (let.s call it 70.90.191.0/27) from his
primary ISP and his secondary ISP supplies him with a dynamic IP address
on the 91.156.0.0/19 network. From the output of <command>shorewall show
routing</command>:</para>
@ -1314,7 +1314,7 @@ shorewall 2 2 - eth0 192.168.1.254 track,balance=2,optional<
<para>With this additional entry, the routing rules are as below and
traffic from the /27 is returned via ISP1.</para>
<programlisting>900: from 70.90.191.0/27 to 91.156.0.0/19 lookup nebula
<programlisting>900: from 70.90.191.0/27 to 91.156.0.0/19 lookup ISP1
999: from all lookup main
10000: from all fwmark 0x100 lookup ISP1
10001: from all fwmark 0x200 lookup ISP2</programlisting>