Need help understanding LAN/DCHP settings

Cassady

Cassady

Expert Member
Joined
Oct 27, 2011
Messages
1,968
Reaction score
65
Location
Die Kaap
Hello all,

Would really appreciate some help. iBits came and did the installation today. Line of sight access, with some sweet speeds coming through Speedtest.net!

Still waiting for the account to be opened.

Was told to do the following to my router, upon plugging in the network cable from the aerial:

1.) Switch my IP address under the LAN tab of my router from 1xx.1xx.1.1 to 1xx.1xx.0.1, which I have done.

2.) Switch off the DCHP - which I have also done.

My laptop and fixed computer can see the Wi-Fi network, and I am able to connect to the router interface.

But now my iPhone and iPad (and presumably all the other devices that were connecting via Wi-Fi) can now, after initially all being fine, no longer connect.

FWIG, the DCHP manages the connections to the network?

Switching it off - does this mean I need to manually add a static IP address to each device? And if so - would I do that on the device, or add them through the route interface?

Any suggestions?

Edit:

Under the IP address section on my phone - I see a completely different IP address - not sure where it's found that. I have the option to add a static one as well. That unfamiliar IP address is presumably why it cannot correct atm.
 
Last edited:
DHCP Assigns IP addresses to devices. So if you don't have another router with DHCP turned on then your devices won't get IP addresses and you won't be able to connect to the internet.

On computers you can manually assign IP addresses without the need of DHCP, but I don't think iPhones/iPads can...

Edit: Scrap this -
but I don't think iPhones/iPads can...
Click to expand...
 
$m@Rt@$$ said:
DHCP Assigns IP addresses to devices. So if you don't have another router with DHCP turned on then your devices won't get IP addresses and you won't be able to connect to the internet.

On computers you can manually assign IP addresses without the need of DHCP, but I don't think iPhones/iPads can...

Edit: Scrap this -
Click to expand...

It actually appears that you can. So assuming that to be the case, I add the static addresses to the devices, and then all should be fine?

I guess I'm asking: is using DHCP simply for convenience? There won't be any other downsides to switching it off, apart from having to enter the IP addresses manually?
 
Did you ask them why they want you to switch off DHCP?

May be good idea to understand their reasoning on the subject.

I went through a phase whereby I would not allow devices to just connect, and insisted on fixed IP addresses and disabled DHCP .
 
daniellgr said:
Did you ask them why they want you to switch off DHCP?

May be good idea to understand their reasoning on the subject.

I went through a phase whereby I would not allow devices to just connect, and insisted on fixed IP addresses and disabled DHCP .
Click to expand...

Nope. They simply said it caused problems. I'm thinking of switching it back on. If it bombs, can surely just switch it off again?

That said - what would be advisable? Adding the static addresses router side, device side?
 
DHCP is literally just for convenience, also very nice to have on otherwise you need to setup IP/DNS/Mask/Gateway on all devices manually.
 
daniellgr said:
Did you ask them why they want you to switch off DHCP?

May be good idea to understand their reasoning on the subject.
Click to expand...

We know a little of what's going on, on their network as we speak with them at least once a day, every day.

iBits have a nice block of public IPv4 addresses. They also have a block of IPv6 addresses.

Like us, they spend most every night converting clients from "192.168" address to public IP addresses.

Like us, they use a combination of router on the roof and wireless AP in the house.

We mostly use Mikrotik on the roof, but also use Ubiquiti in some areas. They mostly use Ubiquiti.

If there's a Mikrotik on the roof, we'll either put a TPLink or a couple of Ubiquiti UniFis inside. This is a recipe we've used for years. It works.

The theory is that the radio on the roof does the PPPOE connection back to the ISP. All our new clients receive a static public IP address at this point.

Believe it or not, but iBits have a massive network. Switching all the users over is taking a very long time. The way I understand it, they have rolled out static publics to the towers / PPPOE concentrators, but are still rolling public IPs out to the clients. At this point the PPPOE should therefore receive a 192.168 address that is NATted. Now, if your router on the roof does all the DHCP and your router in the house is a dumb bridge, you don't have a double NAT situation.

You don't want a double NAT. This is bad.

We normally pop a RJ45 connector into the TPLink or Tenda AP's WAN port to block it. Then the AP receives a static ip of 192.168.1.1 with gateway 192.168.1.254 and DHCP is switched off.

