I have bought a Saphairon Speedlink 1113 and now everything is working fine. If I reboot pfsense or the modem pppoe is reconnecting directly.

I dont thin\k i did anything to stupid  ;D tried to put screen shots here but 300k is a bit of a joke would have to make 10 posts to fit them all.  Note i never get anything on the queue  screen and have waited far longer than 5 secs recommended

screenshot_13.png
screenshot_13.png_thumb

Yay, fixed now!

I'm always a genius when the person who needs help solves their own problems…    :P

I split this topic because it was a new issue unrelated to the other thread.

You might try sniffing some packets on the WAN when it claims to be updating.

It's possible that the packets are trying to go out but not actually making it to the DNS server.

Since fixing this, I have setup RFC2136 on close to two dozen firewalls and VMs and they all work well.

No, not without patches. Given the "problematic" (to put this very mildly) upstream, I'd not install any such thing anywhere. It works just fine with unbound.

Afraid 128MB of RAM will break as soon as you start blocking the IPv6 bogons.

$ wc -l /etc/bogonsv6 79175 /etc/bogonsv6

BTW, some use cases should be easy to test using hw.physmem="128M" I guess.

All good now… thanks.

All of the crashes are different (one in the filesystem code, two in different memory operations), I'd wager it's hardware.

I know there is not enough info here to debug yet. I wanted to avoid the time to do all that by describing it here first in case someone else had already bumped into this. And I haven't done anything with IPSEC yet. In fact, I haven't changed ANYTHING yet except for the upgrade. It was after upgrading that while I was testing everything out that I discovered a host on 0.0/24 couldn't ssh to a 1.0/24 host anymore. And how it was behaving was bizarre. Prior to posting this, I had read of others having some weird issues with IP alias and CARP after upgrading, but they weren't quite the same thing, but may be related. I am next going to sniff the WAN port next and see what the 0.0/24 originated packet IP layer looks like.

@bill_mcgonigle:

I have another 2.1 machine that I did not upgrade - can anybody offer advice on perhaps rsync'ing the one to the other, to get an older 2.1RC on a new machine?  I'd imagine fstab needs to be excluded, and I'll put the backup config.xml on removable media.

In case anybody else gets stuck, this worked.  I'm back on July 10th, and apparently stable.  The mini-ITX board in this router has only one slot, and all I've got on hand are 256MB DDR-2/533 sticks…

mini HOWTO:

both machines:

pkg_add -r ftp://ftp-archive.freebsd.org/pub/FreeBSD-Archive/ports/i386/packages-8.2-release/Latest/rsync.tbz rehash

source machine:

mv /root/.profile /root/profile

destination machine:

rsync -azvlSWHx --progress --delete --exclude=/etc/fstab --exclude=/var/db/rrd/ --exclude=/var/tmp --exclude=/var/yp --exclude=/var/spool -e ssh root@source.example.com:/ /

The following files failed to copy, but it seems fine anyway:

boot/loader.rc usr/bin/chfn usr/bin/crontab usr/bin/opieinfo usr/bin/opiepasswd usr/bin/passwd usr/bin/su usr/lib/librt.so.1

Oh, memory usage is at about 43% on either the current RC snapshot at boot time or the July 10 build (fairly stable over time), so I don't think it's an issue of insufficient RAM, per se.

Just curious if anyone else is seeing this particular issue?  ???

@jimp:

More recent thread here:
http://forum.pfsense.org/index.php?topic=63160.10

Ah awesome. Thanks you can merge the threads if necessary.

@kejianshi:

So, is your internet nice and laggy again?  haha

Ah yeah, about 3ms slower than localhost. I guess I'll switch back to the buggy one.  :D ;D

With further investigation i found out, that my WAN IP can be pinged normally, but user in lan cannot acces WAN.
I will try to disable multiwan, to see if problem lies there.