2.1.5 -> 2.2.2: Default Route Wrong
-
I am attempting to upgrade from pfSense 2.1.5 to 2.2.2. After applying the upgrade, I can no longer talk to the Internet. This happens whether I use the auto-update feature, or if I perform a fresh install and restore my config.xml.
After poking around, it seems like it's setting the default route incorrectly. Under 2.1.5, my routing table looks like this. As you might guess, the LAN interface is em0; the WAN interface is bge0:
$ netstat -rn Routing tables Internet: Destination Gateway Flags Refs Use Netif Expire default 173.228.113.1 UGS 0 175 bge0 10.0.0.0/16 link#1 U 0 344 em0 10.0.0.1 link#1 UHS 0 88 lo0 10.3.0.0/16 link#7 U 0 0 em0_vl 10.3.0.1 link#7 UHS 0 0 lo0 127.0.0.1 link#5 UH 0 63 lo0 173.228.113.0/24 link#2 U 0 44 bge0 173.228.113.XXX link#2 UHS 0 0 lo0 [ ... ]After performing a fresh install of 2.2.2 and restoring the 2.1.5 config, my routing table becomes this:
$ netstat -rn Routing tables Internet: Destination Gateway Flags Netif Expire default 10.0.0.1 UGS em0 10.0.0.0/16 link#1 U em0 10.0.0.1 link#1 UHS lo0 10.3.0.0/16 link#7 U em0_vlan 10.3.0.1 link#7 UHS lo0 127.0.0.1 link#5 UH lo0 173.228.113.0/24 link#2 U bge0 173.228.113.XXX link#2 UHS lo0 [ ... ]Everything else looks correct, but the default route is clearly nuts. In both cases, the WebGUI correctly shows WANGW as 173.228.113.1, so I can't understand why it's selecting the LAN interface for the default route.
What might I have messed up?
-
Interfaces LAN et WAN (em0 and bge0) got swapped ?
-
Interfaces LAN et WAN (em0 and bge0) got swapped ?
I don't think so. Both still have the correct IP addresses, the WAN's gateway has the correct WANGW IP address, and the LAN's gateway is set to "None," as the instructions on that page dictate.
-
So, no clues, then? Should I file a bug?
Normally I'd just go, "Meh," and set everything back up from scratch, except that I have a long-ish list of static DHCP assignments for the LAN that I'd rather not have to type in again.
-
Interfaces LAN et WAN (em0 and bge0) got swapped ?
I don't think so. Both still have the correct IP addresses, the WAN's gateway has the correct WANGW IP address, and the LAN's gateway is set to "None," as the instructions on that page dictate.
Are those actually assigned to WAN and LAN properly? Look at the Interfaces - Assign screen.
-
Normally I'd just go, "Meh," and set everything back up from scratch, except that I have a long-ish list of static DHCP assignments for the LAN that I'd rather not have to type in again.
Set up by hand and then do a restore, selecting ONLY DHCP settings … from your config.xml ;)
-
Interfaces LAN et WAN (em0 and bge0) got swapped ?
I don't think so. Both still have the correct IP addresses, the WAN's gateway has the correct WANGW IP address, and the LAN's gateway is set to "None," as the instructions on that page dictate.
Are those actually assigned to WAN and LAN properly? Look at the Interfaces - Assign screen.
Just reloaded 2.2.2 to check: Yes, the WebGUI reports both interfaces assigned properly – bge0 is WAN, and em0 is LAN.
-
Set up by hand and then do a restore, selecting ONLY DHCP settings … from your config.xml ;)
I didn't know you could selectively restore bits of the config. If this problem persists, I will definitely check that out.