We configured a hotspot (RouterBoard) with a public IP address. And maintained the configuration in the quote below, but we still find ourselves with the same error message at the welcome portal as indicated in the screenshot below.Hi,
in the upcoming version 7.0.140, it will be released a fix for this.
Please wait till the release will be completed, install it the give a try then give us feedback.
Have a nice day.
On our server online (CentOS 6.10), We have HSNM Appliance running on VMware workstation 12.5.9.
HSNM in the VMware is on a NAT with the server (on public IP). The NAT network of the vmware is 192.168.27.0 and the HSNM (in the vmware) has an ip of 192.168.27.2
We can access the HSNM Appliance's web interface by openning through http://public IP/
When we configure a gateway (RouterBoard with Wi-Fi) in HSNM and carry the configurations and put in the router and attemp to connect devices, the welcome portal opens propally. Users can register themselves, and also recharge (through vouchers) their accounts.
But the problem now is that, the HSNM server can not communicate with the gateway ( even on a public IP) to permit the user be connected to the internet through the gateway.
We were advised by the HSNM support team to ensure that all the necessary ports (80, 1514, 1812, 1813, 443) be opened. We have done that. We even took the risk to "turn off" the iptables completely but we still get the same problem mentioned above.
Explicit description of our HSNM configurations.
1) Under the "system settings" under the "Admin tab", everything was left in default except the following;
1.1) In "network" setting, we have;
a) Server Rule --> Master
b) IP Address --> 192.168.27.2 (IP address from the NAT configured for VMware.
c) Subnet Mask --> 24
d) Gateway --> 192.168.27.1 (NAT gateway set up in VMware)
1.2) In "web server", we have;
a) Domain Name --> set the public IP of CentOS 6 server.
1.3) In "Radius" settings we have;
a) Secret --> Our Radius secret
b) Timeout --> 3000 miliseconds
2) Under the "Gateway" settings under the "Admin tab", everything was left in default except the following;
2.1) under "General Data" everything was left in default except the following;
a) Activate Logs --> Enabled
b) Internet Connection IP Address or DynDNS Name --> Static Public IP of our Gateway (RouterBoard)
c) URL or IP to Access the Web Management --> Static Public IP of our Gateway (RouterBoard)
d) Hardware Type --> RBx
e) Maximum Number of Users --> 0 (which means infinity)
f) Welcome Portal Template --> Green Park (default welcome portal)
2.2) under "Fields for Configuring the Gateway" everything was left in default except the following;
2.2.1) Under "Authentication Options"
a) Authentication via Mac Address --> left unticked
2.2.2) Under "Wireless"
a) Use wireless --> ticked
b) SSID --> Our SSID for hotspot
2.2.3) Under "Wan"
a) Same Network of the appliance --> unticked
b) Addressing Mode --> Static IP or DHCP
c) WAN Interface --> Ether1
d) It uses a VLAN --> unticked
f) It uses DHCP Client for the WAN --> unticked
g) WAN IP Address --> Static public IP for our Gateway (RouterBoard)
h) WAN Network Mask --> Network mask of our gateway IP.
i) WAN Gateway --> gateway IP of the WAN interface of our Gateway (RouterBoard)
2.2.4) Under "Hotspot"
a) Add Ether2 to Hotspot Bridge --> ticked (only Ether2 is ticked for the bridge ports)
b) Keep-Alive Timeout --> 72 Hours
c) IP Address --> 10.10.10.1 (IP address of the WLAN1 or Ether2 of Our Gateway)
d) Network Mask --> 255.0.0.0 (Subnet mask of the network 10.10.10.0 above)
f) DNS IP Addresses --> 188.8.131.52 (google's DNS)
g) First IP Address for the DHCP Address Pool --> 10.10.10.253
h) Last IP Address for the DHCP Address Pool --> 10.10.10.2
i) DHCP Lease Time --> 72hours
What are we suppose to fix?
Any help will be appareciated
It is right that our HSNM in VMware is on NAT not BRIDGE. We will change the NAT to BRIDGE and carry out any other modifications to be done with respect to this change, test againg and give you feedbacks.Hi Paulin
This kind of error mean a communication problem between HSNM and gateway so you have to double check your network configuration. You wrote that vmware where HSNM is installed is natted: what do you mean? Did you set the vmware network interface as NAT instead of as BRIDGE? If YES, please don't do that: the vmware network interface of HSNM must be set to BRIDGE
Belot you can also find a sample network schema that allow you to understand how is the communication between HSNM and GWs
Hope this help you
It is right that our HSNM in VMware is on NAT not BRIDGE. We will change the NAT to BRIDGE and carry out any other modifications to be done with respect to this change, test againg and give you feedbacks.
Thank you for the quick reply!
It is our case, we were giving HSNM the same Public IP address as the server/host.Hi Paulin
I don't know your network topology and your network IP configuration so it quite difficult to help you.
What I can tell you is that you cannot assign to HSNM the same IP address of the server/host where it is running. So if you are running HSNM under vmware player installed on a server/host you cannot give the same IP to the HSNM and to the server.
So, if this is your case, now you must change the IP address of the server/host settings one different from the one set to HSNM but inside the same subnet
Hope this help you
Users browsing this forum: No registered users and 1 guest