One network, one server, 2 dsl lines

Toggle sidebar Toggle sidebar
K

KMZ-89

Prominent
Apr 16, 2017
2
0
510
In my workplace we have only one server, one limited dsl line with high bandwidth and another unlimited dsl line with low bandwidth . They are all connected to one network wired and wireless through out the building, connecting over 100 PC, laptop and smart phones.

When the limited package of the first dsl line runs up, I have to manually replace it with the unlimited low bandwidth dsl, changing its router IP to meet the gateway address previously set by the DHCP/Static configuration.

I am trying to figure out a way to solve this situation that could enable me to connect both dsl line to the network and allow only specific PCs, Laptops and Smart devices to use the high bandwidth and leave the others (usually guests) to the low bandwidth line, but allow all of them to be connected to the server. IS THAT POSSIBLE?

Noting that I am not trying to load balance here, I only need some devices to be routed to the first WAN, and other devices to the second wan.

The high bandwidth router have white/black list MAC filtering capabilities, but when I tried to connect it with the other router I struck by the fact that they can't run simultaneously and only one has to be the internet gateway.
 
Solution
Solandri

It's impossible to do this completely automatically (via DHCP) because someone has to manually decide if a new device should connect to the high bandwidth or the low bandwidth line. This would be the case even with a more sophisticated router.

If you use the method kanewolf suggested, new devices will auto-configure via DHCP and default to the low bandwidth connection. Only if someone requests a device be "upgraded" to the high bandwidth connection do you need to manually set up a static gateway address.

The only change I would make to kanewolf's suggestion is to make sure you limit the DHCP range. So for example...
Sort by date Sort by votes
kanewolf

kanewolf

Titan
Moderator
May 29, 2013
37,316
3,275
156,790
They both can't be DHCP. IF you have a limited set of devices that need high bandwidth you COULD manually configure the IP information for those devices using the high BW router as the gateway. You would disable DHCP on that router. All devices that DHCP would get the low bandwidth router.

So low BW router == 192.168.1.1 with DHCP enabled. High BW router == 192.168.1.254 with NO DHCP enabled. Manually configure the devices that have to point to 192.168.1.254.
 
Upvote 0 Downvote
K

KMZ-89

Prominent
Apr 16, 2017
2
0
510


I would prefer not to go static because I may not be available to set configuration for new devices.

Can I combine the two WANs into one gateway with one IP that also serves as DHCP server? Can a router in bridge mode do this job?

 
Upvote 0 Downvote
kanewolf

kanewolf

Titan
Moderator
May 29, 2013
37,316
3,275
156,790
If you don't want to do my suggested implementation, then you are going to need a more sophisticated router. You would need a dual WAN router and some static routes to force traffic the way you want it.

If you can't set a static, then they new device gets low bandwidth. It would still work, but not get high bandwidth.
 
Upvote 0 Downvote
Solandri

Solandri

Illustrious
Jan 4, 2012
4,919
98
39,240

It's impossible to do this completely automatically (via DHCP) because someone has to manually decide if a new device should connect to the high bandwidth or the low bandwidth line. This would be the case even with a more sophisticated router.

If you use the method kanewolf suggested, new devices will auto-configure via DHCP and default to the low bandwidth connection. Only if someone requests a device be "upgraded" to the high bandwidth connection do you need to manually set up a static gateway address.

The only change I would make to kanewolf's suggestion is to make sure you limit the DHCP range. So for example 192.168.1.2-199 could be allocated via DHCP. Any devices you want using the high bandwidth connection, you can set a static IP in the 192.168.1.200-253 range, with 192.168.1.254 as their gateway. (Ideally, you'd only have to set the gateway manually on a privileged device, and it retains the other settings given to it via DHCP. But nearly every OS I've seen is all or nothing when it comes to DHCP.)
 
Upvote 0 Downvote
Solution
You must log in or register to reply here.

TRENDING THREADS

Latest posts

Moderators online

Share this page

COMPANY
RESOURCES
FOLLOW
Top Bottom