@stephenw10

Hi Steve,
I can confirm that did the trick and firmware upgrade was applied.

Thanks!

The 6100 and 4100 use the i225-v Rev3 (B3) NIC chips which are not affected by that. I've never seen that sort of connection issue in any of the testing I've done.

[23.01-RELEASE][root@4100.stevew.lan]/root: pciconf -lv igc0 igc0@pci0:4:0:0: class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x15f3 subvendor=0x8086 subdevice=0x0000 vendor = 'Intel Corporation' device = 'Ethernet Controller I225-V' class = network subclass = ethernet

Steve

You should open a ticket with us, that does sound like a hardware issue.

https://www.netgate.com/tac-support-request

Steve

I think whatever went wrong with pfsense caused my ubiquity access points to crash which is why I couldn't see the SSID. Once I restored pf sense, and restarted my ubiquity devices, I could see the SSID again.

@davidylau said in Netgate 1100 can no longer update nor install apps (again):

@nguser6947 My EFI partition is 200M, so my system should be OK.

Then you should be fine, lucky you. 🤕 If you don't want to wait to install 23.01 you can reinstall from image, and restore your config, or check back in a couple weeks.

It should still be a static IPv4 address. You always want the firewall to be a static IP so you can always access it even if the dhcp server goes down.
The only interfaces you might want to be a dhcp client would be the actual WAN if it is a DHCP type.

@aaronouthier said in How to use a managed switch with VLANs with SG-1100? basket random:

@rcoleman-netgate
I think I don’t completely understand how VLAN tagging works.

In the photo above, I don’t understand what you did with the “Members” column.

My managed switch has 5 VLANs, ports 2 and 6 are untagged in VLAN1, ports 7 & 8 are untagged in VLAN 5, the rest are untagged alone in separate VLANs, and each VLAN has port 1 tagged.

I’m not clear how to interface with that in pfSense?

It sounds pretty reasonable. I will try it now.

This seems like a good time to try out my shiny new ZFS memory usage boilerplate message.

23.01 can appear to use more memory than expected if you are using ZFS for a few different reasons:

ZFS ARC (Adaptive Replacement Cache) usage is reported differently, though the behavior is similar to older versions #14011. ZFS will give up this cache memory as needed but not always fast enough for certain workloads.

To correct the memory reporting on graphs and the dashboard, install the System Patches package and then create an entry for 0d83ed084a987f3446a0cbdcf249fc5b8722726f to apply the fix.

The first boot after upgrading the ARC usage will be high from all the disk activity during the upgrade. This will gradually lower, or a reboot will make it go back to "normal".

FreeBSD default cron jobs are enabled when they shouldn't be #14016, and run at 3am causing RAM usage from ARC to jump overnight.

To correct this, install the System Patches package and then create an entry for ff715efce5e6c65b3d49dc2da7e1bdc437ecbf12 to apply the fix.

To set limits on ZFS ARC size to reduce the chance of contention for RAM, configure a tunable for vfs.zfs.arc.max to set a limit on how many bytes it can consume, e.g. 67108864 would set a 64MB limit. Also consider setting a "Free Target". Both are explained in detail on https://docs.netgate.com/pfsense/en/latest/hardware/tune-zfs.html.

A reboot is required to fully activate the changes from these patches. The ZFS ARC limit will take effect immediately but the wired memory may not be immediately freed, so a reboot is helpful for that as well.

@stephenw10 Hi Steve
(this) Linux sees all as generic sdX as long as it's block storage so it doesn't matter how it is connected. To dive into would need a /dev/disk/by-path or such, which I did not last year.

I installed the M.2 into another PC (with only an Infiniband card, so no nic at all); installed 21.05 Rescue on it, and on first boot after I put the M.2 into the SG2220 and after a few minutes the card asked for DHCP on my WAN port and reacted on 192.168.1.1/24 as expected on the LAN side.
Problem fixed so far.
Thanks for the HowTo help!
Cheers
Michael

P.S.: I wonder what fails next on this box....

@stephenw10 said in Migrating from SG-5100 to 4100:

...
It also can be difficult if you have VLANs or other sub interface types. Editing the config directly can be an easier option.
...

Steve

Thanks for the response.
Yes, I'm using three different hardware interfaces with a handful of VLANs. I'll probably open a ticket for help with the conversion.

Thanks again!

@mentisdominus
SS14 can unfortunately not be used to replace DZ3.

Schottky diodes like SS14 are designed to conduct current in one direction already at a low voltage whereas TVS diodes like SMAJ13CA are designed to only conduct current when a high voltage is present across it (a voltage that is so high that it should never be seen during normal conditions).

I have been running my SG-1100 without DZ3 fitted for some time, but this leaves the device unprotected against defective or wrong power supplies as stephenw10 points out.

Thank you @bigsy. One rj45 crossover patch after, problem resolved :)
As Auto-MDI-X is in the 1000BASE-T standard (ref), i've not tried that...

@richa99 said in Netgate 1100 and ONT:

SG1100

The 1100 is a router. Is there a reason you want another router behind it?

You can connect the 100 to the ONT and it'll work.

@arri That’s how I read that too.

@viragomann
Ahh, I've got you. I will give that a try.

☕️

All
For what it's worth, I just thought I would share my experience of my SG1100 failing to boot after a local power outage 2 days ago. After power was restored to the house, the SG1100 power LED came back ON, but with no activity on the console & the boot LED was OFF.

After six attempts at power cycling the device, only once did it actually boot.
So I took a punt at putting a voltmeter across the connector of the 12v power supply while off load and the reading was 11.8v. Decided to swap out the PSU for a equivalent 12v / 2A spare I have. The spare gave a voltmeter reading of 12.2 volts.

Connected the replacement PSU to the 1100 & it booted first time. Has been working just fine ever since even after several halt commands/power cycles.

I'm impressed with the resilience of my two year old 1100.

@dominikhoffmann See https://forum.netgate.com/topic/177872/sg-1100-black-diamond-led-always-off-in-23-01/

@stephenw10 Thanks Steve. 👍

To close the loop: disabling VLAN_HWFILTER on the igb port solved the issue.

Put this in Early Shell Command using the Shellcmd package:

/sbin/ifconfig igb0 -vlanhwfilter -vlanhwtso

I can now get a DHCP address on the igb0 WAN port from the Azores Networks WAG-20D ONT.

@thatguymark said in Netgate 2100 update to 23.01 from 22.05 issues:

In the process of trying to install some packages on my Netgate 2100, I was prompted to update the firmware to 23.01.

Don't install packages if a later version is detected/offered. Select Previous Stable in the update branch, so you're installing 22.05 packages on 22.05. (that said, 22.05 repos are offline temporarily, but it sounds like you already upgraded)

@thatguymark said in Netgate 2100 update to 23.01 from 22.05 issues:

CPU usage is all but maxed out

Was one package pfBlockerNG? There was a bug in an initial 3.2 release when TLD Wildcard blocking was enabled in DNSBL settings. Resolved in a package update that was probably after your post.