How to Setup Adopisoft
Network Configuration
In this setup, you will
learn how to configure the adopisoft network to work the built-in wifi,
VLAN, and USB2LAN at the same time. First of all, you need to know their name:
eth0 is the BOARD Ethernet WAN port. This is where
your internet is going in.
wlan0 is your built-in wifi
eth1 is your first connected usb2lan, next is eth2
is the 2nd,eth3 is the 3rd,eth4, the fourth one.
eth0.22 is your vlan22. 22 is the adopisoft default
VLAN. You can use any VLAN number as long as it is both configured as the same
number in the ado admin dashboard and to your VLAN hardware.
Every interface has
its own gateway separated from its other.
Example:
eth0(WAN) 192.168.1.2
Network Prefix: /24
Gateway: 192.168.1.1 (Your PLDT
modem IP)
wlan0(Built-in) 12.0.0.1
Check Enable Captive Portal
Set Maximum Hops Allowed to 1
Static IP:12.0.0.1
Network Prefix: /20
Check Use System DNS Server
Check enable DHCP on this Interface
DHCP start:12.0.0.10
DHCP End:12.0.15.254
eth1(USB2LAN 1) 20.0.0.1
Check Enable Captive Portal
Set Maximum Hops Allowed to 1 Static IP:20.0.0.1
Network Prefix: /20
Check Use System DNS Server
DHCP start:20.0.0.10
DHCP End:20.0.15.254
eth0.22(VLAN22)22.0.0.1-Go to Network then Interface then 802.1Q then create VLAN using VLANID22. You can use any VLAN number but 22 is the default. Make sure the VLAN number in adopisoft vs VLAN id number in your hardware are the same.
Check Enable Captive Portal
Set Maximum Hops Allowed to 1
Static IP: 22.0.0.1
Network Prefix: /20
Check Use System DNS Server
Check enable DHCP on this Interface
DHCP start:22.0.0.10
DHCP End:22.0.15.254
You can use whatever
number you want. With this setup, every interface has its own IP separated from
each other. You will automatically see what interface you are connected via the
IP assigned to you by the interface gateway.
Why does the DHCP address start with 10? Because the IP x.0.0.2 to x.0.0.9
where X will determine what interface you are connected to, is your reserved IP
if you want your AP to be static. The reserved IP can be used by your Access Point in static AP mode. This will ensure that the IP cannot be used by your system to assign it to one of your clients.
Having a different
interface will have different Portal IP when connected to its Access Point or
routers AP. Ex with the IP assignment above, if you are connected to USB2LAN, your portal IP would be 20.0.0.1. If you are connected to the built-in, your portal IP would be 12.0.0.1, and so on.
The disadvantage of having different portal IP for every interface:
This will get you disconnected from the internet if you switch AP
connection and needed to reconnect to the portal or at least open the portal manually
to allow the internet again into your phone. What if all your SSID from all your
interface are the same? You will likely get disconnected from the internet if your
phone disconnects from one interface to another interface with different portal
IP. You need to at least reopen the browsers portal to gain internet access again.
With this problem, INTERFACE BRIDGING is introduced. With
interface bridging, the IP on all the bridge member interfaces are all the
same. Their individual gateway will be ignored. Each accommodated interface connected to a physical segment
is handled as one segment.
br0(Bridge) 10.0.0.1
Check Enable Captive Portal
Set Maximum Hops Allowed to 1
Set static IP to 10.0.0.1
Check the required interface to bridge
Network Prefix: /20
Check Use System DNS Server
Check enable DHCP on this Interface
DHCP start:10.0.0.10
DHCP End:10.0.15.254
Before Bridging:
After Bridging:
Bonus: Maximum Hops Allowed must be set to 1 to prevent phone tethering on all your interface.
No comments:
Post a Comment