Yeah, that is a router. It might have a modem in it but if you're able to disconnect the WAN cable form there and it works in pfSense it probably doesn't. The actual modem is whatever's on the other end of that cable is the modem. You are replacing that router with pfSense so you need a switch on the pfSense LAN side to connect other devices. Steve

@viragomann RDP is allowed via the firewall. When enabling it, it seemed to do it automatically. Same issues on linux machines also.

I would highly suggest you use HA proxy and not use Squid for anything.

solved All done from the web gui Brand new install (with intel NICs) Restore old configuration (Realtek NICs) Pfsense will whinge that your interface assignments are incorrect. DO NOT REBOOT at this stage go to Interfaces | Assignments | PPPs edit the Link Interface to the Intel NIC repeat for VLANs Now Pfsense will ask to reboot - do it - now it works!

@Gertjan You wouldn't happen to have a Redmine account would you?

@stephenw10 Thanks, Steve!

@jimp said in Editing Aliases open wrong aliases: If you are on 23.01 and have applied the alias sort order fix patch in the System Patches package, then you'll need to update the system patches package again and apply one more fix from the list there. See also: https://redmine.pfsense.org/issues/14015 https://forum.netgate.com/topic/178813/problem-with-change-in-aliases-list-sorting-redmine-14015 You're a lifesaver :)

@viragomann You gem of a person! Seriously, I need to take myself outside for a vigorous uppercut - I completely overlooked that parameter! Thank you!!!!

@jimp My problem is that my customers are using pfSense internal user database and from my RADIUS server, there is no way to verify user’s password…

Right. If you have a virtual environment requirement that justifies larger hardware like that then it's an easy choice.

@stephenw10 I appreciate the confirmation of the values. I’ll try again soon.

@michmoor said in [Negate 6100] No logging post 23.01 upgrade: @stephenw10 Nope no error. I still think it’s package related perhaps. Suricata alerts I get a syslog entry. EVE json logs are not generated and not sent to pfsense syslog. Probably just similar to this then but as you say that code will all be in the package. Better to open a new thread for that in the IDS/IPS section.

@jimp Wow I knew nothing about this patches system ! It's nice. I just did what you said. I learned many new stuff about my pfsense today, thanks to you ! I love it even more :D Thank you !

@stephenw10 Staples has nothing on Netgate in the "That was easy" department. :) 10 mins to get the image, 5 to find a usb stick and burn it, maybe 20 total to install 23.01 to a different mSATA and restore the old config. Yep, half hour total. Good job. Thanks.

@mauro-tridici The path ends up being like this: packet goes out from 192.168.120.111 to 192.168.120.1 192.168.120.1 sends the packet to 172.16.3.10 The PC at 172.16.3.10 doesn't need to use a gateway, it knows how to talk to 192.168.120.111, because it's on that network, so sends a response out from 192.168.120.10 to 192.168.120.111 192.168.120.111 is not listening for a reply from 192.168.120.10 so ignores it

Mmm, run sockstat and see what's using port 80. I assume you moved the webgui to 8180? If you've installed some 3rd party package though anything is possible!

@Gertjan Do you know what token I should use here ? https://github.com/pfsense/FreeBSD-ports/blob/487258ae7cbd1039621b5dc5ac625f23d5519f39/security/pfSense-pkg-acme/files/usr/local/pkg/acme/acme_command.sh#L96 Where I can find it?

If you run that script it enables that option, so you would see it checked after no matter what it was before. Look in the config history to see what changed in the configuration when you ran the script. Do a diff from the version before to that version and see what it altered.

https://redmine.pfsense.org/issues/13983

Somehow Virtual IP of WA2 was created. Just removed it and all back to normal Thanks!