F5F Stay Refreshed Power Users Networks Building a fresh network specifically for mobile devices

Building a fresh network specifically for mobile devices

Building a fresh network specifically for mobile devices

I
Inezze009
Senior Member
716
04-09-2016, 08:18 PM
#1
Hi, I set up a new subnet just for phones and added a separate Wi-Fi network. Unfortunately, I’m not getting internet access. I already have a DHCP server running at 192.168.1.0/24, but when I created the new network with a different range (192.168.2.0/24) and set DHCP Server mode, I’m still missing connectivity. My gateway is at 192.168.1.253, and I need to link this new network to it. Could you guide me through the steps? Thanks, Roly
I
Inezze009
04-09-2016, 08:18 PM #1

Hi, I set up a new subnet just for phones and added a separate Wi-Fi network. Unfortunately, I’m not getting internet access. I already have a DHCP server running at 192.168.1.0/24, but when I created the new network with a different range (192.168.2.0/24) and set DHCP Server mode, I’m still missing connectivity. My gateway is at 192.168.1.253, and I need to link this new network to it. Could you guide me through the steps? Thanks, Roly

S
SpaghettiSquid
Junior Member
15
04-12-2016, 03:58 AM
#2
Check the setup of your new subnet: Confirm the IP range is correct (192.168.2.0/254) and that devices are getting addresses from the DHCP server within that range. Validate gateway configuration: Make sure the gateway (192.168.1.253) permits traffic from the new subnet to the internet, possibly via a static route or firewall rules. Ensure phones connect properly: Verify they’re joining the correct Wi-Fi network using the right SSID and password. Test connectivity: Send a ping from a device on the new subnet to both the gateway and an external site like Any failures suggest configuration problems. These steps should help you pinpoint and fix access issues. Success!
S
SpaghettiSquid
04-12-2016, 03:58 AM #2

Check the setup of your new subnet: Confirm the IP range is correct (192.168.2.0/254) and that devices are getting addresses from the DHCP server within that range. Validate gateway configuration: Make sure the gateway (192.168.1.253) permits traffic from the new subnet to the internet, possibly via a static route or firewall rules. Ensure phones connect properly: Verify they’re joining the correct Wi-Fi network using the right SSID and password. Test connectivity: Send a ping from a device on the new subnet to both the gateway and an external site like Any failures suggest configuration problems. These steps should help you pinpoint and fix access issues. Success!

S
Sokil
Member
65
04-12-2016, 05:07 AM
#3
All systems functioning properly.
3. The device at 192.168.1.253 acts as the firewall. You should set up a rule there to permit the subnet 192.168.2.0/254 to access the internet.
S
Sokil
04-12-2016, 05:07 AM #3

All systems functioning properly.
3. The device at 192.168.1.253 acts as the firewall. You should set up a rule there to permit the subnet 192.168.2.0/254 to access the internet.

N
nicolaj101
Member
102
04-19-2016, 04:42 AM
#4
I drafted the policy for the firewall, though it hasn't fully resolved. It appears to be correct for your Zyxel USG60W.
N
nicolaj101
04-19-2016, 04:42 AM #4

I drafted the policy for the firewall, though it hasn't fully resolved. It appears to be correct for your Zyxel USG60W.

S
shadowwiz42
Junior Member
23
05-05-2016, 02:36 AM
#5
The purpose here is unclear. Are you aiming for security? You might be using VLANs or separate physical networks with firewall rules to control traffic. Just be aware that these methods don't guarantee strong security on their own. If the goal is just for phones, security likely isn't a priority.
S
shadowwiz42
05-05-2016, 02:36 AM #5

The purpose here is unclear. Are you aiming for security? You might be using VLANs or separate physical networks with firewall rules to control traffic. Just be aware that these methods don't guarantee strong security on their own. If the goal is just for phones, security likely isn't a priority.

C
Cutie_Kitcat
Senior Member
644
05-08-2016, 05:25 PM
#6
not for security reasons, i aim to connect a phone to a different subnet so it can free up ip addresses on the regular network. it doesn't matter what type of phones are involved; they shouldn't need access to shared drives. people using pcs and laptops should stay on the same subnet to reach internal software or shared drives on the local server.
C
Cutie_Kitcat
05-08-2016, 05:25 PM #6

not for security reasons, i aim to connect a phone to a different subnet so it can free up ip addresses on the regular network. it doesn't matter what type of phones are involved; they shouldn't need access to shared drives. people using pcs and laptops should stay on the same subnet to reach internal software or shared drives on the local server.

L
LOLMENKING
Member
68
05-09-2016, 05:57 AM
#7
L
LOLMENKING
05-09-2016, 05:57 AM #7

B
Blockwalker02
Member
181
05-09-2016, 12:45 PM
#8
Based on your explanation, I should configure firewall rules for the subnets to communicate. I’ll continue with that now. Thank you!
B
Blockwalker02
05-09-2016, 12:45 PM #8

Based on your explanation, I should configure firewall rules for the subnets to communicate. I’ll continue with that now. Thank you!