PfSense not routing traffic

bryanz

Should I post this to the mailing list to see if anyone there has ideas? The website says not to crosspost so I don't want any bad mojo…

hoba

Please don't do. A lot of people are active at the mailinglist and the forum as well and this always means reading things twice. Be sure that at least all the devs have read your problem here.

Btw, one last thing to try:

Reset to factory defaults
only configure the wireless WAN interface (make sure to disable block private subnets), keep all the rest at default values
test from a client behind the your pfSense's LAN to go to an IP at WAN (as it does NAT in default config no routing is needed)

If this doesn't work something must be seriously broken.

bryanz

I'll try that when I get home tonight.

I noticed on the serial console I'm getting an error on startup:
"route: writing to routing socket: No such process"
Maybe that has something to do with why it's not routing? Although the routing tables look ok, so maybe not.

bryanz

Bad news, resetting to factory defaults did not work, neither did re-flashing the CF card with a fresh image. I installed the latest version of m0n0wall and everything worked perfectly, both with and without NAT. I really like all the extra features in pfSense, so if you have any other suggestions I would appreciate them. If not I may have to settle for m0n0wall.

wdp

any updates on this one?

I am seeing the same issue on a Soekris net4801 platform
using fresh installs of two different releases:

http://system42.net/pfsense/downloads/pfSense-1.0.1-Embedded.img.gz

and

http://www.pfsense.com/old/pfSense-1.0-RC1a-Embedded.img.gz

After copying one of these images to a new CF card using physdiskwrite
and booting the image on a net4801, from the main menu I select option 1
to assign interfaces, assign sis0 to be the LAN interface, assign sis1 to be the WAN
interface, and then get this:

The interfaces will be assigned as follows:

LAN -> sis0
WAN -> sis1

Do you want to proceed [y|n]?y

One moment while we reload the settings…killall: warning: kill -TERM 638: No s
uch process
done!
route: writing to routing socket: No such process

bryanz

nope, sorry. but i'm glad to hear i'm not crazy, and this is happening to other people. m0n0wall, which pfsense is based on, worked perfectly for me. maybe we should open a bug report?

sullrich

It is not a bug. Do not open a ticket. Work with someone to get your misconfiguration fixed.

bryanz

Scott, unfortunately no one has been able to help us. Even with a fresh install and only changing the config to set the wireless card as the WAN interface we're still hosed. I have no idea why, as everything looks ok, minus the route socket error on the console. Have you seen that error in the past and do you know why it might occur?
Thanks,
Bryan

sullrich

It means you do not have a default route.

bryanz

Very strange. I get the message even though I have a default route, as shown earlier in the email string:

default 192.168.0.1 UGS 0 98 1500 wi0

Merl

hi,

i'have also a problem with the routing, my WAN interface have 212.21.69.97 and the default gateway ip is 192.168.23.8.
i'can ping the default gw very well but i dont get traffic over the gateway only if i set up a static route, for example to dns-server.
the i'can ping the dns-server but nothing more around the world.

i'work 5 years with freebsd and pf an hfsc … and i'dont understand it. the routing table look ok but the pfsense dont do it. ???

maybe someone have the same problem and know a workaround.

nice day for all ...
merl