I added a second, non-default gateway to my pfsense box, and on
reboot, the supposed-to-be non-default gateway ended up as the
default gateway.
I'm running 2.0-RC1 (i386) built on Sat Apr 23 22:59:02 EDT 2011.
The gateways section of my config file looked like this:
<gateways>
<gateway_item>
<interface>wan</interface>
<gateway>11.22.23.129</gateway>
<name>pullman</name>
<weight>1</weight>
<descr><![CDATA[pullman default gateway]]></descr>
<defaultgw/>
</gateway_item>
<gateway_item>
<interface>opt2</interface>
<gateway>33.44.150.33</gateway>
<name>tofront</name>
<weight>1</weight>
<descr><![CDATA[gateway to front]]></descr>
</gateway_item>
</gateways>
And "netstat -nr" on the firewall showed 33.44.150.33 as the
default gateway:
Destination Gateway Flags Refs Use Netif Expire
default 33.44.150.33 UGS 0 2447 em5
10.3.1.0/24 link#2 U 1 5477 em1
10.3.1.1 link#11 UH 0 0 vip1
10.3.1.2 link#2 UHS 0 0 lo0
11.22.23.128/26 link#1 U 0 58642 em0
11.22.23.132 link#15 UH 0 0 vip5
11.22.23.133 link#1 UHS 0 0 lo0
11.22.23.135 link#12 UH 0 0 vip2
11.22.23.136 link#14 UH 0 0 vip4
11.22.23.137 link#13 UH 0 0 vip3
11.22.23.138 link#16 UH 0 0 vip6
11.22.75.248/30 33.44.150.33 UGS 0 13 em5
33.44.150.32/30 link#6 U 0 57734 em5
33.44.150.34 link#6 UHS 0 0 lo0
127.0.0.1 link#7 UH 0 131 lo0
192.168.1.0/24 link#3 U 0 12 em2
192.168.1.1 link#3 UHS 0 0 lo0
(I obfuscated the real first two octets on the public addresses.)
Anyone seen anything similar, or is this a known issue, or is it
fixed in a more recent build?
Thanks very much!
John
jsell...@syonex.com
---------------------------------------------------------------------
To unsubscribe, e-mail: support-unsubscr...@pfsense.com
For additional commands, e-mail: support-h...@pfsense.com
Commercial support available - https://portal.pfsense.org
