Interface Add Button Missing

[oznet]

Under interfaces the add button is missing? I want to add an IoT and create a 172.16.16.0 for IoT devices.

It was there now its gone, rebooted 2100 same thing?

Why?

[patient0]

@oznet there is never an add button but an assign button on this page. And if you don't see one then there is not interface that is not assigned.

May have a read in the doc: https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/configuring-the-switch-ports.html

[stephenw10]

That^. You only see the assign button if unasigned interface exist to assign. So first create the VLAN on mvneta1.

[oznet]

@stephenw10 Why do I need to do anything with a Vlan, I just need to create an interface called IoT and apart from my 192.168 network I just want to create a 172.16 network for IoT devices and then use Avahi to restrict and allow cross traffic?

So are you saying I need need create a vlan to get the add button back?

[stephenw10]

You would use a VLAN interface to separate the IoT subnet from other devices. You can use the switch config to provide the subnet directly on one of the LAN ports. The VLAN only exists internally but on the assignments page that's what you would see. As in the example @patient0 linked to above.

[oznet]

@patient0 said in Interface Add Button Missing:

https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/configuring-the-switch-ports.htm

Ok thanks I created a vlan called it IoT and plugged the laptop into port 4 set up the Iot dhcp server and specified the ip address 172.16.1.1 and I can ping that from my 192.168 which is good. I then setup a static map of the laptop mac address on the IoT dhcp server and assigned a 172.16.1.80 but it never gets that address.

I have 11 Iot devices and just want to get the laptop Dell XPS 13 getting the 172 address and then use avahi to prevent the 172 address from getting to the 192 address but allow 192 space to get to the 172 space. I have not done anything with the ports.

Also set up a rule etc as per this video from Lawrence Systems.
https://www.youtube.com/watch?v=HW9mUrF1ZgU

[SteveITS]

@oznet it sounds like you want
https://docs.netgate.com/pfsense/en/latest/solutions/netgate-2100/opt-lan.html#isolated

If you set a static IP on the laptop does it work?

And to be clear you’re not setting a VLAN on the laptop right?

[luckman212]

I'm having deja vu from yesterday...

[stephenw10]

So other IoT devices are receiving dhcp leases in the correct subnet? Or nothing is?

Does the laptop get a dynamic lease if you don't have the static mapping in place?

I assume 172.16.1.1 is the local IoT interface address in pfSense? Pinging that from something in the LAN subnet doesn't pass the switch/VLAN setup so that could still be problematic.

[stephenw10]

Oh missed some posts! Yeah that other thread tells a story. Almost certainly a switch config issue.

[luckman212]

@oznet repeating this from the other thread: "Send screenshots of your Marvell 6000 switch config (all 3 tabs)"

For reference I am talking about this (example below is from one of my 2100s):