Messages

1

23.1 Legacy Series / VNStat hasn't been working for months, any fix or alternative?

« on: May 31, 2023, 07:55:56 pm »

It's been quite a while now that VNstat hasn't been working, showing blank tabs. Others have reported the problem but there doesn't seem to be much traction on it, granted it's not anything critical.

Is there an alternative to it that would give daily/monthly stats?

2

General Discussion / Re: DHCP not working for new VLAN

« on: February 04, 2023, 11:48:17 pm »

They were actually added to the lag, I just didn't remember since I did this a while ago, and going to Port Membership and switch to lag to see the settings and change them, instead of Port to VLAN just didn't occur to me at all...

3

General Discussion / Re: DHCP not working for new VLAN

« on: February 04, 2023, 11:12:51 pm »

Well you were right about the setup, just was the wrong place. Port to VLAN doesn't allow changing anything, you have to go to Port VLAN Membership and there you can select the LAG and assign the tagged VLAN. Ugh, I'm not sure why they don't allow the other option and I didn't think to look at that one.

Thank you for you patience and pointing me the right way, appreciate it!

4

General Discussion / Re: DHCP not working for new VLAN

« on: February 04, 2023, 08:33:58 pm »

Look at the screenshot, you can't tag anything on the LAG, the VLAN is tagged when it reaches the port it's connected to, not the LAG. The LAG simply forwards the packets.

5

General Discussion / Re: DHCP not working for new VLAN

« on: February 04, 2023, 07:11:59 pm »

You can't tag anything on the LAG and the other VLANs work as is, the LAG only passes things through.

I tried also access instead of trunk, with the same result. You can see that port 16 is setup as trunk and works perfectly. If I swap 1 or 15 to VLAN2 it will also work. None of the VLAN 3 tagged or otherwise, work.

6

General Discussion / Re: DHCP not working for new VLAN

« on: February 04, 2023, 06:12:12 pm »

17/18 are setup as LAG and go to the router. You can see on the very first picture they all have the parent as lagg0

7

General Discussion / Re: DHCP not working for new VLAN

« on: February 04, 2023, 04:12:19 pm »

The firewall rules have very little, currently only the DHCP and an Allow All for testing purposes.

I can't indeed exclude something malfunctioning on the switch, but I know the configuration is correct as, like I said, it works when testing the other 2 working VLANs.
If I plug on Port 16, I get an IP from VLAN 2. If I plug on port 15, no IP.
Port 8 is my wifi, 1733 is the guest VLAN which works as intended, tagging VLAN 3 does not work.

8

General Discussion / Re: DHCP not working for new VLAN

« on: February 04, 2023, 05:46:04 am »

I did.

If I switch to VLAN 2 Untagged on the port, it picks up the IP immediately, but if I put VLAN 3 it just times out. Also tried on my AP, which is what I was trying to originally do, configure a VLAN for IoT and after it was failing, i went and plugged a laptop directly to the port.

If other VLANs didn't work, I would point at the switch, but both my wifi guest (VLAN 1733) and VLAN 2 work without any issues, which makes me point to Opnsense

9

General Discussion / DHCP not working for new VLAN

« on: February 04, 2023, 01:47:23 am »

Hello,

I already have 2 VLANs that are working perfectly and have been for quite some time. Today I've been trying to add a third one to no avail, it does not get any IP.

I connected a laptop directly on the switch's port (SG200) and if I switch to VLAN2 on that port, I get the IP as expected, when I set VLAN3 on it, it just times out.

I checked the rules and compared with the working ones and nothing seems out of place. I even redid everything from scratch using a different VLAN number but it just doesn't work at all.

Any input would be appreciated!