My two pence worth... > Then, the second decision: > > 2a) Use RADIUS to assign the IP address. > > 2b) Use DHCP to assign the IP address. > > 2c) Use an RDBMS to store the relevant state needed for IP pool > allocation. > > Chris and Ben at Netservers.co.uk, as well as I, think 2b is > the way to > go. David has voiced that he thinks 2a is the way to go. > Someone else > suggested using a RDBMS to manage IP pool assignment, but I think this > is much more heavyweight than necessary for this application.
IMHO, I would like to see at least support for 2c in addition to the 2b (if thats how its going to go). As its being implemented via pppd plugin, I guess it would not be a huge task to re-write in to another module. As i've iterated before, IMHO, there are many for us, going down the sql db storage route of ip pool state. Dossy, if you can share your code as you progress, i'll ask one of our c guys if they can help with the sql db module. > > The problem that needs to be solved in both 2a and 2b scenarios is what > happens if the same user connects multiple times but they're > supposed to be assigned a static IP? > Chris and Ben want the behavior to be "first > connection gets the static IP, the rest get a dynamic IP" from what I > understand. Can rp-l2tpd not work with pppd doing channel bonding (mlppp)?? Any subsequent connections should be bonded to the first, thus one ip utilised for all connections. > They also want to be able to possibly define a seperate > private range of IPs to allocate from for a specific > username, so again, we need to handle a one-to-many allocation > from username to IPs. IMHO, I would suggest pools are an absolute mandatory requirement. I would think that a pool should be defined, then the username, or user group is tied to the pool. We use radius for pool assignments, thus I would suggest making it, so that radius can respond with a pool name, and this is then used. Radius can then respond with pool name, via user or group reply items, thus enabling all users of type x or of service x, are grouped to use this pool. > > I'm not clear on how this might be solved from RADIUS -- perhaps David > can speak to a specific implementation of a solution. Again, any radius questions, I believe i can answer... fire away... Hope the above is useful. > This flow scenario doesn't cover all the possible use cases that Chris > and Ben have laid out, but I think on closer inspection, some of them > may be mutually exclusive. I'd like to hear more from everyone about > actual use scenarios that MUST be supported, and see if we > can't come up > with appropriate control flows that will support them all. > I have a specific scenario, whereby i wish to dump our expensive 20k cisco 7200 series routers, and replace them with hi-spec linux boxes. I can provide as much detail as required, how detailed do you want our requirements ?? ;) Best Regards, Ben Murphy, murphx Innovative Solutions tel: +44 (0) 870 757 1650 fax: +44 (0) 870 757 1651 e-mail: [EMAIL PROTECTED] This e-mail is confidential and may contain legally privileged information. If you are not named above as an addressee it may be unlawful for you to read, copy, distribute, disclose or otherwise use the information contained within this e-mail. Any views or opinions presented are solely those of the author, and may not represent those of murphx Innovative Solutions.
