Aliases and client isolation

Hello!,

So i was reading about this but i still got a little confused.

How would one sent a specific client to the new created alias?

As for now my current lan network ip is 10.234.53.1/24 and my alias has 192.168.1.1/24 with disabled dynamic dhcp.

I want to sent my isp tv box over this alias, would setting the tvbox to a static ip address be enough or do i need to add routing?

I'm confused. Are you saying you created a second [alias] interface on the same LAN - but with a different subnet (where you intend to statically address clients)?

If so, given it's the same physical network (i.e. no security) - why?

Thats correct, well I just wanted to try to isolate them, I readed aliases can also use their own firewall zone.

I know vlan can be used aswell, but i rather wanted my tvbox reflect the normal lan route from my old original isp box also avoiding having multicast/igmp over the full lan interface.

My isp router is now replaced with the openwrt one.

1 Like

I guess you are using the wrong tool, but I think you should explain your current setup and what are you trying to achieve exactly.

1 Like

well it's more of a homelab experiment from what I can do with aliases and what not :slight_smile:

I was reading it could be possible to setup a guest network like this without the need of vlan.

heres a diagram of the topology:

image

however the only piece i'm missing here is how would I make a client get on the alias network maybe by dhcp tagging or mac?

if all doesn't work I guess idd I use the wrong tool :slight_smile:

If your clients are wireless, then you do not need VLANs or aliases, just define different networks and attach separate SSIDs to each one. If you clients are wired, I would use VLANs and isolated ethernet ports.

4 Likes

okay I guess thats the best way of doing it thanks :slight_smile:

2 Likes

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.