Karlnet
[Top] [All Lists]

RE: [Karlnet] Reduction of Karlnet features w/out notification.

To: <david.m.holligan@rraz.net>,"'Karlnet Mailing List'" <karlnet@WISPNotes.com>
Subject: RE: [Karlnet] Reduction of Karlnet features w/out notification.
From: "Kevin Knuth" <kknuth@karlnet.com>
Reply-to: Karlnet Mailing List <karlnet@WISPNotes.com>
Date: Fri, 14 Nov 2003 14:17:01 -0600
List-post: <mailto:karlnet@WISPNotes.com>
RADIUS is still in our build- not sure what you mean with this question.


RADIUS is used at the base station- not in a single client CPE.

Kevin

**************************************
Kevin R. Knuth
Business Development Manager
North America
260-424-9690 Regional Office
614-822-5275 Corporate Office
kknuth@karlnet.com
www.karlnet.com
**************************************
 


-----Original Message-----
From: karlnet-bounces@WISPNotes.com
[mailto:karlnet-bounces@WISPNotes.com] On Behalf Of David M Holligan
Sent: Friday, November 14, 2003 12:42 PM
To: Karlnet Mailing List
Subject: Re: [Karlnet] Reduction of Karlnet features w/out notification.


When will the RADIUS feature be returned?

Thanks
Dave



David Holligan
Red River Wireless, a division of Red River Communications
2011 McCulloch Blvd, Suite 8     Lake Havasu City AZ 86403
Phone: 928-505-2999                       Fax:928-505-3595
Tech Support: 928-505-2935         Toll Free: 888-388-2999
http://www.rraz.net



Support wrote:
> This feature(NAT/DHCP) has been returned to the license-it site. We 
> apologize for any inconvenience this may have caused. Thanks for all 
> the valuable feedback!.
> 
> KarlNet Support
> RLM
> 
> -----Original Message-----
> From: karlnet-bounces@WISPNotes.com 
> [mailto:karlnet-bounces@WISPNotes.com]On Behalf Of Steve Deaton
> Sent: Thursday, November 13, 2003 4:34 PM
> To: 'Karlnet Mailing List'
> Subject: [Karlnet] Reduction of Karlnet features w/out notification.
> 
> 
> Just FYI, not trying to start any flaming, but be aware that karlnet 
> is working on removing features like NAT & DHCP from the SR-4000 & 
> possibly others.  We started flashing CPE's for our contractors to 
> have next week & were met with an absence of NAT and DHCP as options.

> This was a change that was made last night without notification, thus 
> I am posting here.
> 
> Our standardized install entails contractors picking up RG's or KN's 
> with NAT & DHCP so they always have a standard installation & don't 
> need to understand IP addressing.  This is important when you have 
> several different subnets that they will be connecting to (i.e. 
> different towers & channels).  We then connect remotely on an 
> as-needed basis & change settings if requested (i.e. client needs a 
> public or static IP), but by default they're getting a NAT IP.  We 
> have found this to be the best way to simplify things for installers.
> 
> I'd appreciate input on this concept as I know Karlnet monitors this 
> thread.  If many ISP's use the NAT & DHCP it may help motivate them in

> our favor.  If not, it will help karlnet relieve overhead by not 
> offering these features in the future.  To confirm, if you're using 
> bridging or routing as a normal setup, this won't effect anything, so 
> don't stress.  However, if you normally implement NAT/DHCP it may not 
> be there anymore as of 7pm last night.  You will still pay the same 
> for the licenses, but received reduced features unless you notify 
> karlnet.  We found them to be interested in working with us to meet 
> our needs, so this is more of a speed bump than a brick wall.  They 
> have offered to edit our web login, possibly all web logins, at 
> license-it.com to offer options for NAT/DHCP, so voice your approval 
> or disapproval so that they know what their users like.
> 
> 
> Regards,
> 
> Steve Deaton
> IT Director
> Texas Broadband, Inc.
> (888)868.3835 ext 85 (office)
> 979.289.0148 (office)
> 979.289.5117 (fax)
> 
> 
> -----Original Message-----
> From: karlnet-bounces@WISPNotes.com 
> [mailto:karlnet-bounces@WISPNotes.com] On Behalf Of Ben Polson
> Sent: Thursday, November 13, 2003 2:38 PM
> To: Karlnet Mailing List
> Subject: RE: [Karlnet] Conversion of SNR values to dB
> 
> Thanks Phil.  Sure, I'd love to see what this has produced for you.
> 
> 
>>-----Original Message-----
>>From: karlnet-bounces@WISPNotes.com 
>>[mailto:karlnet-bounces@WISPNotes.com]On Behalf Of Phil
>>Sent: Thursday, November 13, 2003 12:33 PM
>>To: 'Karlnet Mailing List'
>>Subject: RE: [Karlnet] Conversion of SNR values to dB
>>
>>
>>I'm not sure if it is correct but I've been dividing by 2 and then 
>>subtracting 95.  I can show some examples of my S/N graphs that I 
>>generate for all of our customers and APs if anyone wants to see them.

>>(not attached of course)
>>
>>
>>-----Original Message-----
>>From: Ben Polson [mailto:bsp@bandwave.net]
>>Sent: Tuesday, November 04, 2003 11:33 AM
>>To: Karlnet Mailing List
>>Subject: [Karlnet] Conversion of SNR values to dB
>>
>>Does anyone know the algorithm to convert the INTEGER values returned 
>>from the OIDs for signal and noise into dB values?
>>
>>A signal value of 86 and noise value of 10 aren't as helpful as the dB

>>values.  Thanks in advance.
>>
>>-Ben.
>>
>>_______________________________________________
>>Karlnet mailing list
>>Karlnet@WISPNotes.com 
>>http://lists.wispnotes.com/mailman/listinfo/karlnet
>>
> 
> _______________________________________________
> Karlnet mailing list
> Karlnet@WISPNotes.com 
> http://lists.wispnotes.com/mailman/listinfo/karlnet
> 
> _______________________________________________
> Karlnet mailing list
> Karlnet@WISPNotes.com 
> http://lists.wispnotes.com/mailman/listinfo/karlnet
> 
> _______________________________________________
> Karlnet mailing list
> Karlnet@WISPNotes.com 
> http://lists.wispnotes.com/mailman/listinfo/karlnet
> 

_______________________________________________
Karlnet mailing list
Karlnet@WISPNotes.com
http://lists.wispnotes.com/mailman/listinfo/karlnet


_______________________________________________
Karlnet mailing list
Karlnet@WISPNotes.com
http://lists.wispnotes.com/mailman/listinfo/karlnet

<Prev in Thread] Current Thread [Next in Thread>