Eric, Great idea
Tom DeReggi RapidDSL & Wireless, Inc IntAirNet- Fixed Wireless Broadband ----- Original Message ----- From: "Eric Rogers" <[EMAIL PROTECTED]> To: "WISPA General List" <[email protected]> Sent: Monday, January 28, 2008 8:32 PM Subject: Re: [WISPA] Private vs Public addresses for end-users > If the default for most routers is DHCP, then give it a private block > and then D-NAT all port 80 traffic to one of your servers and give them > a spash-page that says..."Your router lost its' configuration. Here are > instructions of how to reset it." > > Don't forget, the default for most routers' wireless is wide-open. If > you lock them out by default...it is in both of your interests to get it > set back up and secure. I'll spend the extra 15-20 minutes to walk them > through a configuration so their neighbor has to pay for a connection. > > Eric > > > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On > Behalf Of Tom DeReggi > Sent: Monday, January 28, 2008 6:31 PM > To: WISPA General List > Subject: Re: [WISPA] Private vs Public addresses for end-users > > The biggest cost in using Static IP is after support. Thinks liek > Linksys > routers are notorious for loosing their configurations. > When teh configuration is lost, your on the phone for an hour walking > your > customer through how to enter the IP back in. > MOst commodity routers default to DHCP, so if it loses its config, > rebooting > will still get it a working IP with out a phone call for > reconfiguration. > However, we only use Public Static IPs. We typically charge more for our > > service and justify the higher charge because of added benefits such as > Static IP benefits. We are willing to spend the time. > > Tom DeReggi > RapidDSL & Wireless, Inc > IntAirNet- Fixed Wireless Broadband > > > ----- Original Message ----- > From: "Ryan Langseth" <[EMAIL PROTECTED]> > To: "WISPA General List" <[email protected]> > Sent: Monday, January 28, 2008 6:11 PM > Subject: Re: [WISPA] Private vs Public addresses for end-users > > >> There are things like looking at the customer base. >> >> 1) are they likely to need incoming connections ( This is mainly for >> businesses ) >> 2) are they likely to get a worm and have it start spamming ( I hate >> trying to track down a spammy machine behind NAT ... its not hard just >> annoying) >> 3) are they going to have problems with double NAT, the customers >> router will be doing nat also. Certain system do not handle that very >> nicely >> >> Frankly I hate using Private IPs for customers at all, I also >> strongly dislike not doing DHCP unless the customer is paying for that >> static. >> Static IP addressing is a PITA if you have to renumber, obivously >> with privates that problem is largely gone. >> >> Depending on where you are doing your NAT, I would suggest if you go >> that route to do it at your Head End, not at your edge routers. That >> way you can implement one of the common IDS/IPS systems to find >> problem customers (virus, etc) . >> >> Not doing DHCP, if you plan on being profitable, imo, is also a major >> mistake. You will end up consuming 10+ minutes of your install techs >> and CSRs time per install. >> >> >> Ryan >> >> On Jan 28, 2008, at 3:37 PM, Ugo Bellavance wrote: >> >>> Tom DeReggi wrote: >>>> whether to give private or public address has nothing to do with >>>> cost. >>>> >>> >>> Oh, what are the thing to consider exactly? >>> >>> Regards, >>> >>> Ugo Bellavance >>> >>> >>> >>> > ------------------------------------------------------------------------ > -------- >>> WISPA Wants You! Join today! >>> http://signup.wispa.org/ >>> > ------------------------------------------------------------------------ > -------- >>> >>> WISPA Wireless List: [email protected] >>> >>> Subscribe/Unsubscribe: >>> http://lists.wispa.org/mailman/listinfo/wireless >>> >>> Archives: http://lists.wispa.org/pipermail/wireless/ >> >> >> >> > ------------------------------------------------------------------------ > -------- >> WISPA Wants You! Join today! >> http://signup.wispa.org/ >> > ------------------------------------------------------------------------ > -------- >> >> WISPA Wireless List: [email protected] >> >> Subscribe/Unsubscribe: >> http://lists.wispa.org/mailman/listinfo/wireless >> >> Archives: http://lists.wispa.org/pipermail/wireless/ > > > > ------------------------------------------------------------------------ > -------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > ------------------------------------------------------------------------ > -------- > > WISPA Wireless List: [email protected] > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ > > > -------------------------------------------------------------------------------- > WISPA Wants You! Join today! > http://signup.wispa.org/ > -------------------------------------------------------------------------------- > > WISPA Wireless List: [email protected] > > Subscribe/Unsubscribe: > http://lists.wispa.org/mailman/listinfo/wireless > > Archives: http://lists.wispa.org/pipermail/wireless/ -------------------------------------------------------------------------------- WISPA Wants You! Join today! http://signup.wispa.org/ -------------------------------------------------------------------------------- WISPA Wireless List: [email protected] Subscribe/Unsubscribe: http://lists.wispa.org/mailman/listinfo/wireless Archives: http://lists.wispa.org/pipermail/wireless/
