@stephenw10

Ahhh. I didn't realize this was solved. Thought OP was still having issues.

OK, turns out I couldn't ping because my ISP had to provision my router. I had to go through port by port until they could finally see my MAC address. Turns out port 6 is igb1. What a huge pain in the neck... Anyway, now I can ping.

Next, I just left the ethernet cable from my PC in one port and just changed the interface assignment for the LAN port until I found the assignment that lets me access the web gui. So port 7 is igb2 and I can access the web gui using a static IP - but I can also pull an IP via DHCP. I guess I'll repeat that until I've mapped all the ports.

Thanks for the help, everyone!

Not on Netgate hardware, pfSense Plus is included.

@Finger79 And a big thanks from me who forgot to put JPME2 back again after flashing with the same results…

Is that actually the same server you're testing against? The ping time looks different.

The default queue doesn't seem to present any restriction from what information you have given us. It wouldn't affect downloads at all since the only queue it can hit is outbound on the WAN. So you should be seeing much better than that from the firewall itself.

Right because it now is the default so you don't need to set it. You can try setting it to something different as a test if you want but I don't believe it will make any difference.

@Gertjan hi!
I don't have any these packages installed.
I have many open-vpn site-to-site and ipsec site-to-site connections (50) .

Outputs:
systat -iostat

systat -iostat /0 /1 /2 /3 /4 /5 /6 /7 /8 /9 /10 Load Average || /0% /10 /20 /30 /40 /50 /60 /70 /80 /90 /100 cpu user| nice| system| interrupt|X idle|XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX /0% /10 /20 /30 /40 /50 /60 /70 /80 /90 /100 ada0 MB/s tps|XXXXXXX da0 MB/s tps| da1 MB/s tps| da2 MB/s tps| da3 MB/s tps| pass0 MB/s tps| pass1 MB/s tps| pass2 MB/s tps| pass3 MB/s tps| pass4 MB/s tps| pass5 MB/s tps|

iostat -c 10

tty ada0 da0 da1 cpu tin tout KB/t tps MB/s KB/t tps MB/s KB/t tps MB/s us ni sy in id 0 0 11.0 12 0.1 0.0 0 0.0 0.0 0 0.0 2 0 2 3 93 0 234 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 1 0 0 3 96 0 78 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 2 0 1 3 94 0 78 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 1 0 1 2 96 0 78 15.2 66 1.0 0.0 0 0.0 0.0 0 0.0 2 0 0 2 95 0 78 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 2 0 0 3 94 0 78 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 1 0 1 2 96 0 78 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 1 0 1 4 94 0 78 0.0 0 0.0 0.0 0 0.0 0.0 0 0.0 1 0 1 4 94 0 78 10.8 55 0.6 0.0 0 0.0 0.0 0 0.0 2 0 2 5 92

@DaddyGo, actually instead of using a custom made cable for 12V supply out of PWS-203-1H psu, one can use the connected 8 pin 12v line into the 4 pin onboard connector, keeping the yellow lines at the left. One just need to use the bottom four pins of the connector. To insert the cable align the pins of the connector to pin 1 and 3 side of onboard header and just push till the point it goes in. It will not go till the bottom due to obstruction from adjacent USB header but a stable connection can be achived.

Now just the PS_On of the ATX connector to be grounded using a jumper for continous 12v supply. This is also done on the custom connector as shown by you.

Yes it's a harmless notice. It's not something we would address directly. If it gets fixed upstream in FreeBSD we will pull that in.

The 4200 shows the same thing:

uart2: <16750 or compatible> iomem 0xfe03e000-0xfe03e007 irq 16 on acpi0 ns8250: UART FCR is broken uart2: console (115200,n,8,1)

It doesn't affect the console.

Steve

@Dobby_

Yeah I just have 200mbit WAN, but pfsense runs behind another router, so that won't even be a problem, it's more the lan side where 2.5 gb will become handy later.

@sarrasine
Pretty sure they offer a free trial so you can try it out. App also does SSH, Telnet and probably a few other protocols.

@stephenw10 sent thanks!

Most of the Checkpoint hardware I've seen are Portwell/Caswell appliances so should run any x86 OS OK. I would expect that work fine as long as it's not locked down in some way.

Steve

@beerguzzle said in SG-2100 factory reset does not remove packages:

I don't find bugs, they find me.

Ha, yup I know that feeling!

@stephenw10
I'm not 'concerned' ... I just aiming for as low power waste as possible. Just min/maxing it. :)

At the downloads page: https://atxfiles.netgate.com/mirror/downloads/

@SteveITS Restoring the backed up config via the GUI did the trick, all the packages are there now 👍

Instead of uninstalling the ntopng package, I disabled it in the settings. So with that, I'm crossing my fingers that my SSDs will last longer this time :-o

@viragomann Thanks a lot!

I had to reconfigure the LAN and WAN assignements upon reboot, which was not that hard. Then the vlans had to be redirected to the new LAN. And it is working.

I do have some questions on the outcome.

My LAN interface still does not have an option for 10Gbase-T. It only has autoselect.
bba2ff40-0303-4c87-ac11-ef8923904e2e-image.png

Speeds are definetely better, but far away from 10Gbit/s.
Is this normal? Is there any other configuration I have to do to get the right intel driver for the interface in pfsense?
I was looking at CPU usage and it goes to about 9%. Once it hit 30% when running iperf3 -P 10. Which resulted in lower speeds in sum :/

I do have a high MTU set on the network adapter of the windows PC I am running as the iperf3 client. And I haven't changed anything regarding that on pfsense. I imagine that could be the reason for not reaching higher speeds. Different MTU settings?!

6e49445c-1414-4657-9c5f-cdde012df3ec-image.png

c7737fbb-bf5b-4d6b-a4ce-6bb1ec74a570-image.png

@Cool_Corona just changed those settings, it didnt seem to have any effect

@mikey_s said in Install PFSense on a Sophos SG appliance:

Like others on the XG230 Rev2 the LCD works fine, but the buttons are the wrong way round if I recall.

The SDEC driver was developed or the firebox hardware so the button order could well be different. It's possible to set the button mapping if you use a custom conf file with LCDproc. You'd probably have to start it outside of the GUI though.