Flint 1, eth ports seems isolated after enabling vlan

Hello

I have a Flint 1 and I have a home lab with proxmox and many MV so I decided to start in the great world of the vlan tagging :slight_smile:

I’ve read manuals and I’ve seen some videos so I’ve decided to create my first vlans with no luck :slight_smile:

The most important thing was not to break the LAN, so I decided to create a single VLAN (VLAN 1) on all the Ethernet ports and check that everything was still working.

The result was that everything I plugged into the ports obtained an IP address and could browse the internet, but even though they were on the same VLAN, the devices couldn’t see each other. I couldn’t even ping them, nor access the services they expose on ports 80 and 443.

If I disable the VLAN, everything works fine. If I enable it, the devices can’t see each other.

I’m going to share the configuration to see if you can tell me what I’ve done wrong or what I’m missing.

I’ve looked for port isolation options or something similar, but I haven’t been able to find anything.

LuCI Web UI:

  1. Network > Interfaces > Devices.
  2. br-lan and click “Configure”.
  3. “Bridge VLAN filtering” tab.
  4. Check “Enable VLAN filtering”.
  5. Configure VLAN 1 (LAN)
  6. Click “Save”.

As far as i know, with this config, all eth ports are in the same vlan (vlan1) and all ports can manage untagged packets, treating them as vlan 1 packets.
Summing up, all devices should be in the same vlan and work as when there were in the LAN.

After that, I modifed the LAN interface in order to asociate with the new vlan.

LuCI Web UI:

  1. Network > Interfaces.
  2. Edit lan Interface:
  3. “General Settings”, “br-lan.1”.
  4. Click “Save”.

After that Save and Apply.

Do I missing something?

Thanks in advance.

1 Like

Bu the way. My FW version is 4.7.0

Thanks again

Hi

Please try upgrading the AX1800 firmware to the latest v4.8.3 beta and test again.
Also, if you are configuring only a single VLAN ID, there is no need to enable PVID.

For reference, you may also find the OpenWrt DSA user guide helpful:


Download link:

Upgrade guide:

1 Like

Hi, thanks for the reply.

The final goal is have several vlans so I’ll ned PVID.

Reading the info you sent me there is an option that I din’t do.

Network → switch

Do I have to add the vlan1 also in the switch if it’s added to the br-lan device?

Is this what i was missing?

I don’t mind upgrade the router but I ask you because should be great know is the problem was my configuration or a problem with the FW version, shouldn’t it?
Is I have a bad configuration the problem will be there again with the new FW version.

Thanks in advance

I post again to give more information and ask you one question.

Question: If I upgrade ans something is broken, can I downgrade to a stable version again?

More info: The final goal is this:

With this two interfaces

And this FW configuration

Thanks!!

Yes, you can downgrade to the stable version at any time.
However, your configuration may not be preserved.

1 Like

Great

What about what I asked before my configuration with VLAN 1 on all the ports? Is it correct and should it work, or is there something else that still needs to be done, which is why it’s not working?

You can see the pics in the earlier conversation (post 3)

Thanks

Finally I’ve updated to 4.8.3 beta and apply the same configuration and works!

1 Like

Hi again

After some time (2 days) working good, suddenly I’ve lost inet connection. I’ve tried to access to the web UI with no success, no conecction.
Ping between devices works.
I’ve unplug and replug the Flint and everything works again.

This issue does not appear to be related to VLAN.

When the problem occurs, please check the following:

  1. Whether any devices can connect to the AX1800’s Wi-Fi.
  2. Try connecting to the AX1800’s GL UI, LuCI, or SSH via both wired and Wi-Fi to see if any of them are accessible.
  3. Confirm that the AX1800 is using the original power adapter or another one that meets the 12V/1.5A specification.
  4. If none of the management interfaces are accessible and the power adapter is original or meets the required specs, please try SSHing into the router while it is working normally and run the following command to stream the logs in the session. Keep the SSH session open, and after the issue occurs, export the logs shown and send them to us via private message.
logread -f

1 Like

Hi again

I agree with you, probably is not related to the vlans. Power adapter is original so may be never happend again.

I'll see if it happens again.
I think the problem may be that I have added DNS blocklists in adguard and that sometimes eats up a lot of memory.

Going back to the question in the post, I have added a new vlan (40) and configured everything.
Something interesting has happened.
The devices in the new vlan did not obtain IP and if I configured it by hand they did not reach the flint interface (ping)
I've spent quite a bit of time going over settings etc and everything seemed fine so I decided to restart Flint as a last resort and it worked.
That is, in my case a Flint restart was required for the new Vlan configuration to work correctly.

For AdGuard Home, you can refer to the following configuration to help mitigate the memory overflow issue.

We plan to add some limitations in future versions to address this problem.

1 Like

Thanks!!

And regarding to the needed of restart the Flint after Vlan configuration. Is it normal?

In some cases, it may be necessary to restart network-related components (which reboot the entire device will do also).

That’s why you’ll often see us include commands like reboot or /etc/init.d/network restart after the UCI configuration commands we provide.

1 Like