VLAN Setup Question. One VLAN has internet and the other does not.

Notice: Page may contain affiliate links for which we may earn a small commission through services like Amazon Affiliates or Skimlinks.

miogpsrocks

New Member
May 7, 2026
1
0
1
Hello.

I am trying to setup an VLAN. One VLAN network has access to the internet and the other does not.

Overall the setup is ATT fiber gateway in passthrough mode with ER605 MAC address as the location.

The ER605 is showing the public IP address assigned to the WAN port.

There are 2 networks.

First LAN: 192.168.1.1
Second LAN : 192.168.2.1


The network on the 192.168.1.1 has internet access
The network on the 192.168.2.1 does not have internet access.

Please help me out if you can.

Thanks.
 

clcorbin

Member
Feb 15, 2014
87
15
8
NOTE: I am a novice on networking! With that said, if the gateway is in pass through mode, what is doing the routing between VLANs?
 

sic0048

Active Member
Dec 24, 2018
235
169
43
Hello.

I am trying to setup an VLAN. One VLAN network has access to the internet and the other does not.

Please help me out if you can.

Thanks.
What firewall/router are you using? Odds are the system defaults to a single "Allow All" firewall rule for the main LAN network which is why you can access the internet without any additional configuration on the network segment that the system created by default (192.168.1.1).

However a lot of systems won't add any firewall rules by default when you add/create additional network segments - like VLANs. A network segment with "no rules" usually results in the system "blocking all" traffic meaning devices on that network segment can communicate with each other, but not outside of the network segment - including with other local devices on different network segments, or with the "internet". That is what I suspect happened here. You likely need to go into the firewall rules and modify/add rules to allow devices on the VLAN to access the "internet". The easiest way to do that is usually to create a firewall alias that is comprised of all the private network segments and then creating a firewall rule that allows the INVERSE of that firewall alias. That will allow traffic to any destination that isn't a private network segment (like 192.168.x.x, 10.x.x.x, etc).

Long story short, I am 99.99999% certain your issue lies with the firewall rules for your second network segment. You don't have any rules that would allow devices to communicate with your local network, or with devices located on the "public" network outside of your gateway.
 
Last edited:
  • Like
Reactions: cesmith9999