Thank you, I have confirmed this patch fixes the issues.

Robbert

I'm using Ubuntu on all the machines.

This is the working configuration of THE_PROBLEMATIC_MACHINE:

Contents of "over-modem.sh":

#!/bin/bash ifconfig wlan0 192.168.0.11/24 route add default gw 192.168.0.1 wlan0 ifconfig wlan0 route -n

Execution output:

ceremcem@cca-peynir:~$ sudo ./over-modem.sh [sudo] password for ceremcem: wlan0    Link encap:Ethernet  HWaddr 74:f0:6d:09:91:54            inet addr:192.168.0.11  Bcast:192.168.0.255  Mask:255.255.255.0           inet6 addr: fe80::76f0:6dff:fe09:9154/64 Scope:Link           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1           RX packets:68556 errors:0 dropped:0 overruns:0 frame:0           TX packets:60755 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:1000           RX bytes:44370422 (44.3 MB)  TX bytes:15999975 (15.9 MB) Kernel IP routing table Destination    Gateway        Genmask        Flags Metric Ref    Use Iface 192.168.0.0    0.0.0.0        255.255.255.0  U    0      0        0 wlan0 0.0.0.0        192.168.0.1    0.0.0.0        UG    0      0        0 wlan0

traceroute output:

ceremcem@cca-peynir:~$ traceroute google.com traceroute to google.com (173.194.67.106), 30 hops max, 60 byte packets 1  10.12.0.1 (10.12.0.1)  16.806 ms  16.599 ms  16.457 ms 2  172.25.35.25 (172.25.35.25)  16.365 ms  16.222 ms  16.096 ms 3  * * * 4  izmr-2-2-izmr-3-4.turktelekom.com.tr (81.212.222.41)  21.540 ms  21.479 ms  21.407 ms 5  uls-2-2-izmr-2-2.turktelekom.com.tr (81.212.26.210)  35.391 ms  37.496 ms  37.396 ms 6  ms-col-2-uls-2-2.turktelekom.com.tr (212.156.102.81)  92.361 ms  82.691 ms  91.997 ms 7  212.156.102.14.static.turktelekom.com.tr (212.156.102.14)  93.065 ms  93.257 ms  93.689 ms 8  209.85.254.92 (209.85.254.92)  92.202 ms 209.85.254.250 (209.85.254.250)  86.555 ms  94.451 ms 9  209.85.255.70 (209.85.255.70)  94.415 ms  94.342 ms 209.85.255.72 (209.85.255.72)  94.304 ms 10  209.85.240.158 (209.85.240.158)  107.233 ms 209.85.240.221 (209.85.240.221)  107.157 ms 209.85.240.158 (209.85.240.158)  107.118 ms 11  209.85.250.165 (209.85.250.165)  107.020 ms  106.941 ms 209.85.250.167 (209.85.250.167)  110.486 ms 12  * * * 13  wi-in-f106.1e100.net (173.194.67.106)  104.037 ms  103.917 ms  99.949 ms

If I change the ip in that way, internet connection disappears:

Contents of "over-pfsense.sh":

ifconfig wlan0 10.0.1.11/24 route add default gw 10.0.1.1 wlan0 ifconfig wlan0 route -n

Here is execution output:

ceremcem@cca-peynir:~$ sudo ./over-pfsense.sh wlan0    Link encap:Ethernet  HWaddr 74:f0:6d:09:91:54            inet addr:10.0.1.11  Bcast:10.0.1.255  Mask:255.255.255.0           inet6 addr: fe80::76f0:6dff:fe09:9154/64 Scope:Link           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1           RX packets:70024 errors:0 dropped:0 overruns:0 frame:0           TX packets:61680 errors:0 dropped:0 overruns:0 carrier:0           collisions:0 txqueuelen:1000           RX bytes:46251309 (46.2 MB)  TX bytes:16106481 (16.1 MB) Kernel IP routing table Destination    Gateway        Genmask        Flags Metric Ref    Use Iface 10.0.1.0        0.0.0.0        255.255.255.0  U    0      0        0 wlan0 0.0.0.0        10.0.1.1        0.0.0.0        UG    0      0        0 wlan0

Here is traceroute output:

