.
I'm sure someday, somewhere I will.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of rabbtux rabbtux
Sent: Wednesday, January 30, 2008 1:33 PM
To: WISPA General List
Subject: Re: [WISPA] Private vs Public addresses for end-users
Have you had any vpn
: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Tom DeReggi
Sent: Monday, January 28, 2008 2:47 PM
To: WISPA General List
Subject: Re: [WISPA] Private vs Public addresses for end-users
whether to give private or public address has nothing to do with cost.
The cost per IP, is next
List
Subject: Re: [WISPA] Private vs Public addresses for end-users
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
On Jan 29, 2008 11:52 AM, Bryan Scott [EMAIL PROTECTED] wrote:
Tom DeReggi wrote:
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
On Tue, 29 Jan 2008, Andrew Niemantsverdriet wrote:
So what happens when the customer plugs the radio into the switch
and is broadcasting his local DHCP info to everybody? That would
really mess up the network.
Depends on the network. On any network that I set up (at least
where it is my
Unless you have a H.323 compliant firewall, 1 to 1 NAT will generally
break H.323 (Netmeeting)
Also, some VPN clients default config doesn't work properly through NAT.
John
Ugo Bellavance wrote:
Jason Hensley wrote:
Even if you buy your own from ARIN, if you're that big, then the costs
]
To: wireless@wispa.org
Sent: Monday, January 28, 2008 2:01 PM
Subject: [WISPA] Private vs Public addresses for end-users
Hi,
I was wondering what were the considerations of giving out private
addressing to end users. Are public addresses worth the costs?
The project is to provide internet access
.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Tom DeReggi
Sent: Monday, January 28, 2008 2:47 PM
To: WISPA General List
Subject: Re: [WISPA] Private vs Public addresses for end-users
whether to give private or public address has nothing to do with cost
-
From: Ugo Bellavance [EMAIL PROTECTED]
To: wireless@wispa.org
Sent: Monday, January 28, 2008 4:37 PM
Subject: Re: [WISPA] Private vs Public addresses for end-users
Tom DeReggi wrote:
whether to give private or public address has nothing to do with cost.
Oh, what are the thing to consider
PROTECTED] On
Behalf Of Ryan Langseth
Sent: Monday, January 28, 2008 5:12 PM
To: WISPA General List
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
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!
the time.
Tom DeReggi
RapidDSL Wireless, Inc
IntAirNet- Fixed Wireless Broadband
- Original Message -
From: Ryan Langseth [EMAIL PROTECTED]
To: WISPA General List wireless@wispa.org
Sent: Monday, January 28, 2008 6:11 PM
Subject: Re: [WISPA] Private vs Public addresses for end-users
]
On
Behalf Of Ryan Langseth
Sent: Monday, January 28, 2008 5:12 PM
To: WISPA General List
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
] [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
easy for me.
For me, static works, dhcp doesn't. Of course, everyone is different.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On
Behalf Of Ryan Langseth
Sent: Monday, January 28, 2008 5:12 PM
To: WISPA General List
Subject: Re: [WISPA] Private vs Public
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
a t h a n
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Eric Rogers
Sent: Monday, January 28, 2008 7:32 PM
To: WISPA General List
Subject: Re: [WISPA] Private vs Public addresses for end-users
If the default for most routers is DHCP, then give
' wireless@wispa.org
Sent: Monday, January 28, 2008 7:01 PM
Subject: Re: [WISPA] Private vs Public addresses for end-users
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
:12 PM
To: WISPA General List
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
, 2008 5:12 PM
To: WISPA General List
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
PROTECTED]
To: wireless@wispa.org
Sent: Monday, January 28, 2008 1:01 PM
Subject: [WISPA] Private vs Public addresses for end-users
Hi,
I was wondering what were the considerations of giving out private
addressing to end users. Are public addresses worth the costs?
The project is to provide
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
PROTECTED]
To: wireless@wispa.org
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
-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On
Behalf Of Ryan Langseth
Sent: Monday, January 28, 2008 5:12 PM
To: WISPA General List
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
Date: Mon, 28 Jan 2008 20:32:26 -0500
From: [EMAIL PROTECTED]
To: wireless@wispa.org
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
, everyone is
different.
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On
Behalf Of Ryan Langseth
Sent: Monday, January 28, 2008 5:12 PM
To: WISPA General List
Subject: Re: [WISPA] Private vs Public addresses for end-users
There are things like looking
: [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
: [WISPA] Private vs Public addresses for end-users
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
30 matches
Mail list logo
