DHCP server(s)

sib · #1 (**permalink**) 09-10-2004, 04:00 AM

Hi peeps,

Im new to NZ wireless, registered my node up near long bay a few weeks ago.

Since then I've been configuring my linux box to do some snazy stuff.

One thing Im doing is dhcp server for my subnet (I chose 10.24.0.0/24) and it got me wondering...

Is it possible to put a dhcp server on the internet so current wireless dhcp servers that allocate from little pools (10.x.x.x/24) can just relay to the internet dhcp and get their assignments from thier.

So I looked into it, and it is possible, and with a little programming can be configured through a web interface. (working on it now).

Security isn't an issue as a client has to connect to a central server with an account to register mac address(s) to get permit use of the dhcp server. One problem im looking into though is mac spoofing... Any Ideas?

So if its possible, Im more than willing to host dual dhcp (failover) servers on the net.

Please post your feed back, if anyone tried or knows about this im interested to hear there experiences.

* How are subnet allocated currently? just the IP Subnets list on the menu to the left there?
* Does each subnet host provide its own dhcp or forced addresses?
* Would most nodes that run dhcp know how to configure relay?

For the moment I'll continue writing this snazy stuff for linux... oh so much *fun*. My initial goal is to prive public internet access at my location that doesn't interfere (much) with my internet use as I only have 256k downstream connection and 128kup. so with a little magic im building the in in one all godly router... in php/mysql/xhtml. it will be configure to allow 4 users to connect to the internet while distrubuting bandwidth to my requirements.

Also im looking to link with friends over the valley (direct LOS) and wondering about linking our internet connects to give us a max of 512kdown does any one know how this can be achieved?

Thankyou you all.

Looking forward to increasing the nzwireless network, not just in size, but capability.

Regards

unicorn · #2 (**permalink**) 09-10-2004, 09:21 AM

Assuming I've got the picture, I think this is how it might work.

I think you can build your own private network and become a private ISP
by sharing your bandwidth (non-profit of course), and anyone elses that cares to join you in this venture but ultimately those users you share with will be using your internet account even if you have multiple accounts to the same link.
You can do whatever you like on the private side of your network.
To setup redundant DHCP servers with another person as keen as yourself you would agree on an addressing scheme for those servers and your private user community. If your users are off-net to those DHCP servers then you would have to provide a means of forwarding their DHCP requests to your DHCP servers via a router.
When your users access the internet, they will be utilising your ip address allocated by your ISP so you will be providing NAT in your private network in order for them to do this.
If another member of your private community also wishes to share their internet access then you would have a load balancing mechanism somewhere in your network, probably on a router, plus this is probably where you will also control the allocation of bandwidth.
I do not think you can aggregate your ISP link and your peers ISP link/s
because your entry points at the ISP end are seperate and your packet disassembly/reassembly will not work.
All traffic coming from your source will be returned via your path and so too with any other peers ISP link.
I am not sure that ISPs support aggregation either. You could ask them.
Also, you cannot route any private addresses over the ISP's network. The packets will be dropped. that's just a rule in the ISP world.
I'm talking about the 10.x.x.x networks and the 172.16.x.x networks etc.
Unless you have a registered address, which your ISP already knows how to get back to, you must rely on the ISP assigned addresses.
You posted this a while ago but I am new to the forum. You probably have all of your answers and some by now.

Good luck.

Lihualee · #3 (**permalink**) 09-29-2008, 07:46 PM

bump and lurk

Gisa Susi · #4 (**permalink**) 07-10-2009, 05:39 AM

The DHCP servers and DHCP clients communicate through a series of DHCP messages. To obtain a lease, the DHCP client initiates a conversation with a DHCP server using a series of these DHCP messages. You can watch the process with a network monitor.