Re: [WISPA] OT: Proxim 5054

[lakeland]

I assume you don't have the log in user and password?  

Sent from my Verizon Wireless 4GLTE smartphone

- Reply message -
From: "Dan Petermann" 
To: "Ubiquiti Users Group" 
Subject: [WISPA] OT: Proxim 5054
Date: Mon, Dec 10, 2012 8:26 pm


Does anyone know how to default a Proxim 5054 WITHOUT the stock power supply?

Basically I need to know what pairs to short out to do a full default.
___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless
___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless

[WISPA] OT: Proxim 5054

[Dan Petermann]

Does anyone know how to default a Proxim 5054 WITHOUT the stock power supply?

Basically I need to know what pairs to short out to do a full default.
___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless

Re: [WISPA] IPV6 address allocation

[Tim Densmore]

Networks longer than /64 break SLAAC which may be desirable or 
undesirable, depending on what you're doing.


The info at this site is what I frequently see/hear currently - 
http://www.ipbcop.org/ratified-bcops/bcop-ipv6-subnetting/


In general:
Subnet at the nibble boundary
Do everything you can to make sure that you can aggregate routes
Use /48 for customer allocations (though many people use /56 currently)
Use /64 or /126 or /127 (or LL) for P2P links
Use /128 for loopbacks

As with anything, look at what other forks are doing, read the BCPs and 
RFCs, and then do what you feel makes the most sense.


TD

On 12/10/2012 1:07 PM, Arthur Stephens wrote:
Thinking of splitting our /32 up into large enough subnets to cover 
existing and future equipment on our network. Seems that assigning 
/112 IPV6 to currently assigned /24 IPV4 networks would be more than 
enough addresses. Any thoughts? Ideas?


--
Arthur Stephens
Senior Sales Technician
Ptera Wireless Inc.
PO Box 135
24001 E Mission Suite 50
Liberty Lake, WA 99019
509-927-7837
For technical support visit http://www.ptera.net/support
 - 

"This message may contain confidential and/or propriety information, 
and is intended for the person/entity to whom it was originally 
addressed.
Any use by others is strictly prohibited. Please note that any views 
or opinions presented in this email are solely those of the author and 
are not intended to represent those of the company."



___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless


___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless

Re: [WISPA] SM ICMP Redirect Issue

[LTI - Dennis Burgess]

