• Some users have recently had their accounts hijacked. It seems that the now defunct EVGA forums might have compromised your password there and seems many are using the same PW here. We would suggest you UPDATE YOUR PASSWORD and TURN ON 2FA for your account here to further secure it. None of the compromised accounts had 2FA turned on.
    Once you have enabled 2FA, your account will be updated soon to show a badge, letting other members know that you use 2FA to protect your account. This should be beneficial for everyone that uses FSFT.

Subnet mask issue?

M

MIPS64

n00b
Joined
Sep 1, 2012
Messages
41
Several years ago, our network was established using 172.16.3.0 but was assigned a subnet mask of 255.255.255.0 instead of 255.255.0.0 which seems a little odd to me. We have had no known network problems throughout the years using this.

Now we have bought a device and it has been assigned an IP with 172.16.3.x and does not like that it is assigned the subnet mask of 255.255.255.0. It says that it is wrong and should be 255.255.0.0. I can assign it that, however, it will not work because the firewall is saying the subnet mask is 255.255.255.0.

So before we pay obscene money to get the network guys out here, is this a legit problem we should be concerned about? Is it possibly causing more problems on the network we do not know about? Thanks for your assistance.
 
Using a /24 with 172.16.3.0 is perfectly fine, there are no issues with it at all.

What device is complaining about it?
 
A particular model of Foscam cameras. We have several different models from Foscam but this particular one is the only one complaining.
 
I'd go through the dreaded process of calling them up, emailing them, visiting their forums/site and put in a ticket, and see what they've heard about it. If it's a firmware issue that might suck if they don't have a fix for it since it seems that it's locked in classful mode.

The network and set up is perfectly fine, the device should not be picky about that subnet whatsoever.
 
Is there another address that's incorrect, and the camera is complaining about that? Maybe your default route/gateway is on another network than 172.16.3.0

Or it might be assuming since you have a class B you also have to have 255.255.0.0 - and the software for it is badly written and won't accept any setting other than that.
 
You must log in or register to reply here.
Back
Top