[admin@HOT SPOT] ip dns> print
primary-dns: 192.168.0.200
secondary-dns: 0.0.0.0
allow-remote-requests: no
cache-size: 2048KiB
cache-max-ttl: 1w
cache-used: 19KiB
DHCP
[admin@HOT SPOT] ip dhcp-server> print
Flags: X - disabled, I - invalid
# NAME INTERFACE RELAY ADDRESS-POOL LEASE-TIME ADD-ARP
0 dhcp1 hot hs-pool-1 1h
[admin@HOT SPOT] ip dhcp-server>
Soleed,
make sure you have accomplished the following requirements,
Valid IP config is required on both interfaces.
valid DNS configuration in the /ip dns submenu
HotSpot configured on the Local interface, using the same IP address pool as DHCP server uses for that interface.
I suggest you to reset the current router configuration using ‘system reset’, then add IP addresses and route confiuguration, as well SRC-NAT rules to allow access for local IP addresses.
Add DNS settings to ip dns menu, make sure that local client is able to connect to public networks.
Then setup HotSpot,
‘ip hotspot setup’
select local interface;
‘local address of network’ should be address of the local interace;
masquerade network: no (as you have already created masquerade rule);
use address-pool predefined value;
select certificate: none
specify SMTP server address, if you want to redirect all clients to the specific SMTP server;
specify DNS server addresses for HotSpot clients;
dns name leave blank;
add default user (as well you can additional users to ‘ip hotspot user’ menu).
Then HotSpot should work fine.
After a lot of strugle with the hotspot, I found that these steps should set up the initial configuration for a hotspot to work:
assuming that your router has no configuration (assuming that you reset it)
If you have an internet conection that sends DHCP then in the interface that connects to your ISP put a DHCP client
Then run the hotspot setup for the interface the hotspot is going to be in, select the IP RANGE x.x.x.x/x (You can have it like 192.168.0.1/16) yes on maskerade network, and the rest is up to you.
Then it should work.
This will give you a basic configuration so you can add the other feathures latter.
Hope this hellps you… I am really new to RouterOs.
have you try to configured IP redirect in yout firewall, because you have chose tranparent proxy so you have to create a transparent proxy too not just only proxy.
1.-Upgrade to latest version
2.-Set the ip for the interface on with the router is goin to run hotspot, like: 192.168.0.1/16
Yo can skip this since I have not done this, it’s just an Idea: go to webbox and mark the “protect router” and “protect client”
3.-If you can implement ppp0e(highly recommended) on your WAN interface, do so and enable: use peer dns. f your ISP provides you with dynamic or static DHCP ip’s then on your WAN interface set up a DHCP client. If you have manual static IP then call your ISP so they can give you the rigth configuration
4.-Run the hotspot setup wizard to create the hostpot.
5.-Set web-proxy to transparent and enable it.
6.-on ip-firewall: put this nat rule:
(interface local is the interface on witch the hotspot is running)
7.-in ip-services: change your www service to another port (not port 80 since it will be used for web-proxy)
8.-if you wold like to use usermanager… go ahead¡¡¡ it’s cool¡¡
Yes, this problem is because both hotspot and web-proxy use the same port: port 80, and when they are working at the same time, the nat rule that redirects the traffict from port 80 to the web-proxy is responsible for this.
Follow the steps I gave in my previous post, allso, view my topics, I had the same problems, they are all fixed and I posted the solutions for them.