we can't remove it form the command line of the SM/AP :( rebooting it is
the only way to clear them :(  I have been turning routers to not issue the
ICMP redirect, just stinks that it happens and then 400 SMs can't be
monitored :(   Only ever had this issue with Canopy AP/SMs!


On Mon, Dec 10, 2012 at 2:18 PM, Scott Lambert wrote:

> On Mon, Dec 10, 2012 at 01:27:41PM -0700, LTI - Dennis Burgess wrote:
> > I have a client with a bunch of SMs that end up getting an ICMP redirect
> > error.  They enter a ICMP redirect to their routing table for their
> > monitoring servers, and the only way to clear that out is to reboot them,
> > any workarounds for this?
>
> Tell the routers not to issue ICMP redirects.  The routers can
> forward the packet to the best gateway.  The SM's route tables don't
> get confused when the best gateway changes.
>
> Depending on the SM, you may be able to write scripts to batch
> delete all but the default gateway and connected subnet routes.
>
> --
> Scott LambertKC5MLE   Unix SysAdmin
> lamb...@lambertfam.org
> ___
> Wireless mailing list
> Wireless@wispa.org
> http://lists.wispa.org/mailman/listinfo/wireless
>



-- 

*Dennis Burgess, Mikrotik Certified Trainer** Author of "Learn RouterOS-
Second Edition ”

 Link Technologies, Inc -- Mikrotik & WISP Support
Services

 Office*: 314-735-0270 *Website*: http://www.linktechs.net – *Skype*:
linktechs
* **-- Create Wireless Coverage’s with *www.towercoverage.com* **– 900Mhz –
LTE – 3G – 3.65 – TV Whitespace
**

*
___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless

Re: [WISPA] SM ICMP Redirect Issue

[Scott Lambert]

On Mon, Dec 10, 2012 at 01:27:41PM -0700, LTI - Dennis Burgess wrote:
> I have a client with a bunch of SMs that end up getting an ICMP redirect
> error.  They enter a ICMP redirect to their routing table for their
> monitoring servers, and the only way to clear that out is to reboot them,
> any workarounds for this?

Tell the routers not to issue ICMP redirects.  The routers can
forward the packet to the best gateway.  The SM's route tables don't
get confused when the best gateway changes.

Depending on the SM, you may be able to write scripts to batch
delete all but the default gateway and connected subnet routes.

-- 
Scott LambertKC5MLE   Unix SysAdmin
lamb...@lambertfam.org
___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless

Re: [WISPA] IPV6 address allocation

[Scott Reed]

Recommendation from those in the know is /64 as minimum subnet.
To do IPv6 we have to quit thinking in terms of "that is enough" 
addresses.  It won't be.

You can still do logical sub-divisions.
There are some resources in the WISP Wiki and there is a WISPA IPv6 
mail-list for more assistance.


On 12/10/2012 3:07 PM, Arthur Stephens wrote:
Thinking of splitting our /32 up into large enough subnets to cover 
existing and future equipment on our network. Seems that assigning 
/112 IPV6 to currently assigned /24 IPV4 networks would be more than 
enough addresses. Any thoughts? Ideas?


--
Arthur Stephens
Senior Sales Technician
Ptera Wireless Inc.
PO Box 135
24001 E Mission Suite 50
Liberty Lake, WA 99019
509-927-7837
For technical support visit http://www.ptera.net/support
 - 

"This message may contain confidential and/or propriety information, 
and is intended for the person/entity to whom it was originally 
addressed.
Any use by others is strictly prohibited. Please note that any views 
or opinions presented in this email are solely those of the author and 
are not intended to represent those of the company."



___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless


No virus found in this message.
Checked by AVG - www.avg.com 
Version: 2013.0.2805 / Virus Database: 2634/5948 - Release Date: 12/09/12



--
Scott Reed
Owner
NewWays Networking, LLC
Wireless Networking
Network Design, Installation and Administration

 


Mikrotik Advanced Certified
 
www.nwwnet.net

(765) 855-1060
(765) 439-4253
(855) 231-6239

___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless

[WISPA] SM ICMP Redirect Issue

[LTI - Dennis Burgess]

I have a client with a bunch of SMs that end up getting an ICMP redirect
error.  They enter a ICMP redirect to their routing table for their
monitoring servers, and the only way to clear that out is to reboot them,
any workarounds for this?

-- 

*Dennis Burgess, *
___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless

Re: [WISPA] IPV6 address allocation

[Mike Hammett]

I believe it was recommended at the MUM that each time you need a subnet, you 
take the largest available subnet you have, cut it in half, then assign what 
you need out of that. Each time you need more IP space in a given area, you 
simply expand out the allocation. You then have many non-contiguous blocks 
allocated, but each block can grow.



-
Mike Hammett
Intelligent Computing Solutions
http://www.ics-il.com

- Original Message -
From: "Arthur Stephens" 
To: wireless@wispa.org
Sent: Monday, December 10, 2012 2:07:05 PM
Subject: [WISPA] IPV6 address allocation


Thinking of splitting our /32 up into large enough subnets to cover existing 
and future equipment on our network. Seems that assigning /112 IPV6 to 
currently assigned /24 IPV4 networks would be more than enough addresses. Any 
thoughts? Ideas? 


-- 
Arthur Stephens 
Senior Sales Technician 
Ptera Wireless Inc. 
PO Box 135 
24001 E Mission Suite 50 
Liberty Lake, WA 99019 
509-927-7837 
For technical support visit http://www.ptera.net/support 
- 
"This message may contain confidential and/or propriety information, and is 
intended for the person/entity to whom it was originally addressed. 
Any use by others is strictly prohibited. Please note that any views or 
opinions presented in this email are solely those of the author and are not 
intended to represent those of the company." 

___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless
___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless

[WISPA] IPV6 address allocation

[Arthur Stephens]

Thinking of splitting our /32 up into large enough subnets to cover
existing and future equipment on our network. Seems that assigning /112
IPV6 to currently assigned /24 IPV4 networks would be more than enough
addresses. Any thoughts? Ideas?

-- 
Arthur Stephens
Senior Sales Technician
Ptera Wireless Inc.
PO Box 135
24001 E Mission Suite 50
Liberty Lake, WA 99019
509-927-7837
For technical support visit http://www.ptera.net/support
 -

"This message may contain confidential and/or propriety information, and is
intended for the person/entity to whom it was originally addressed.
Any use by others is strictly prohibited. Please note that any views or
opinions presented in this email are solely those of the author and are not
intended to represent those of the company."
___
Wireless mailing list
Wireless@wispa.org
http://lists.wispa.org/mailman/listinfo/wireless