There are reasons to have PPPoE other than IP address assignment.
----- Mike Hammett Intelligent Computing Solutions http://www.ics-il.com ----- Original Message ----- From: "Forrest Christian (List Account)" <[email protected]> To: "af" <[email protected]> Sent: Wednesday, April 15, 2015 3:02:50 AM Subject: Re: [AFMUG] Providing public routed IPs to customers (WISP HAT ON) We have a subnet (or a couple of subnets, as sites have grown) at each tower, and an public IP statically assigned to each customer. The radio gets a managment address out of 172.[16-31].x.x which corresponds to the public IP address. No DHCP anywhere, no PPPoE. But again, we have an /18 and a /19 assigned to us from back before NAT really existed and DHCP implementations from the early '90's kinda sucked. We've played with PPPoE and DHCP, but kinda have been spoiled by the simplicity and reliability of a statically numbered network. -forrest On Tue, Apr 14, 2015 at 6:20 PM, Josh Reynolds < [email protected] > wrote: For those of you currently providing public/routed ips to customers? What is your topology like and delivery method? Looking at doing a few things, have considered a few options, and wanted to look out there and see what other people are doing. Thanks -- Josh Reynolds CIO, SPITwSPOTS www.spitwspots.com -- Forrest Christian CEO , PacketFlux Technologies, Inc. Tel: 406-449-3345 | Address: 3577 Countryside Road, Helena, MT 59602 [email protected] | http://www.packetflux.com