The TPLink or Tenda is then a dumb bridge. It does no work, apart from wifi and network switch. These things don't have the fast processors you find in Routerboards. Switching from router to dumb bridge means our clients (and iBits' clients) can now have speeds of 30Mb+ over wireless on relatively inexpensive kit.

The router on the roof then does the DHCP and NAT's the 192.168.1.x network to the WAN IP address of the router.

For the techs... The other reason both us and iBits are doing this, is ease of implementation of IPv6. All we need to do is have a static IPv6 address in one /64 on the WAN port and another IPv6 address on another /64 that advertises on the LAN port of the router on the roof. This is a simple, but highly effective way of rolling out IPv6. All the client needs to do is ensure that IPv6 is enabled on his device.

This is what I am doing right now. One client at a time... Three or four hours a night, every night.
 
Last edited:
portcullis said:
We know a little of what's going on, on their network as we speak with them at least once a day, every day.

iBits have a nice block of public IPv4 addresses. They also have a block of IPv6 addresses.

Like us, they spend most every night converting clients from "192.168" address to public IP addresses.

Like us, they use a combination of router on the roof and wireless AP in the house.

We mostly use Mikrotik on the roof, but also use Ubiquiti in some areas. They mostly use Ubiquiti.

If there's a Mikrotik on the roof, we'll either put a TPLink or a couple of Ubiquiti UniFis inside. This is a recipe we've used for years. It works.

The theory is that the radio on the roof does the PPPOE connection back to the ISP. All our new clients receive a static public IP address at this point.

Believe it or not, but iBits have a massive network. Switching all the users over is taking a very long time. The way I understand it, they have rolled out static publics to the towers / PPPOE concentrators, but are still rolling public IPs out to the clients. At this point the PPPOE should therefore receive a 192.168 address that is NATted. Now, if your router on the roof does all the DHCP and your router in the house is a dumb bridge, you don't have a double NAT situation.

You don't want a double NAT. This is bad.

We normally pop a RJ45 connector into the TPLink or Tenda AP's WAN port to block it. Then the AP receives a static ip of 192.168.1.1 with gateway 192.168.1.254 and DHCP is switched off.

The TPLink or Tenda is then a dumb bridge. It does no work, apart from wifi and network switch. These things don't have the fast processors you find in Routerboards. Switching from router to dumb bridge means our clients (and iBits' clients) can now have speeds of 30Mb+ over wireless on relatively inexpensive kit.

The router on the roof then does the DHCP and NAT's the 192.168.1.x network to the WAN IP address of the router.

For the techs... The other reason both us and iBits are doing this, is ease of implementation of IPv6. All we need to do is have a static IPv6 address in one /64 on the WAN port and another IPv6 address on another /64 that advertises on the LAN port of the router on the roof. This is a simple, but highly effective way of rolling out IPv6. All the client needs to do is ensure that IPv6 is enabled on his device.

This is what I am doing right now. One client at a time... Three or four hours a night, every night.
Click to expand...

Appreciate the detailed reply. I think I followed most of that... :whistle:

I'm not entirely sure what is on my roof - simply appears to be an aerial of sorts - with a simple LAN cable that feeds into my router.
At the moment, still have DHCP activated, since I realised that switching this off, will see me having to add static addresses to 12 devices... But if needs be, then I will.

I'm contemplating leaving DHCP on initially. If things go awry, will simply switch it off - and go the manual route.

The single question I still have: Would it be advisable to add the static addresses from the Router interface, or from the devices' side?
 
To close this off - found the little Ubiquti device >> I initially thought it was just some sort of plug, thing is *tiny*.

Regardless, disabled DHCP, and all is working as it was. No idea why it gave me hassles on the first day, but it's been 48hrs now, and all that was connected, still is.

Thanks for the help. Really enjoying HD streaming! :)
 
I suspect the Antenna is doing the DHCP and that's why they asked you to disable it.

So that's why then IP addressing will need to be the same and you need to connect it on a LAN not a WAN port if it has those.

Your Gateway will need to be the Antenna IP and if there is a DHCP relay option you want to make that the Antenna IP as well.
 
You must log in or register to reply here.
Back
Top
Sign up to the MyBroadband newsletter
X