Hotspot fetures or limitations?

I’ve x86 router running by ROS 4.17 with 3 intrfaces

  1. WAN 10.10.10.10/30 (transport network to ISP)
  2. DMZ 11.11.11.11/27 (routed network from ISP with some external hosts running web and etc..)
  3. LAN 172.16.1.1/24 (local hosts placed here)

LAN interface also running Hotspot with Radius auth on local AD with no problems. LAN users can access DMZ without any NAT. Ip-binding feature is disabled on Hotspot & DHCP also disabled on ROS, local stations use wheir own adresses leased by MS Windows DHCP.

So grand question :slight_smile:
User point their IE to go to anyplace, then hi/she’ll see login page and fill their login/pass, after auth, we’ll see his/her activity in billing (for examp - UserManager or any other, that can use Radius). In my configuration example i don’t need to bill user’s traffic to/from DMZ and i’ve free access to some external networks running by my ISP. So, using winbox hotspot config, I can’t exclude some hosts/networks from “billing” after user authorisation and I see all their traffic in “billing”, even then they go to hotspot’s status page. And, as you can see, WallGarden and ip-binding is helpless in this case :frowning:

Can someone help?

You cannot except any traffic from showing up in traffic counters.

I’ve problem with that. One user noticed that, he can get “huge downloads” by simply refreshing his hotspots’s status page :frowning:

There is no solution for that, other than using NetFlow/TrafficFlow and going to an entirely different billing solution based on that protocol.

That’s sad :frowning:

Thanks anyway.