DHCP will not allocate IP addresses on Netcomm NF4V Router

Forums › LAN (ethernet/Wifi/routers/Bluetooth) › DHCP will not allocate IP addresses on Netcomm NF4V Router

Oddball

65 posts

Master Geek

#153880 11-Oct-2014 00:08

Hi,

Got a new router / VDSL.

I can't get it to allocate IP addresses, works if I use a static. And it assigns static via mac addresses on the router.

I would appreciate any help.

Here is an image of my settings:

1 | 2

534 posts

Ultimate Geek

#1151646 11-Oct-2014 00:17

Dunno if it's relevant but your subnet mask is wrong for the ip range. 192.168.x.x is 255.255.255.0, you should be using 255.0.0.0

Home ADSL: School:

Oddball

65 posts

Master Geek

#1151660 11-Oct-2014 01:49

Thank you, that fixed it :)

jamesrt

1002 posts

Uber Geek

Trusted

Lifetime subscriber

#1151718 11-Oct-2014 09:58

Oddball: Thank you, that fixed it :)

Well then, in my opinion you've found a firmware bug then. 255.255.255.0 is a perfectly valid network subnet mask for an IP address range starting with 10.x.x.x; all it means is that you are constraining the network range to that "subnet", so in the case of 10.1.1.x/255.255.255.0, anything from 10.1.1.1 to 10.1.1.254 is a valid IP, 10.1.1.0 is the network address, and 10.1.1.255 is the broadcast address; 10.1.2.y (for example) is outside the network and needs to be routed to, rather than being on the same "LAN segment".

That's kinda networking 101, and I'm a little surprised the router got it wrong.

linw

2206 posts

Uber Geek

Subscriber

#1151757 11-Oct-2014 10:56

Agree. Something weird going on there.

Oddball

65 posts

Master Geek

#1151761 11-Oct-2014 11:00

No idea. Perhaps changing it forced something to reset? I kept hearing good things about this router which is why I got it so that's somewhat surprising, I was actually just trying it to humor the idea but it worked :/

michaelmurfy

/dev/null
9436 posts

Uber Geek

Moderator

Trusted

Lifetime subscriber

#1151765 11-Oct-2014 11:09

You should set the IP range to 192.168.1.0 (subnet 255.255.255.0) instead, having a 255.0.0.0 subnet at home is pretty bad.

Oddball

65 posts

Master Geek

#1151768 11-Oct-2014 11:15

Why is it bad? My networking knowledge is relatively limited, I can get things going but don't quite understand everything.

The Orcon router used 10.1.1.1 by default and I'm NOT using that to justify it, rather that my flatmates who aren't tech savvy are used to it.

Furthermore it's far less tedious to enter 10.1.1.1 than 192.168.1.0 on a device with limited input (i.e not a proper keyboard).

Also: Finally free from Orcon, hooray.

Athlonite

1828 posts

Uber Geek
Inactive user

#1151775 11-Oct-2014 11:55

Oddball: The Orcon router used 10.1.1.1 by default.

Strange mines default is 192.168.20.x / 255.255.255.0 not 10.1.1.1 / 255.0.0.0

dcole13

534 posts

Ultimate Geek

#1151779 11-Oct-2014 11:59

Athlonite:
Oddball: The Orcon router used 10.1.1.1 by default.

Strange mines default is 192.168.20.x / 255.255.255.0 not 10.1.1.1 / 255.0.0.0

Orcon white uses 192.168.20.x, the old Bob used 10.0.0.0

Home ADSL: School:

Oddball

65 posts

Master Geek

#1151780 11-Oct-2014 11:59

Athlonite:
Oddball: The Orcon router used 10.1.1.1 by default.

Strange mines default is 192.168.20.x / 255.255.255.0 not 10.1.1.1 / 255.0.0.0

Black or white? Mine was black. They're different models.

Oddball

65 posts

Master Geek

#1151784 11-Oct-2014 12:25

dcole13:
Athlonite:
Oddball: The Orcon router used 10.1.1.1 by default.

Strange mines default is 192.168.20.x / 255.255.255.0 not 10.1.1.1 / 255.0.0.0

Orcon white uses 192.168.20.x, the old Bob used 10.0.0.0

Ah right.

Point of interest: The Orcon White is the nf4v I'm using, but probably modified.

Mine also had 192.168.20.x but I changed it for reasons specified.

jamesrt

1002 posts

Uber Geek

Trusted

Lifetime subscriber

#1151786 11-Oct-2014 12:37

... and worth noting for posterity, or (Google searches!), that you shouldn't reset your Orcon White to use 192.168.0.0/255.255.255.0; otherwise "bad things" may happen. And by "bad" I mean an unstable connection that keeps dropping out.

Another firmware issue - Orcon's DHCP server uses the 192.168.0.0/24 address space, and the white gets confused when trying to renew it's lease, and asks the wrong server, and doesn't get it renewed. At least that was the issue in my experience - changing back from 192.168.0.0/24 to anything else resolved it.

This was my experience - YMMV, newer firmware may have fixed, etc etc. Worth noting in this discussion however.

Oddball

65 posts

Master Geek

#1151787 11-Oct-2014 12:38

Orcon teaches us how not to internet.

dcole13

534 posts

Ultimate Geek

#1151789 11-Oct-2014 12:41

I guess if you change anything it breaks something?

Home ADSL: School:

raytaylor

3455 posts

Uber Geek

Trusted

#1153826 14-Oct-2014 18:04

Oddball: Why is it bad?

On our customer installs we use the 10.1.1.x/255.255.255.0 range for their home ip address structure

How a subnet affects you
255.255.255.0 means 10.1.1.X stays within your network and is directly accessed. Anything else goes via the gateway device (router)
255.0.0.0 means 10.X.X.X stays within your network and is directly accessed. Anything else goes via the gateway device (router)

RFC 1918 states that there are a few different blocks of IP addresses allocated for private use.
They are
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255

The 10.X.X.X and 192.168.X.X are the most common types of addresses used for private networks.
There is the problem.
You can see that not all ip addresses within 192 are private - most are actual routable internet addresses.

Eg. 192.168.1.5 is a private address.
192.169.1.5 is a routable internet address.

So if you use the subnet mask 255.0.0.0 with a network address beginning with 192.168 then you are saying the entire 192 range is local.
Websites that have a routable address in the 192 range would become inaccessible because computers on your home network dont know that they are accessed via the gateway.
So you would need to use 255.255.255.0

APNIC and various other regional registries are now issuing ip addresses in the 192.X.X.X and 172.X.X.X ranges outisde the reserved private allocations as ipv4 addresses are running out.

Ray Taylor
Taylor Broadband (rural hawkes bay)
www.ruralkiwi.com

There is no place like localhost
For my general guide to extending your wireless network Click Here

1 | 2