inter-VLAN routing

Soogs · 19 Feb 2021 at 14:46

ok so after reading all your replies I've decided that it's not worth setting up VLANs for what I want, as I'm not trying to make more work for my router (and that it goes against why you would set them up in the first place).

I've tried to set up different subnets but for some reason, even though I can ping and traceroute the devices, none of the devices have internet access.

eth2 192.168.10.1/24 WAPs ((no internet access))
eth3 (switch0 192.168.1.1/24) internet access ok
eth4 192.168.20.1/24 media ((no internet access))

if i have static addresses mapped in the 192.168.1.1 network would it affect the devices that now would be in a different subnet?

do i need to wait some time for devices to find their way to the new gateway?

the-evaluator · 19 Feb 2021 at 14:50

I'm confused, you say you're not going the setup the VLANs and then ask why devices in the new VLAN's have internet access problems? If you're adding a new subnet to your router then you're adding a new VLAN.

What's doing DHCP for the networks hanging off of eth2 & eth4? Can a client on one of those VLANs ping 8.8.8.8? What IP address have they got? What DNS server are they using? Can they ping the gateway address in that VLAN?

Armageus · 19 Feb 2021 at 14:56

the-evaluator said:
If you're adding a new subnet to your router then you're adding a new VLAN.

Nope you can have subnets without vlans, or you can have vlans on the same subnet.

the-evaluator · 19 Feb 2021 at 14:59

Armageus said:
Nope you can have subnets without vlans, or you can have vlans on the same subnet.

Yeah, a secondary range. But surely if that new range is assigned to a different LAN port or vSwitch then it's a new VLAN?

You can't have multiple VLANs on the same subnet unless you're using VRF's.

Soogs · 19 Feb 2021 at 15:05

no, I've removed all the VLANs and unchecked "VLAN aware"
removed eth 2 and 4 from the switch0 interface and given the ports their IP addresses and set up DHCP pools for each interface.

they all have internet access now. a reboot of all devices seemed to have fixed that.

do I need to set up mDNS so that the plex media player on 20.1 can see the plex server which is on 1.1? and likewise so the smartphone can remote control the plex player?

alexp999 · 19 Feb 2021 at 15:09

Wouldn't it be easier just to bridge the interfaces so they are all on the same LAN and subnet?

Soogs · 19 Feb 2021 at 15:22

yes, it would but I'm not going for easy.
it all works fine in the same subnet.
this is for fun and for experience messing with networks/routing

Caged · 19 Feb 2021 at 15:37

You should consider doing this in something like Packet Tracer, or at least get familiar with Wireshark and getting packet captures out of the EdgeRouter - currently you're in a position where you're learning by making changes but not necessarily getting an understanding of what is going on.

Soogs · 19 Feb 2021 at 18:23

packet tracer (and my course videos) are what has sent me deep down this rabbit hole lol
that and the words interVLAN routing

I think I'm going to learn more about routing between subnets before I try to go any further with this

Deleted member 77746 · 19 Feb 2021 at 18:24

Just stick em on same ip and subnet n have done with it.

Networks too small to do it really.

Caged · 19 Feb 2021 at 19:19

What are you actually trying to do? You can shove all your IoT devices in a known IP range and just stop them talking to the internet other than through HTTP/HTTPS and DNS ports if that's what you want, and you'll still be able to connect to them internally as they will be in the same subnet as your other clients.

Soogs · 19 Feb 2021 at 19:31

Just tinkering and trying to learn about Subnets and VLANs and how to route between them. (by route I mean share files or have remote access) (sorry if my terminology is incorrect)