Default gateway not setting properly
-
I just installed pfSense and am configuring it for a transparent bridge. I have my WAN IP and gateway set in Interfaces > WAN. The LAN and WAN are bridged according to the howto I found. Only the WAN has an IP. The gateway was already populated, and I can connect to the box via the webconfigurator from my home IP.
The WAN interface is currently the only one plugged into the network, because I am configuring all the rules before plugging it inline on my network.
When I tried to look at System > Packages, I got an error about not being able to see www.pfsense.com. I got DNS just fine, so I ssh into the pfsense box and try traceroute and I get
traceroute: findsaddr: failed to connect to peer for src addr selection.
I check routing tables and I see…
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
6#.###.###.160/28 link#1 U 0 111002 fxp0
6#.###.###.170 link#1 UHS 0 0 lo0
127.0.0.1 link#6 UH 0 114 lo0There is no specific default gateway listed, despite being selected in the GUI setup for WAN.
I execute 'route add default 6#.###.###.161'
and traceroute works, and I can then access www.pfsense.org/com in the GUI.
Now my gateway shows up properly in the routing table.
Routing tables
Internet:
Destination Gateway Flags Refs Use Netif Expire
default 6#.###.###.161 UGS 0 2246 fxp0
6#.###.###.160/28 link#1 U 0 113016 fxp0
6#.###.###.170 link#1 UHS 0 0 lo0
127.0.0.1 link#6 UH 0 150 lo0Why is the default gateway not being set by pfsense properly, even though it shows in the WAN setup page? Should I have to add the default gateway to the rc files on start, or is there a fix in the GUI? Is this a known bug or am I just missing something?
Thanks for any help,
-Cameron Mandrake
-
I think I have this figured out. When I first installed I gave it an IP on another subnet, thinking I would use that IP as the management IP, since it will be a transparent bridge. The machine seemed to cache that IP number and attempted to set the wrong default gateway, which I found had failed in the logs. I removed the second IP from the configs, and the gateway, and it seems to be working now.