ceremcem@cca-peynir:~$ traceroute google.com traceroute to google.com (173.194.67.105), 30 hops max, 60 byte packets 1  10.0.1.1 (10.0.1.1)  2.057 ms  2.972 ms  2.846 ms 2  10.12.0.1 (10.12.0.1)  11.241 ms  11.131 ms  19.620 ms 3  172.25.35.25 (172.25.35.25)  20.677 ms  21.907 ms  21.764 ms 4  * * * 5  izmr-2-2-izmr-3-4.turktelekom.com.tr (81.212.222.41)  26.902 ms  26.842 ms  26.620 ms 6  uls-2-2-izmr-2-2.turktelekom.com.tr (81.212.26.210)  39.045 ms  29.144 ms  30.038 ms 7  ms-col-2-uls-2-2.turktelekom.com.tr (212.156.102.81)  89.296 ms  89.214 ms  89.151 ms 8  212.156.102.14.static.turktelekom.com.tr (212.156.102.14)  100.893 ms  100.825 ms  100.748 ms 9  209.85.254.92 (209.85.254.92)  100.616 ms  100.556 ms 209.85.254.250 (209.85.254.250)  100.446 ms 10  209.85.255.74 (209.85.255.74)  101.237 ms 209.85.255.72 (209.85.255.72)  106.939 ms  106.875 ms 11  209.85.240.158 (209.85.240.158)  113.903 ms 209.85.240.221 (209.85.240.221)  112.697 ms  110.949 ms 12  209.85.250.165 (209.85.250.165)  99.229 ms 209.85.250.167 (209.85.250.167)  100.491 ms 209.85.250.165 (209.85.250.165)  102.901 ms 13  * * * 14  wi-in-f105.1e100.net (173.194.67.105)  220.406 ms  222.355 ms  220.278 ms ceremcem@cca-peynir:~$

From THE_PROBLEMATIC_MACHINE, I can ping the machine and browse the gui of pfsense but I can not have the internet sites (eg. google.com).

I don't know how I could debug the problem any further… Any ideas?

Went home and tried it last night.  Everything is working as you would expect.  Thanks for the help.

This saved me bigtime today.
Just upgraded a firewall(HP Proliant with 4x broadcom) with 1.2.3 to pfsense 2.0.1 and had all kinds of problems.
Most annoying thing was that i could not SSH or HTTP at all(except for 1 time that the login screen showed, but it was so slow that I was never able to really login).
After adding the above /boot/loader.conf.local, all was well.
Tnx!

For the archives here, the current (updated) memstick image in my directory on files.pfsense.org should be working better now.

http://doc.pfsense.org/index.php/Upgrade_Guide#Changing_architecture_.2832_bit_to_64_bit_or_vice_versa.29_during_upgrade

It was a great learning experience, I have a solid understanding of troubleshooting pfSense installs and I know a bit more about partitioning for BSD!  I got it working last night routing one wireless connection into another, which was one of the tasks I wanted to try with this machine so I'm happy  :)

Jimp,

Yeah, up for 19 days now on 2.0-Release with no issues.  So reverting back to 2.0 (with no config changes at all) fixed whatever my issue was.  I suspect it might just be that combination of hardware since I have 5 other boxen running 2.0.1 with no problems.

If you'd like to investigate just tell me what you need.  I can reload that box with 2.0.1 whenever.

Thanks.

I have the exact same problem. Removing /usr/local/pkg/squidguard* followed by a reboot get things back to normal. Thanks for the tip!

Checked in a fix for this one today, too

https://github.com/bsdperimeter/pfsense/commit/b357f0a66de848ce7b840538e5499b1d2c989833

Ok, thanks!

Those must have been from quite an old version of pfSense.

Sure. I'm using pfSense for the last 5 years. I did many upgrades !!!

I didn't edit manually any alias.

Regards,

Josep Pujadas

This did the trick

http://forum.pfsense.org/index.php/topic,32017.15.html

The memstick image is the same as the livecd – it's an installer and test platform, it's not meant to be run indefinitely. It does not store the config on the drive.

I would not run on the Dev kernel in production.

Aside from being slower due to increased debugging, it is also more likely to panic if it gets into a situation it doesn't like for any touchy little reason.

Thanks both.

Check this:

http://www.pfsense.org/index.php?option=com_content&task=view&id=43&Itemid=44

What would I have done without you  :)
it worked….

much appreciated..

still dont know why using the web manual update hangs..

have a good day

@nexusN:

@cmb:

It means what it says, it can't write to /var/tmp because there is no space available on the device. That's either because there is no space (something overrunning the disk? would have to be a package) or at times a dying disk will produce that output. Check "df -h" at the console when it's happening.

Sadly I don't have another harddisk to test it out;
They are too expensive now such that I must use an old one.

While I do think it works quite well as I have been using it to store and download new data frequently.
Maybe I should check it anyway. Thanks for your advice.

Thanks for the check advice!
I am sorry for my irresponsible claim on the software,
on WD harddisk check the harddisk is found to have bad sector, and it cannot even pass a quick test.
Now I have switched to a 2.5" harddisk and hopefully I won't see the same error on the page.

Thats exactly what solved the problem! (Creating a small boot-partition)
Thanks a lot for this excellent help!!!

having the same problem