DHCP server multiple gateways

Gregory Sloop gregs at sloop.net
Thu Oct 22 19:29:08 CEST 2020

UB> Thanks for your response :)

>>  The best approach is to use VLANs.  You can create one VLAN per network segment.  Then use one SSID.  And when a user connects, assign him to the correct VLAN.
>>  The downside is that if someone visits a different site, they won't be able to use the local printer.  But that may be a good thing, because they also can't see _any_ devices on that network.

UB> I have tested VLANs, but I need to share local resources between
UB> houses (printer and storage, for example). This is why everyone is
UB> in the same subnet. By my tests/research I just can achieve this
UB> buying a new device that has routing ip policy (so I could still
UB> have intervlan routing using interfacevlan and the default static
UB> routing set to this new device could route packages properly (but
UB> I'm trying not to spend extra $$$ with a new router).

You know Dell Powerconnect 6248 switches (48 port GBE) which will do L3 routing are <$100 on ebay, right. (I think the last one I bought was ~$50)
6248-PoE's are like <$125.

Seems like a pretty cheap way to "git er done," if it can solve your problem.

>>  If you want each users *public* traffic to go through their own LTE/4g antenna, then VLANs are the best solution.

UB> Yep, this is my main goal: allow roaming wifi between houses but
UB> respecting the LTE/4g antenna each person's belong.
UB> This is why I thought that setting up pihole as
UB> freeradius+dhcpserver could let me send IPs+Gateways based on the specific house login.
UB> I would just have 5 shared users: house1, house2, house3, house4, house5
UB> Everytime some device using house1 login try to reach one AP the
UB> freeradius+dhcpserver was going to return a valid ip from their IPpoll

More information about the Freeradius-Users mailing list