I have a RB configured as Hotspot router.
It has 3 NIC:
eth1 configured as WAN
eth2 configures as LAN1 with 3 differents networks (192.168.0.0/24, 192.168.1.0/24, 195.95.130.0/0)
eth3 configures as LAN2 with only one network (192.168.2.0/24)
So, i have 2 interfaces configured as LAN for customers.
1. My first question is about how configuring hotspot on LAN1 that have 3 address pool :
should i configure only one instance of hotspot server for that interface, where parameter “address-pool” has for value “none” or
should i for that interface, configure three instances of hotspot for each of 3 address pool ?
2. The second question is:
I would like all customers, no matters from what hotspot they connect, use same hotspot dns name (/ip hotspot profile dns-name) when they try to connect/disconnect.
As i will get at least 2 hotspots instances, is it possible to get only one dns name for thoses hotspot profile ?
Well first let me ask you this. Is there any good reason why you want to use two /24 addresses instead of one /23? You can always increase the subnet size to gain more address space. By having two /24’s on your LAN you just make things harder on yourself and don’t really gain any functionality. Also your 3rd address on that LAN is a public IP, is there any reason why you want it there?
The DNS name for the hotspot doesn’t really matter, that’s just a local DNS record that users are redirected to. If you are going to have two hotspots on two different interfaces, I’m fairly sure you can’t use the same DNS name since the DNS record is going to be tied to the IP of the local interface and the firewall will probably block them from getting to a different interface, but I could be wrong.
If you are going to have two hotspots on two different interfaces, I'm fairly sure you can't use the same DNS name since the DNS record is going to be tied to the IP of the local interface and the firewall will probably block them from getting to a different interface, but I could be wrong.
You can work around that. When there already is a static DNS entry for the A record the Hotspot server profiles do not insert dynamic entries.
I usually have several VLANs with Hotspots stacked on a physical interface. I assign the physical interface 10.1.0.1 and statically map hotspot.mydomain.com to 10.1.0.1. That then works fine on all VLANs. As long as it resolves to a router owned IP address things appear to work - it doesn’t have to be the IP address of the interface facing the Hotspot client.
Since all that is undocumented behavior that may stop working in the future, though.
Absolutely agree to only use one IP address per Hotspot network. Public IPs work fine for Hotspots - just make sure you remove any NAT rules created by the wizard if you use the wizard, and to turn off universal NAT. But the public IPs should be on their dedicated Hotspot interface.
Well first let me ask you this. Is there any good reason why you want to use two /24 addresses instead of one /23? You can always increase the subnet size to gain more address space. By having two /24’s on your LAN you just make things harder on yourself and don’t really gain any functionality. Also your 3rd address on that LAN is a public IP, is there any reason why you want it there?
Ok for subnetting privates ip’s.
About the public one, the reason is i have on that Lan two kind of customers, and some need public IP.
Do you mean in my case, I should use two hotspot servers on the LAN having 2 networks (private and public one) ?
Actually, I just have one hotspot server on that LAN, with address pool to “none” (supposed to cover any ip network).
Depends on what you mean by “Hotspot server”. If you mean two physical devices - no, that is not necessary. If you mean “two instances of Hotspot servers on the same physical router, but tied to two different interfaces (be they VLANs or physical interfaces on the same router)” - yes, that is exactly what we mean.
Basically make a LAN3 with the public IP address and run the Hotspot wizard again and set it up on LAN3 - and make sure you set the address pool to ‘none’ like you have been.
Like i said earlier, i was actually able to work around this by creating a dns for each VLAN; doing this, allow me to be able to use the gateway of the switch for the clients which enables intervlan on the switch and not on the router(i have lots of local traffic and don’t want those to go through the router). Will still keep trying to see how to have a dns name for all Vlans on hotspot.
@abdonetwork what you posted works perfectly. But when you want to change the gateway of your “ip dhcp-server network print” to that of the switch(like in my case), hotspot won’t work with a single domain such as your www.skynet.com. The current option which works for me is to create each domain per physical interface (vlan in my case)on the “ip hotspot profile”..say www.skynet.com and www.skynet1.com. ofcourse the ip address on ip hotspot profile print will remain the gateway(s) of the router interfaces
i found the best Solution to be can have more than one range each one Lan card
Well
if we have one Lan card and need to use the max IP's range
just add it when you enter the Lan ip
e.g if you have the lan range 192.168.0.1/24 it will give the ip's range 192.168.0.0-192.168.0.255
but if we need 4 ranges in same lan card we can add the address with /22 e.g= 192.168.0.1/22
this will give: 192.168.0.0-192.168.3.255
then go to ip pool edit your pool to be hs-pool-1 ranges=192.168.0.2-192.168.3.254
then go to ip firewall nat add a new ranges
