I try to setup the pfSense firewall behind my Belkin router with the latest image (1.2-R3-pfSense), below is my system specs;
40 GB Hard Drive
2 intel nics
The Belkin's WAN interface is setup with DHCP and the LAN interface is setup with static. The WAN interface of the pfSense firewall is setup with static IP of the LAN interface of the Belkin. Howerver, every time I boot up the system I got this error message "route: writing to routing socket: No such process". When this happen, clients behind the pfsense firewall can't access the internet. On the other hand, if I setup the Belkin router LAN interface with DHCP and setup the pfSense WAN interface with DHCP then everything works fine. Please help
GruensFroeschli last edited by
what do you mean with
"The WAN interface of the pfSense firewall is setup with static IP of the LAN interface of the Belkin."?
do you actually have on both interfaces the same IP?
What I meant to say was the WAN interface of the pfSense is setup with a static IP within the static IP range of the Belkin LAN interface, and they both have different IP.
jahonix last edited by
What's the reason for having a (more or less crappy) Belkin router in front of pfSense?
On the other hand, if I setup the Belkin router LAN interface with DHCP and setup the pfSense WAN interface with DHCP then everything works fine. Please help
On the Belkin you setup a DHCP server, right? Just to make sure.
Did you enter the Belkin toy as gateway adn DNS server in your pfSense's WAN setup? This is done automatically when assigned by DHCP.
No, I setup the LAN interface of the Belkin as static and the WAN interface as DHCP. However, I've figured out what I did wrong and I've fixed it. Thank for replying
Guest last edited by
This thread was kinda funny - in that I have sort of the same setup here - but reversed. Put PFSense infront cause I cant stand the dlink or the netgear routers. No logging capabilities which pfsense has plus more.
And at a reasonable price I might add.
cmb last edited by
That error is "normal", I'm not sure where it comes from but it's not the cause of your issues.
Is the LAN and WAN on the same subnet by chance? That won't work. Aside from that, no other issues come to mind that would cause problems in this type of setup.