DHCP and RRAS

krumpt · 08-07-2008, 08:49 AM

Hi,

I have a client that is currently using SBS2003, along with a RV043 Linksys VPN gateway.

Current:

Code:

DSU -- VPN_GW -- SBS < DNS & NAS-- LAN

New:

Code:

DSU -- UT -- SBS, DNS & NAS & LAN

Currently the SBS server is handling DHCP and was once doing RRAS. We are trying to migrate away from SBS but for the time being we are going to keep it in place. I like untangle because of RAP and AD integration that it does provide. My primary question is, will there be any ramifications to the AD environment if I disable the DHCP on the SBS and use untangle instead??

Thanks

John

sky-knight · 08-07-2008, 09:10 AM

Nope, but to be fair the UT DHCP doesn't do everything that the windows server one does. So if you use it for DNS updates, or have some advanced stuff configured you won't be able to make the switch. If all you have is a few reservations and a basic scope, you could make the switch in a heartbeat.

dmorris · 08-07-2008, 10:24 AM

Quote:

Originally Posted by sky-knight

Nope, but to be fair the UT DHCP doesn't do everything that the windows server one does. So if you use it for DNS updates, or have some advanced stuff configured you won't be able to make the switch. If all you have is a few reservations and a basic scope, you could make the switch in a heartbeat.

what isn't in untangle? fancy options or what?

just curious

sky-knight · 08-07-2008, 11:36 AM

Advanced DHCP support..

Multiple scopes, DHCP scope options, mac range limitations, Dynamic DNS updating...

The list goes on..

DHCP is far more than just "hand out this single range of IP's on this one adapter" Untangle does do basic reservations which is handy...

This is why several of us have asked for an advanced DHCP configuration GUI. Dnsmasq is capable of all of this it is purely a GUI limitation.

For example, supporting Option 66 so those of us with IP phones can use UT's DHCP and make our IP phones automatically boot. Currently Microsoft DHCP supports basically Options 2-76, and 249 natively with the ability to manually define a configuration for any other numerical option. For an example of what you can set with DHCP look at the properties of TCP/IP on any windows station. Litterally everything present within the normal and advanced areas of the IP properties windows can be configured with a Microsoft DHCP server. Currently all UT allows you to do is configure the IP, mask, gateway, and DNS server.

UT also has a bug where IP reservations ignore the DHCP lease time configuration.

Supporting multiple DHCP scopes would allow UT to hand out DHCP addresses for more than just 1 network on a single interface. Say perhaps an office with two "internal" interfaces with different network ranges.

A full DHCP implementation adds a pile of options to help customize the platform. When you need them you really need them, when you don't what UT has is more than enough.

SirBC · 08-07-2008, 07:30 PM

I'm no network guru but I am a forum junkie, and in the SBS newsgroup whenever the question comes up of running DHCP on the router and not SBS, the recommendation always seems to be to let SBS handle DHCP.

Krumpt, why do you want to move DHCP off of SBS? What is it you are trying to accomplish?

sky-knight · 08-08-2008, 12:50 AM

The reason why is Microsoft's DHCP service is just a dead simple yet powerful service... if you have a Windows server on your network and you run DHCP you should be running it on the Windows server. You just do, it's better.

As for why he's moving off? he said he is migrating away from SBS. A very wise decision...

08-07-2008, 08:49 AM	#1 (permalink)
krumpt Newbie Join Date: Aug 2008 Posts: 6	DHCP and RRAS Hi, I have a client that is currently using SBS2003, along with a RV043 Linksys VPN gateway. Current: Code: DSU -- VPN_GW -- SBS < DNS & NAS-- LAN New: Code: DSU -- UT -- SBS, DNS & NAS & LAN Currently the SBS server is handling DHCP and was once doing RRAS. We are trying to migrate away from SBS but for the time being we are going to keep it in place. I like untangle because of RAP and AD integration that it does provide. My primary question is, will there be any ramifications to the AD environment if I disable the DHCP on the SBS and use untangle instead?? Thanks John Last edited by krumpt; 08-07-2008 at 08:53 AM..

08-07-2008, 09:10 AM	#2 (permalink)
sky-knight Join Date: Apr 2008 Location: Phoenix, AZ URLs submitted: 8 Posts: 15,454	Nope, but to be fair the UT DHCP doesn't do everything that the windows server one does. So if you use it for DNS updates, or have some advanced stuff configured you won't be able to make the switch. If all you have is a few reservations and a basic scope, you could make the switch in a heartbeat. __________________ Rob Sandling, BS:SWE, MCP Intouch Technology Phone: 480-272-9889 rob@intouchtechllc.com UntangleAppliances.com Phone: 866-794-8879

08-07-2008, 11:36 AM	#4 (permalink)
sky-knight Join Date: Apr 2008 Location: Phoenix, AZ URLs submitted: 8 Posts: 15,454	Advanced DHCP support.. Multiple scopes, DHCP scope options, mac range limitations, Dynamic DNS updating... The list goes on.. DHCP is far more than just "hand out this single range of IP's on this one adapter" Untangle does do basic reservations which is handy... This is why several of us have asked for an advanced DHCP configuration GUI. Dnsmasq is capable of all of this it is purely a GUI limitation. For example, supporting Option 66 so those of us with IP phones can use UT's DHCP and make our IP phones automatically boot. Currently Microsoft DHCP supports basically Options 2-76, and 249 natively with the ability to manually define a configuration for any other numerical option. For an example of what you can set with DHCP look at the properties of TCP/IP on any windows station. Litterally everything present within the normal and advanced areas of the IP properties windows can be configured with a Microsoft DHCP server. Currently all UT allows you to do is configure the IP, mask, gateway, and DNS server. UT also has a bug where IP reservations ignore the DHCP lease time configuration. Supporting multiple DHCP scopes would allow UT to hand out DHCP addresses for more than just 1 network on a single interface. Say perhaps an office with two "internal" interfaces with different network ranges. A full DHCP implementation adds a pile of options to help customize the platform. When you need them you really need them, when you don't what UT has is more than enough. __________________ Rob Sandling, BS:SWE, MCP Intouch Technology Phone: 480-272-9889 rob@intouchtechllc.com UntangleAppliances.com Phone: 866-794-8879 Last edited by sky-knight; 08-07-2008 at 11:38 AM..

08-08-2008, 12:50 AM	#6 (permalink)
sky-knight Join Date: Apr 2008 Location: Phoenix, AZ URLs submitted: 8 Posts: 15,454	The reason why is Microsoft's DHCP service is just a dead simple yet powerful service... if you have a Windows server on your network and you run DHCP you should be running it on the Windows server. You just do, it's better. As for why he's moving off? he said he is migrating away from SBS. A very wise decision... __________________ Rob Sandling, BS:SWE, MCP Intouch Technology Phone: 480-272-9889 rob@intouchtechllc.com UntangleAppliances.com Phone: 866-794-8879

Protect

Filter

Perform

Connect

Manage

Add-Ons

08-07-2008, 07:30 PM	#5 (permalink)
SirBC Master Untangler Join Date: May 2008 Location: San Carlos, CA URLs submitted: 3 Posts: 101	I'm no network guru but I am a forum junkie, and in the SBS newsgroup whenever the question comes up of running DHCP on the router and not SBS, the recommendation always seems to be to let SBS handle DHCP. Krumpt, why do you want to move DHCP off of SBS? What is it you are trying to accomplish?