IP Pool

paulct · July 5, 2016, 1:25pm

Hi

Probably a stupid questions. If one was using usermanger for radius across the network, would one set the ip pools on the radius Mikrotik or on the end site Mikrotiks where the pppoe-servers exist? This is for dynamic pppoe IP’s

Thanks

paulct · July 7, 2016, 7:16am

Bump

paulct · July 11, 2016, 3:33pm

Would I need to create e.g an eoip tunnel from each Mikrotik that has a pppoe server to the Mikrotik which is hosting usermanager in order for a “single” IP pool to be used?

ZeroByte · July 11, 2016, 4:20pm

There are pros/cons to each method.
If you run the pool on the RADIUS server itself, then there’s the chance that the PPPoE servers can get out of sync with the state of your pools in RADIUS.
On the other hand, this allows you to use a single pool of addresses between several concentrators.

Conversely, you can let each concentrator have its own unique pool of addresses.
The benefit of this is that you don’t even need to specify the pool in RADIUS - let the concentrator pick its own addresses however it sees fit. You can still specify a static address in a particular user’s RADIUS profile if you like, and that will override the default dynamic address.
The drawback to this method is that each concentrator needs to have a dedicated pool of dynamic addresses.
(this is actually helpful if you’re allocating your addresses in a way that facilitates route aggregation, though)

I generally preferred (when I worked at an NSP) to use dedicated pools per server.

paulct · July 12, 2016, 9:54am

ZeroByte:

There are pros/cons to each method.
If you run the pool on the RADIUS server itself, then there’s the chance that the PPPoE servers can get out of sync with the state of your pools in RADIUS.
On the other hand, this allows you to use a single pool of addresses between several concentrators.

Conversely, you can let each concentrator have its own unique pool of addresses.
The benefit of this is that you don’t even need to specify the pool in RADIUS - let the concentrator pick its own addresses however it sees fit. You can still specify a static address in a particular user’s RADIUS profile if you like, and that will override the default dynamic address.
The drawback to this method is that each concentrator needs to have a dedicated pool of dynamic addresses.
(this is actually helpful if you’re allocating your addresses in a way that facilitates route aggregation, though)

I generally preferred (when I worked at an NSP) to use dedicated pools per server.

+1 thanks for the help. Currently deciding on Freeradius or usermanager. From the above I think static IP’s would be better.