http://www.sys-con.com/read/491387.htm
--
George Rogato
Welcome to WISPA
www.wispa.org
http://signup.wispa.org/
WISPA Wants You! Join today!
http://signup.wispa.org/
whether to give private or public address has nothing to do with cost.
The cost per IP, is next to nothing, for an upstream with large block..
Tom DeReggi
RapidDSL Wireless, Inc
IntAirNet- Fixed Wireless Broadband
- Original Message -
From: Ugo Bellavance [EMAIL PROTECTED]
To:
Even if you buy your own from ARIN, if you're that big, then the costs are
nothing - I agree.
I personally do private addressing on all my broadband clients. That allows
me to NAT how I see fit. I someone needs a public IP I do a static 1-1 NAT
for them. So far I've had no issues.
First one must define public address. Meaning public IPs used belonging to
the upstream ISP or the WISP owning their own block of public IPs. Owning
your own block, you must ask... Is it worth the technical admin headache to
manage them, and is the expertise there to do it. And is the benefit
Not sure where the 10+ minutes per install addition for a static IP comes
into play. Takes 30 seconds or so to program that in. Yeah, not quite as
convenient as DHCP, and you run the risk of duplicate IP's if you get
sloppy, but otherwise I see a huge advantage with static.
Renumbering, like
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
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!
Hi,
I just got a postcard today from www.rescueisp.com. After looking at the
website, I did a whois on the domain and found Mark Hopperton as the
owner. And then I found his other website, www.xsfunds.com.
I'm starting to wonder if these guys have it figured out... get all your
money up front
Mike Hammett wrote:
I currently just use a domain on my InterWorx hosting controller for all of
my email. I'm looking to hire Jeremy Davis to setup Freeside for me and I'd
like to setup a new mail system integrated with Freeside. He'd integrate
Freeside into it and I'm awaiting server
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
Don't forget to track who has what dynamic IP address, and when they
had it.
You will need this information with the law enforcement agencies come
a knocking for some kiddie porn peddler using your network.
ryan
On Jan 28, 2008, at 3:16 PM, Jason Hensley wrote:
Not sure where the 10+
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'
My thoughts got ahead of my fingers,, it was supposed to say bigger
and more profitable.
I am looking at it from my standpoint, we have 2000+ customers, 48
POPs and yes, all static IP addresses (a mix of internet routable and
rfc1918). We have 2 full time installers and 2-3 CSRs on
On Mon, 28 Jan 2008, D. Ryan Spott wrote:
Don't forget to track who has what dynamic IP address, and when
they had it.
While this is a good idea...
You will need this information with the law enforcement agencies
come a knocking for some kiddie porn peddler using your network.
This is not
Most customers will be happy with Dynamic DHCP whereby a domain name will
always fine their server.
If you explain that, especially if you describe the elaborate resolutions
that are available to them via Dynamic DHCP including blocks and multiple
servers, won't they be satisfied?
. . . J o n a
You can always use reservations to give a user the same IP each time even
though they are getting it via DHCP. If you ever have to re-number your
whole network without DHCP you may become a convert.
- Original Message -
From: Jonathan Schmidt [EMAIL PROTECTED]
To: 'WISPA General List'
Ryan,
Have you considered using DHCP to manage manually assigned IP addresses?
It offers the best of both worlds. The IPs are statically mapped to
customers, yet the allocations are managed on the server side, eliminating
the concern about ongoing maintenance (lost client settings).
Yea, actually I have looked that and would love to have that. This is
a network I inherited, it was this way when I got it. If it was mine
from the beginning DHCP would have been used (along with RADIUS and
etc).
Ryan
On Jan 28, 2008, at 8:15 PM, [EMAIL PROTECTED] wrote:
Ryan,
Have
I use PPPoE to hand out public IP addresses for Internet traffic. I then
statically assign private IPs for internal management.
IPs are basically free.
--
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com
- Original Message -
From: Ugo Bellavance [EMAIL
On Mon, 28 Jan 2008, Ryan Langseth wrote:
Yea, actually I have looked that and would love to have that.
This is a network I inherited, it was this way when I got it. If
it was mine from the beginning DHCP would have been used (along
with RADIUS and etc).
Do you have remote access to the
On Mon, 28 Jan 2008, [EMAIL PROTECTED] wrote:
Does it make sense to publish/open source these scripts?
Not for me. I do this (consulting) for a living. It is one of the
tools I have in my toolbox that I pull out from time to time.
FWIW, I do include a script that can do this for Mikrotik on
Jaker,
route-map should work, but have you considered wccp (web cache
coordination protocol)?
ip wccp version _
ip wccp web-cache
interface _out interface_
ip wccp web-cache redirect out
ted
On Mon, 28 Jan 2008, Jake VanDewater wrote:
Eric,
I'm interested in how you pulled off the
We are looking into doing DHCP Option 82 for our NMS DHCP subnet for our CPE
devices. If I am understanding this correctly, through this option I will be
able to designate the IP address(es) that are going to be allocated behind that
CPE device. This way I will only have to track MAC address
Eric,
I'm interested in how you pulled off the D-NAT. Did you use a pix to do this?
I have been researching ways to do this with a 2800 Cisco router. From what I
can find I will need to do some aliasing. Can you provide me some more insight
on how you were able to accomplish?
-Jaker
If you have access to the DHCP server then it should be pretty trivial
to migrate. Your current lease file will show all of the IPs and their
associated MAC addresses. All you need to do is build a static lease
file from this information.
I am finally migrating from a static IP to DHCP with
Eric,
Great idea
Tom DeReggi
RapidDSL Wireless, Inc
IntAirNet- Fixed Wireless Broadband
- Original Message -
From: Eric Rogers [EMAIL PROTECTED]
To: WISPA General List wireless@wispa.org
Sent: Monday, January 28, 2008 8:32 PM
Subject: Re: [WISPA] Private vs Public addresses for
Yes but there are some security concerns with DHCP when sharing wireless
sectors. To prevent requires tracking MAC addressess, which is one more
headache to track. Sure if you are doing true 802.11 CPE, no problem, the
link uses the MAC of the CPE that you already know, but when supporting true
They do not like to be called “radio cops.” They insist on “frequency
coordinators.” But on rare occasions at National Football League games,
the NFL’s Game Day Frequency Coordinators have to get a bit insistent
http://www.networkworld.com/news/2008/012508-nfl-radio-cops.html?page=1
--
28 matches
Mail list logo
