I’m using a 305 Balance with 6.1.3s2 build 1246 system.
The 305 is acting as DHCP server and balancer between
two WAN connections.
The LAN DHCP was using the default config:
IP: 192.168.1.1/24
Range: 192.168.1.10 - 192.168.1.250
Netmask: 255.255.255.0
Since we exhausted all IPs, I had to increase the range… and then the problems
started.
What I did:
In Network > LAN:
IP Settings:
kept 192.168.1.1 as the IP
changed the netmask from 255.255.255.0 (/24) to 255.255.252.0 (/22)
DHCP Server Settings:
changed the IP Range from 192.168.1.10 - 192.168.1.250 to 192.168.1.10 - 192.168.3.250
changed the Subnet Mask from 255.255.255.0 (/24) to 255.255.252.0 (/22)
Clicked ‘Save’ and then ‘Apply changes’
And after that I could no longer access the admin UI.
The DHCP server was working though, did some tests and noticed that the
LAN computers were getting DHCP offers with the correct configs (new netmask and all).
But they could not access the balancer on 192.168.1.1 anymore.
I had to physically force a Factory Reset using the frontal led panel in the 305.
No, I did several manual release/renews and reboots in different machines on the same LAN to no avail.
Even tried assigning IPs by hand and found out something really weird:
If I manually assigned an IP of, say, 192.168.0.42/22 I could ping the gateway at 192.168.1.1 but
if I changed my IP to, say, 192.168.1.9/22 (any 192.168.1.x/22 IP), I could not.
My current configuration is:
IP: 192.168.1.1/20
DHCP range: 192.168.2.0 - 192.168.15.254
Subnet mask: 255.255.240.0 (/20)
If I manually set the IP of a machine to, say, 192.168.1.50, this machine can’t access 192.168.1.1
192.168.0.50, 192.168.2.50, 192.168.15.50, or any other than 192.168.1.x, works.
My current configuration is:
IP: 192.168.1.1/20
DHCP range: 192.168.2.0 - 192.168.15.254
Subnet mask: 255.255.240.0 (/20)
If I manually set the IP of a machine to, say, 192.168.1.50, this machine can’t access 192.168.1.1
192.168.0.50, 192.168.2.50, 192.168.15.50, or any other than 192.168.1.x, works.