I think your solution is common sense unless you are a dev trying to find an issue and fix in the pfsense release.

Hi,

I think i am having the same issue.
Any chance you have figured out what was happening?

I advise you to re-install pfSense.

@kwiksilver:

If I post some logs/screenshots would that help?

It looks like a similar issue with mine, as already stated:

https://forum.pfsense.org/index.php?topic=90903.0

please perform further investigations (see again my post) and if the issue is close enough start to post there too so the experts have everything in one place.

Verifying free space on nanobsd would be utterly pointless. The entire slice is overwritten.

My point is that several people recently reported Bitten Fruit products to behave like nuts regarding DHCP. Notably when both wired and wireless was enabled on them.

Traffic logs did not show anything unusual.

ORLY? You consider renewing IP lease multiple times per second normal?  :o Find the offending device in the NDP table and unplug it. After than, you will probably need to delete the dhcpv6 leases file manually to get back to sane state.

Actually we had a need for those RFCs the last 2 weeks. A remote site in Gamgadi, Mugu was off-line for 2 weeks. The first week was town hydro power plant maintenance - no power all week and the Telecoms does not have enough solar, so no phones or internet. The second week was some internet "maintenance" thing. They had phones but no data services. It came back up yesterday.
If pfSense at least implemented RFC 1149 then we could have used an RFC 1149 backup link to get some data throughput. And with RFC 2549 we could have even given Sykpe messaging priority.
Maybe I should work on the code for it, if someone can do the hardware design of the necessary electronics<->pigeon adapters.

Just thought I would let everyone know that the upgrade from 2.1.5 to 2.2.1 this morning was problem free, took about 12 minutes using the GUI.

Thank you pfsense team.

Neil

Going to pull the drive and do a fresh install again and restore my backup to see if the do not reinstall again.

Check what is using your CPU cycles. Login to a console and at the comand line run 'top -aSH'. Leave it running for a few seconds and check the processes at the top of the table.

Steve

@phil.davis:

It's a feature  :P
https://redmine.pfsense.org/issues/4383
It has been doing this in the actual firewall log, but there was a bug in the front-end GUI code that displayed the firewall log entries. That bug meant that in previous versions the IGMP entries were not seen on the webGUI firewall log display.
With that bug fixed in 2.2.1, now this underlying issue 4383 can be seen easily.

Ok, thank you Phil. Bring back that nice bug in 2.2.2 please ;)

i'd try to install a clean 2.2.1 and then try to restore your config

@heper:

yes and hope for the best :)

And actually I fully expect you will get a good result as long as the new hardware has the same number of interfaces (or more) as the old hardware. You will just have to do the interfaces assign at the console and it should all go.

What "router" do you have from your isp.  Do you also modem?  Or do you have a gateway modem/router combo.

Pfsense meant to replace your router so it gets a public IP on its wan interface, and then you have your lan segment(s)

Typical setup could be something like this - see attached

Now you could have your lan side segments vlans all through the same switch or if you have physical like shown with say 4 nics total, you have 1 for wan, then 1 for your lan - then I would break out wifi on its own, and then you have another segment where you put stuff that you forward traffic too.  So this is pretty much isolated in its own dmz if you will.

What switch(es) are we dealing with?  Why type of appliance are you looking at for pfsense - how many nics?  I personally would make sure it has 4.  3 you could get by with, well 2 even but 4 is the sweet spot if you ask me this allows to do full physical connections at full gig speeds with our having to vlan and hairpin interfaces, etc.

typical.png
typical.png_thumb

Thanks dotdash, your suggestion worked.

I can agree with killing off insecure crap.  If it weren't for stuff like this hacking would be alot less profitable.