Netgate 1100 - switch misconfigured?

sgw

I recently purchased 10 Netgate 1100 and set them up.

Usually I boor the device and attach a notebook to LAN to deploy a prepared config etc

One of the appliances behaves strange:

from the start the LEDs on WAN are on (even without a cable attached)
the device does not pull an IP on WAN (with cable, sure ;-) )
the device does not provide DHCP on LAN (I expect an IP in 192.168.1.0/24 on my notebook)
instead the notebook gets an IP from the upstream pfSense in my LAN

So it seems there is no NAT active and the internal switch is just ... a bridge?

I tried factory reset and a complete reinstallation (usbrecovery). No change.

The dealer told me to return the appliance. Is there something else I can try before doing so?

stephenw10

At the command line on the console try running:etherswitchcfg

That should return the current switch config. If it return 'no device' or similar that's a problem.

Try:

[24.03-BETA][admin@1100-3.stevew.lan]/root: dmesg | grep e6000
e6000sw0: <Marvell 88E6341> on mdio0
e6000sw0: multi-chip addressing mode (0x1)
e6000sw0: CPU port at 0
e6000sw0: fixed port at 0
e6000sw0: PHY at port 1
miibus0: <MII bus> on e6000sw0
e6000sw0: PHY at port 2
miibus1: <MII bus> on e6000sw0
e6000sw0: PHY at port 3
miibus2: <MII bus> on e6000sw0
e6000sw0: switch is ready.
etherswitch0: <Switch controller> on e6000sw0
e6000sw0port1: link state changed to DOWN
e6000sw0port2: link state changed to DOWN
e6000sw0port3: link state changed to UP
e6000sw0port3: link state changed to DOWN
e6000sw0port2: link state changed to UP
e6000sw0port3: link state changed to UP

You can try reinstalling the firmware. Open a ticket with us to get the image: https://www.netgate.com/tac-support-request

Steve

sgw

@stephenw10 thanks

Unfortunately:

# etherswitchcfg
etherswitchcfg: Can't open control file: /dev/etherswitch0: No such file or directory

The firmware was reinstalled already, I mentioned "usbrecovery".

sgw

filed a ticket now

edit / SOLVED: support told me to reinstall. same image as before. now things work.

stephenw10

Ah, nice! Interesting, presenting like that is not the sort of thing I expect to be resolved by a reinstall. It's possible the required loader values were lost somehow and would have been restored though.

Good result.