Make sure you have working console access, in case you accidentally remove all network access to the WebUI.

@mke said in SG-4860 - throughput question:

I was able to get something close to ideal like 960, 970.

I doubt that. Even in perfect "lab" conditions, max thruput on 1Gbe Ethernet (without using jumbo frames) is ~941Mbps. You can read more on that here. I've never seen anything higher than that in my testing. The good news is I have been able to hit 940 very reliably when I run Ookla speedtest on a 1G fiber line w/ Netgate 4860 & now 5100.

Let me know how that WiFi project works out! Always wanted to try this in my 4860.

Not exactly what you were asking for, but check out my script here if you're interested in getting notifications when updates are available.

At the Global Support Desk, we have seen temps closer to lower 70's; with out issues. The Plate on the bottom is the heat sink, as long as there is air flow under the unit, you should be ok.

Hello,
Our official policy is listed here:
https://www.netgate.com/support/product-lifecycle.html

I would encourage you to open a ticket with our sales team fpr any questions you might have, sales@netgate.com(dot)com

First thing to try is a different USB stick and/or a different USB port. The error suggests that it is unable to mount the installation media, so it's likely a problem with that. Might be some combination of that particular memstick+port that FreeBSD doesn't care for on that hardware.

Yeah I run ntp stratum 1 server on pi 3.. And it part of ntp pool both ipv4 and ipv6

Just cost a few bucks for the hat, and some setup time..

Did that. Thank you.

Mmm, interesting point. I've not seen any issues with the velcro fastenings I've used but whilst they are in rack-mount boxes they are not actually rack mounted, they do not run hot.

Steve

@ltl_off Can you open a ticket at https://go.netgate.com Thanks!

Can you open a ticket at https://go.netgate.com?

Thanks!

Thanks, after some playing around, that setting actually fixed things for us. Thanks for the reply!

I have resolved the issues by rebooting the SG1000. I can now ping and connect to devices in the Untagged VLAN.

PING 10.1.50.2 (10.1.50.2): 56 data bytes
64 bytes from 10.1.50.2: icmp_seq=0 ttl=64 time=0.801 ms
64 bytes from 10.1.50.2: icmp_seq=1 ttl=64 time=0.457 ms
64 bytes from 10.1.50.2: icmp_seq=2 ttl=64 time=0.401 ms

--- 10.1.50.2 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 0.401/0.553/0.801/0.177 ms

It's better to create a ticket on go.netgate.com and describe your problem

Peter,

I'm glad you are all set. Enjoy your firewall!

Cool. Thanks again for the help guys.

Merry Christmas!! 🎄

I've recently purchased and configured from scratch my first pfSense box using the MBT-4220. It's been running well for about a week now and I'll have a few weeks further to evaluate it and tweak it. This MBT-4220 is a great replacement for a quite old FreeBSD system I've not upgraded in years.

For home use this is more than adequate and meets my needs:

DHCP pools and static mapping OpenSSH user shell OpenVPN connection for family mobile devices traffic mapping using ntopng
*Queing
*Squid/squidguard

Many of these things I configured by hand in the past but now have everything in a nice little box. Wifi access is provided by a separate wifi router.

I've read about replacing the fan with a heat sink so I'm investigating that as a possible upgrade.

For home the cpu runs 4-10% depending on activity and ntopng. Load averages are about 0.24 with a video stream running. Temperature with the fan is about 38-40°C.

Configuring OpenVPN for my family's phones and PCs is pretty simple. It's been good to add squidguard on the OpenVPN interfaces so I can filter out the trackers and ads (and other unwanted content).

Thank you, Derelict, for your suggestion. Support was able to help me.
-Fred

@mhab12

I think this might be it (can't reach the DNS servers). I swapped the 3.1 modem for a 3.0 modem I had used for a long time with no problems. So far the problem has ceased. I was actually hoping it would be the modem, but the behavior from pfSense is well uhm, a bug if you ask me. You're trying to work out a problem and pfSense just contributes to the problem.

Well thanks all for replies.

Yes, I could ping. Yes it was a rapid reply. I did not ssh into the box. Once the above appeared to solve the problem I did not want to go back to the old modem since it seems clear (for now) the problem is not with pf Sense.

Regards,
Barry