@PiBa:

"All traffic to the interfaces IP should be blocked" when coming in on THAT interface and not from its own subnet.

Yes, that applies to traffic sourced on that interface. Sounds like that traffic was sourced from a different interface.

We understand "why" now, and will develop a fix.

After update number of processes is constant ;)
Also ps -auxww gives me one instance.

It will forward all subdomains too. Guessing it's probably external in that your forwarded target server didn't reply as you expected.

@jimp:

OK, I added that as a note to https://redmine.pfsense.org/issues/5667, we'll get that fixed up though it may be next week due to the holiday.

Understood and thanks for the workaround. Happy holidays!

changing mac they might not risk but changing ip is fairly easy

Note that it doesn't install new compiled code, so you'll probably want to update as well

@jdillard:

this is something best left to implement in pfSense 3.0 using, say, React.

Shhhhh!

:)  :-X  :) :)

Problem fixed. I'm not sure how it happened but I guess when I upgraded from 2.2.6 to 2.3 Alpha a IPsec tunnel that I had disabled was re-enabled and since I didn't have the other end configured the tunnel didn't come up. I guess IPsec tunnels take precedence over OpenVPN tunnels even if the route is not available.

LFCavalcanti,

Here is the path to the files for pfSense 2.3 / Squid:
https://github.com/pfsense/FreeBSD-ports/tree/devel/www/pfSense-pkg-squid

Gitsync and try again

PR has been merged. Thanks for the detective work. Seems PHP always has a new quirk up its sleeve :)

https://github.com/pfsense/pfsense/commit/9ba351c17e4c85e01832e38b6ba7b6a7898a290d
I put that code back in guiconfig.inc but it did not magically start working again.
Renato made the change, so I guess he will know more quickly what is going on.

The title says "resolver" and the text says "forwarder". You need to put the override in the same DNS thing that you are running.

@cmb:

New snapshots including that fix are out, please try and report back.

On my "spot", i got about 120 simultaneous connections and it's working fine. I think it's solved, but could someone with big numbers give us more reports ?

Thanks
  JC Bilhega

@maverick_slo:

Hello!

dpinger displays correct IPv4 gateway status but IPv6 is always pending.
I tried ping my monitor IPv6 from the box and it works.

BR,
Greg

me too.

Thanks for pointing that out. I completely missed that.

Will try when i get home, but its very likely ive scp'd into the wrong dir at one point over the last couple of days while debugging a different issue.

yep, its official, i fckdup ;)

Fixed via PR

don't really know what would be different or interesting list of packages:
arping
pfblockerng
snort

havent looked at interfaces page in awhile and its not configured on the dashboard

i will poke around and see if i can find a trigger

@pyrodex:

Split DNS isn't an option when you have multiple ports being forward to different devices.

Sure it is… Just use different hostnames for different devices. Kinda normal design.