date:20060917

Re: [WISPA] I need a climber / tower maintainer...

2006-09-17 Thread Mark Koskenmaki

I don't know if things have been arranged yet.

Are you in the area?




+++
neofast.net - fast internet for North East Oregon and South East Washington
email me at mark at neofast dot net
541-969-8200
Direct commercial inquiries to purchasing at neofast dot net

- Original Message - 
From: <[EMAIL PROTECTED]>
To: 
Sent: Saturday, September 16, 2006 4:14 PM
Subject: Re: [WISPA] I need a climber / tower maintainer...


> Mark, Do you still have a need for these services?
>
> Regards,
>
> Mike
>
>
> I need someone who will do some reasonably priced tower climbing  AND
> maintain a sadly neglected tower.The guys are not properly  tensioned,
> and haven't been since it was erected some 5 - 7 years  ago.
>
> I want to put stuff on this tower, but I refuse to be responsible  for
> damage, should something happen because of the improper guy tension,  etc.
>
> http://neofast.net/users/mark/pics/wp/klrftrans.jpg
>
> The tower  owners / station managers have asked for references for someone
to
> do  this.
>
> How do I go about finding people?   I don't see nuttin  the yellow pages.
>
>
> This is for Eastern  Oregon.
>
> Mark
>
>






> -- 
> WISPA Wireless List: wireless@wispa.org
>
> Subscribe/Unsubscribe:
> http://lists.wispa.org/mailman/listinfo/wireless
>
> Archives: http://lists.wispa.org/pipermail/wireless/
>

-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Re: [WISPA] Initial SR9 test results

2006-09-17 Thread Leon D. Zetekoff, NCE


Larry Yunker wrote:
Sounds like multipath you are probably picking up a bounced signal 
on one end.
could be  I think we saw this somewhere else but I can't remember; 
we did so much on Thursday it sometimes is a blur :-(
I think the plan is to try a yagi up on the tower in place of the sector 
for a test and check the signal at the one 900 CPE in the attic 
remotely. (We've only got one 900 CPE currently.)


Any other ideas?

Thanks leon

--
*Leon Zetekoff*
Proprietor  
*Work:* 484-335-9920
*Mobile:* 610-223-8642
*Fax:* 484-335-9921
*Email:* [EMAIL PROTECTED] 
*http://www.linkedin.com/in/leonzetekoff*
*BackWoods Wireless*
 505 B Main Street
 
Blandon, PA 19510

"Bringing Broadband Technology to Rural Areas"

See who we know in common  	Want 
a signature like this? 


begin:vcard
fn:Leon Zetekoff
n:Zetekoff;Leon
org:BackWoods Wireless
adr;dom:;;505 B Main Street;Blandon;PA;19510
email;internet:[EMAIL PROTECTED]
title:Owner
tel;work:484-335-9920
tel;fax:484-335-9921
tel;home:610-916-0230
tel;cell:610-223-8642
x-mozilla-html:TRUE
url:http://www.backwoodswireless.net
version:2.1
end:vcard

-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Re: [WISPA] Initial SR9 test results

2006-09-17 Thread Leon D. Zetekoff, NCE


Larry Yunker wrote:

How much difference are you seeing?  2db or more?

yeah maybe 6-10 I think


- Original Message - From: "Leon D. Zetekoff, NCE" 
<[EMAIL PROTECTED]>

To: "Larry Yunker" <[EMAIL PROTECTED]>
Cc: "WISPA General List" 
Sent: Sunday, September 17, 2006 5:55 PM
Subject: Re: [WISPA] Initial SR9 test results



Larry Yunker wrote:

Let us know more about the configuration(s) and maybe we can figure
out what else you should try.

OK here's the Sector antenna:

http://www.teletronics.com/tant900sector12-5dbi.html

The yagi's are PacWireless YA9-13

Interesting that at the customer with the yagi in the attic, the
CPE-tower signal was weaker than the tower-CPE signal. Both running the
Ubiquiti 900 cards on a  RB112 and the sector antenna is 12.5 db gain so
you would think the signals at each end should be pretty close.

THanks leon




 





--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/






begin:vcard
fn:Leon Zetekoff
n:Zetekoff;Leon
org:BackWoods Wireless
adr;dom:;;505 B Main Street;Blandon;PA;19510
email;internet:[EMAIL PROTECTED]
title:Owner
tel;home:610-916-0230
tel;cell:610-223-8642
x-mozilla-html:TRUE
url:http://www.backwoodswireless.net
version:2.1
end:vcard

-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Re: [WISPA] Initial SR9 test results

2006-09-17 Thread Larry Yunker

How much difference are you seeing?  2db or more?

- Original Message - 
From: "Leon D. Zetekoff, NCE" <[EMAIL PROTECTED]>

To: "Larry Yunker" <[EMAIL PROTECTED]>
Cc: "WISPA General List" 
Sent: Sunday, September 17, 2006 5:55 PM
Subject: Re: [WISPA] Initial SR9 test results

Larry Yunker wrote:

Let us know more about the configuration(s) and maybe we can figure
out what else you should try.

OK here's the Sector antenna:

http://www.teletronics.com/tant900sector12-5dbi.html

The yagi's are PacWireless YA9-13

Interesting that at the customer with the yagi in the attic, the
CPE-tower signal was weaker than the tower-CPE signal. Both running the
Ubiquiti 900 cards on a  RB112 and the sector antenna is 12.5 db gain so
you would think the signals at each end should be pretty close.

THanks leon

--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Re: [WISPA] Initial SR9 test results

2006-09-17 Thread Leon D. Zetekoff, NCE


Larry Yunker wrote:
Let us know more about the configuration(s) and maybe we can figure 
out what else you should try.

OK here's the Sector antenna:

http://www.teletronics.com/tant900sector12-5dbi.html

The yagi's are PacWireless YA9-13

Interesting that at the customer with the yagi in the attic, the 
CPE-tower signal was weaker than the tower-CPE signal. Both running the 
Ubiquiti 900 cards on a  RB112 and the sector antenna is 12.5 db gain so 
you would think the signals at each end should be pretty close.


THanks leon
begin:vcard
fn:Leon Zetekoff
n:Zetekoff;Leon
org:BackWoods Wireless
adr;dom:;;505 B Main Street;Blandon;PA;19510
email;internet:[EMAIL PROTECTED]
title:Owner
tel;home:610-916-0230
tel;cell:610-223-8642
x-mozilla-html:TRUE
url:http://www.backwoodswireless.net
version:2.1
end:vcard

-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Re: [WISPA] Initial SR9 test results

2006-09-17 Thread Leon D. Zetekoff, NCE


Larry Yunker wrote:
What antenna/cable solution are you using on the client side of the 
link? How far are you trying to shoot?
Down in Virginia we're using a 13db (11 ele) Yagi horizontal shooting to 
a tower where there is a 120* hor sector antenna. Antenna pigtail 
connects through a double-barrel right into the radio. Any ideas? I am 
stumped as this should work; in one case the yagi is in the attic and 
the signal is horrible. We're trying to shoot from 1-6 miles or so. We 
did get a -65 way on the other side up in the clear when we were driving 
around on Thurs.


Thanks leon
- Original Message - From: "Leon D. Zetekoff, NCE" 
<[EMAIL PROTECTED]>

To: "Lonnie Nunweiler" <[EMAIL PROTECTED]>
Cc: "WISPA General List" 
Sent: Sunday, September 17, 2006 2:04 PM
Subject: Re: [WISPA] Initial SR9 test results



Lonnie Nunweiler wrote:

Vertical and horizontal were tried.  The results are the same.

Thanks Lonnie...we're trying some Mikrotik with the 900 cards and not
having much luck through the trees using a 900 120* sector H-pol

Leon


Lonnie

On 9/17/06, *Leon D. Zetekoff, NCE* < [EMAIL PROTECTED]
> wrote:

Lonnie Nunweiler wrote:

http://forums.star-os.com/showthread.php?t=5838

I just posted our early rsults of the 900 MHz gear.  Needless 
to say
this is better than I was hoping for and this stuff has a FIRM 
place

in our tool chest.  Forget higher power on 2.4 GHz to get through
some
trees.  This is truly NON LOS.


Hi Lonnie...what polarization did you use?

Thanks leon

-- *Leon Zetekoff*
Proprietor
*Work:* 484-335-9920
*Mobile:* 610-223-8642
*Fax:* 484-335-9921
*Email:* [EMAIL PROTECTED] 
*http://www.linkedin.com/in/leonzetekoff*
*BackWoods Wireless*
 505 B Main Street

 


Blandon, PA 19510
"Bringing Broadband Technology to Rural Areas"

See who we know in common
 Want a signature like
this? 


--
WISPA Wireless List: wireless@wispa.org 

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/







--
Lonnie Nunweiler
Valemount Networks Corporation
http://www.star-os.com/


--
*Leon Zetekoff*
Proprietor
*Work:* 484-335-9920
*Mobile:* 610-223-8642
*Fax:* 484-335-9921
*Email:* [EMAIL PROTECTED] 
*http://www.linkedin.com/in/leonzetekoff*
*BackWoods Wireless*
 505 B Main Street
 


Blandon, PA 19510
"Bringing Broadband Technology to Rural Areas"

See who we know in common  Want
a signature like this? 





 





--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/






begin:vcard
fn:Leon Zetekoff
n:Zetekoff;Leon
org:BackWoods Wireless
adr;dom:;;505 B Main Street;Blandon;PA;19510
email;internet:[EMAIL PROTECTED]
title:Owner
tel;home:610-916-0230
tel;cell:610-223-8642
x-mozilla-html:TRUE
url:http://www.backwoodswireless.net
version:2.1
end:vcard

-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Re: [WISPA] Initial SR9 test results

2006-09-17 Thread Larry Yunker

What antenna/cable solution are you using on the client side of the link? 
How far are you trying to shoot?


- Larry

- Original Message - 
From: "Leon D. Zetekoff, NCE" <[EMAIL PROTECTED]>

To: "Lonnie Nunweiler" <[EMAIL PROTECTED]>
Cc: "WISPA General List" 
Sent: Sunday, September 17, 2006 2:04 PM
Subject: Re: [WISPA] Initial SR9 test results



Lonnie Nunweiler wrote:

Vertical and horizontal were tried.  The results are the same.

Thanks Lonnie...we're trying some Mikrotik with the 900 cards and not
having much luck through the trees using a 900 120* sector H-pol

Leon


Lonnie

On 9/17/06, *Leon D. Zetekoff, NCE* < [EMAIL PROTECTED]
> wrote:

Lonnie Nunweiler wrote:

http://forums.star-os.com/showthread.php?t=5838

I just posted our early rsults of the 900 MHz gear.  Needless to say
this is better than I was hoping for and this stuff has a FIRM place
in our tool chest.  Forget higher power on 2.4 GHz to get through
some
trees.  This is truly NON LOS.


Hi Lonnie...what polarization did you use?

Thanks leon

-- 
*Leon Zetekoff*

Proprietor
*Work:* 484-335-9920
*Mobile:* 610-223-8642
*Fax:* 484-335-9921
*Email:* [EMAIL PROTECTED] 
*http://www.linkedin.com/in/leonzetekoff*
*BackWoods Wireless*
 505 B Main Street


Blandon, PA 19510
"Bringing Broadband Technology to Rural Areas"

See who we know in common
 Want a signature like
this? 


--
WISPA Wireless List: wireless@wispa.org 

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/







--
Lonnie Nunweiler
Valemount Networks Corporation
http://www.star-os.com/


--
*Leon Zetekoff*
Proprietor
*Work:* 484-335-9920
*Mobile:* 610-223-8642
*Fax:* 484-335-9921
*Email:* [EMAIL PROTECTED] 
*http://www.linkedin.com/in/leonzetekoff*
*BackWoods Wireless*
 505 B Main Street

Blandon, PA 19510
"Bringing Broadband Technology to Rural Areas"

See who we know in common  Want
a signature like this? 









--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/



--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

RE: [WISPA] Routing woes.....

2006-09-17 Thread Paul Hendry

In a routed network I would expect all interfaces that directly connect on
the same lan segment to have addresses from the same network range. As yours
do not then it suggests you are bridging and, as Lonnie said, chances are
this is the route cause of your problems. Perhaps now is the time to switch
to a properly routed network? You don’t need to run a routing protocol like
RIP or OSPF if you are no ready for it yet and tbh there are some dodgy
implementations out there. Getting rid of any bridged interfaces and putting
in static routes and correct ip assignment should do the job.

Cheers,

P.

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Mark McElvy
Sent: 17 September 2006 19:55
To: WISPA General List
Subject: RE: [WISPA] Routing woes.

I also like the idea of moving to RIP or OSPF but have yet taken the
time to wrap my head around it to understand how to implement.

Mark McElvy
AccuBak Data Systems, Inc.
573.729.9200 - Office
573.729.9203 - Fax
573.247.9980 - Mobile
http://www.accubak.com/
http://www.accubak.net/
Nationwide Internet Access
Accurate backups for your critical data! 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Lonnie Nunweiler
Sent: Sunday, September 17, 2006 10:22 AM
To: WISPA General List
Subject: Re: [WISPA] Routing woes.

What is the Ethernet assignment on the edge router?  What is the
connection to the BR AP units?  Is it Ethernet or wireless?  I am
thinking it is Ethernet since the BR AP units seem to have their
radios in AP mode, but the BH designation on the one unit has me not
so sure of it.

My first comment is actually a question.  Why use bridging at all?
You have subnets assigned to all devices so routing would be a snap to
implement and you are more than half way there.  Bridging uses the IP
strictly for configuration.  It will figure out the connections based
on the ARP table, so in my mind you never really have routes in a
bridge design.  The two conflict.

For routing design just make sure to use subnets that are common for
each connected device.  That means that if you connect the edge unit
to the other units by Ethernet, they all share a unique subnet and
when you can ping the connected units you have the basis for a routed
backbone.

Once that is done and all backbone units are pingable on Ethernet I
would simply enable RIP and remove the bridge tags and you would be
solid for the rest of the LAN.

Just keep assigning new, unique subnets to all new devices and let RIP
take care of it.  All you will need is a default route on each new
device that points to the machine and IP it connects with.

By moving to routed and RIP you will find your current system is
simpler and easier and I'll bet it will have higher performance and it
will offer you more control and troubleshooting ability.

Lonnie

On 9/17/06, Mark McElvy <[EMAIL PROTECTED]> wrote:
>
>
>
>
> I am trying to add a route to my existing network and I just can't get
it to
> work...
>
> The network I can't get to work is to network 172.22.20.0/24, all
others
> work fine.
>
>
>
> Edge router StarOS
>
>
>
> 0.0.0.0/0   216.229.xxx.xxxether1
>Wan
>
> 172.22.255.0/29 172.22.1.3 ether2
>Route to BR LAN
>
> 172.22.11.0/24   172.22.1.3 ether2
> Route to BR AP1
>
> 172.22.12.0/24   172.22.1.3 ether2
> Route to BR AP2
>
> 172.22.13.0/24   172.22.1.3 ether2
> Route to BR AP3
>
> 172.22.22.0/24   172.22.1.9 ether2
> Route to Atheros test
>
> 172.22.23.0/24   172.22.1.9 ether2
> Route to Prism test
>
> 172.22.20.0/24   172.22.1.3 ether2
> Route to Lenox BH ( does not work )
>
>
>
> BR AP1 - StarOS, 2 wireless cards
>
> Wpci1  172.22.11.1AP
>
> Wpci2   172.22.1.3 BH
>
> Ether1   172.22.255.1
>
>
>
> 0.0.0.0/0   172.22.1.1 wpci2
>
> 172.22.12.0/24   172.22.255.2 ether1
>   Route to AP2
>
> 172.22.13.0/24   172.22.255.3 ether1
>   Route to AP3
>
> 172.22.20.0/24   172.22.255.3 ether1
>   Route to BH Lenox
>
>
>
> BR AP2 - Mikrotik, 1 wireless card
>
> Wpci1   172.22.12.1   AP
>
> Ether1   172.22.355.2
>
>
>
> 0.0.0.0/0   172.22.255.1 ether1
>
>
>
> BR AP3 - StarOS,  2 wireless cards
>
> Wpci1   172.22.13.1
>
> Wpci2   172.22.20.1
>
> Ether1   172.22.255.3
>
>
>
> 0.0.0.0/24  172.22.255.1 ether1
>
>
>
>
>
> Trace from machine on 172.22.1.0/24
>
> C:\Documents and Settings\Administrator>tracert 172.22.20.1
>
>
>
> Tracing route to 172.22.20.1 over a maximum of 30 hops
>
>
>
>   1<1 ms<1 ms<1 ms  172.22.1.1
>
>   2 1 ms 1

Re: [WISPA] Initial SR9 test results

2006-09-17 Thread Leon D. Zetekoff, NCE


Lonnie Nunweiler wrote:

Vertical and horizontal were tried.  The results are the same.
Thanks Lonnie...we're trying some Mikrotik with the 900 cards and not 
having much luck through the trees using a 900 120* sector H-pol


Leon


Lonnie

On 9/17/06, *Leon D. Zetekoff, NCE* < [EMAIL PROTECTED] 
> wrote:


Lonnie Nunweiler wrote:

http://forums.star-os.com/showthread.php?t=5838

I just posted our early rsults of the 900 MHz gear.  Needless to say
this is better than I was hoping for and this stuff has a FIRM place
in our tool chest.  Forget higher power on 2.4 GHz to get through
some
trees.  This is truly NON LOS.


Hi Lonnie...what polarization did you use?

Thanks leon

-- 
*Leon Zetekoff*

Proprietor  
*Work:* 484-335-9920
*Mobile:* 610-223-8642
*Fax:* 484-335-9921
*Email:* [EMAIL PROTECTED] 
*http://www.linkedin.com/in/leonzetekoff*
*BackWoods Wireless*
 505 B Main Street

Blandon, PA 19510
"Bringing Broadband Technology to Rural Areas"

See who we know in common
  Want a signature like
this? 


--
WISPA Wireless List: wireless@wispa.org 

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/







--
Lonnie Nunweiler
Valemount Networks Corporation
http://www.star-os.com/ 


--
*Leon Zetekoff*
Proprietor  
*Work:* 484-335-9920
*Mobile:* 610-223-8642
*Fax:* 484-335-9921
*Email:* [EMAIL PROTECTED] 
*http://www.linkedin.com/in/leonzetekoff*
*BackWoods Wireless*
 505 B Main Street
 
Blandon, PA 19510

"Bringing Broadband Technology to Rural Areas"

See who we know in common  	Want 
a signature like this? 


begin:vcard
fn:Leon Zetekoff
n:Zetekoff;Leon
org:BackWoods Wireless
adr;dom:;;505 B Main Street;Blandon;PA;19510
email;internet:[EMAIL PROTECTED]
title:Owner
tel;work:484-335-9920
tel;fax:484-335-9921
tel;home:610-916-0230
tel;cell:610-223-8642
x-mozilla-html:TRUE
url:http://www.backwoodswireless.net
version:2.1
end:vcard

-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

RE: [WISPA] Routing woes.....

2006-09-17 Thread Mark McElvy

I also like the idea of moving to RIP or OSPF but have yet taken the
time to wrap my head around it to understand how to implement.

Mark McElvy
AccuBak Data Systems, Inc.
573.729.9200 - Office
573.729.9203 - Fax
573.247.9980 - Mobile
http://www.accubak.com/
http://www.accubak.net/
Nationwide Internet Access
Accurate backups for your critical data! 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Lonnie Nunweiler
Sent: Sunday, September 17, 2006 10:22 AM
To: WISPA General List
Subject: Re: [WISPA] Routing woes.

What is the Ethernet assignment on the edge router?  What is the
connection to the BR AP units?  Is it Ethernet or wireless?  I am
thinking it is Ethernet since the BR AP units seem to have their
radios in AP mode, but the BH designation on the one unit has me not
so sure of it.

My first comment is actually a question.  Why use bridging at all?
You have subnets assigned to all devices so routing would be a snap to
implement and you are more than half way there.  Bridging uses the IP
strictly for configuration.  It will figure out the connections based
on the ARP table, so in my mind you never really have routes in a
bridge design.  The two conflict.

For routing design just make sure to use subnets that are common for
each connected device.  That means that if you connect the edge unit
to the other units by Ethernet, they all share a unique subnet and
when you can ping the connected units you have the basis for a routed
backbone.

Once that is done and all backbone units are pingable on Ethernet I
would simply enable RIP and remove the bridge tags and you would be
solid for the rest of the LAN.

Just keep assigning new, unique subnets to all new devices and let RIP
take care of it.  All you will need is a default route on each new
device that points to the machine and IP it connects with.

By moving to routed and RIP you will find your current system is
simpler and easier and I'll bet it will have higher performance and it
will offer you more control and troubleshooting ability.

Lonnie

On 9/17/06, Mark McElvy <[EMAIL PROTECTED]> wrote:
>
>
>
>
> I am trying to add a route to my existing network and I just can't get
it to
> work...
>
> The network I can't get to work is to network 172.22.20.0/24, all
others
> work fine.
>
>
>
> Edge router StarOS
>
>
>
> 0.0.0.0/0   216.229.xxx.xxxether1
>Wan
>
> 172.22.255.0/29 172.22.1.3 ether2
>Route to BR LAN
>
> 172.22.11.0/24   172.22.1.3 ether2
> Route to BR AP1
>
> 172.22.12.0/24   172.22.1.3 ether2
> Route to BR AP2
>
> 172.22.13.0/24   172.22.1.3 ether2
> Route to BR AP3
>
> 172.22.22.0/24   172.22.1.9 ether2
> Route to Atheros test
>
> 172.22.23.0/24   172.22.1.9 ether2
> Route to Prism test
>
> 172.22.20.0/24   172.22.1.3 ether2
> Route to Lenox BH ( does not work )
>
>
>
> BR AP1 - StarOS, 2 wireless cards
>
> Wpci1  172.22.11.1AP
>
> Wpci2   172.22.1.3 BH
>
> Ether1   172.22.255.1
>
>
>
> 0.0.0.0/0   172.22.1.1 wpci2
>
> 172.22.12.0/24   172.22.255.2 ether1
>   Route to AP2
>
> 172.22.13.0/24   172.22.255.3 ether1
>   Route to AP3
>
> 172.22.20.0/24   172.22.255.3 ether1
>   Route to BH Lenox
>
>
>
> BR AP2 - Mikrotik, 1 wireless card
>
> Wpci1   172.22.12.1   AP
>
> Ether1   172.22.355.2
>
>
>
> 0.0.0.0/0   172.22.255.1 ether1
>
>
>
> BR AP3 - StarOS,  2 wireless cards
>
> Wpci1   172.22.13.1
>
> Wpci2   172.22.20.1
>
> Ether1   172.22.255.3
>
>
>
> 0.0.0.0/24  172.22.255.1 ether1
>
>
>
>
>
> Trace from machine on 172.22.1.0/24
>
> C:\Documents and Settings\Administrator>tracert 172.22.20.1
>
>
>
> Tracing route to 172.22.20.1 over a maximum of 30 hops
>
>
>
>   1<1 ms<1 ms<1 ms  172.22.1.1
>
>   2 1 ms 1 ms<1 ms  172.22.1.3
>
>   3 1 ms 1 ms 1 ms  172.22.1.3
>
>   4 2 ms 1 ms 1 ms  172.22.1.1
>
>   5 2 ms 2 ms 2 ms  ^C
>
>
>
> Even though I have a route pointing it to 1.3, it starts with 1.1
unlike all
> the routes in the list.
>
>
>
> Mark
>
>
>  This electronic communication (including any attached document) may
contain
> privileged and/or confidential information. This communication is
intended
> only for the use of indicated e-mail addressees. If you are not an
intended
> recipient of this communication, please be advised that any
disclosure,
> dissemination, distribution, copying, or other use of this
communication or
> any attached document is prohibited. If you have received this
communication
> in error, please notify the sender immediatel

RE: [WISPA] Routing woes.....

2006-09-17 Thread Mark McElvy

It is a Tranzeo TR5-21
Every thing has been and is working fine except for the latest entry for
the 172.22.20.0/24 network

Mark McElvy
AccuBak Data Systems, Inc.
573.729.9200 - Office
573.729.9203 - Fax
573.247.9980 - Mobile
http://www.accubak.com/
http://www.accubak.net/
Nationwide Internet Access
Accurate backups for your critical data! 


-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Lonnie Nunweiler
Sent: Sunday, September 17, 2006 1:47 PM
To: WISPA General List
Subject: Re: [WISPA] Routing woes.

The bridge feeding the BRAPx units can be a problem unless it is a
true bridge, meaning it cannot be a pseudo bridge doing proxy arp or
mac cloning.   What type of unit is that bridge?

Lonnie

On 9/17/06, Mark McElvy <[EMAIL PROTECTED]> wrote:
> The edge router is in my office connected to WAN and 172.22.1.0/24
> There is a radio on the roof (bridge) feeding BR AP1 wireless (1.3)
> The second wpci is an AP (1.12)
> Ethernet connects BRAP1, BRAP2 and BRAP3 on 172.22.255.0/29
> BRAP2 is an AP (12.1)
> BRAP3 is an AP (13.1) and a BH to a new tower.
> The back haul link is 172.22.20.0/24
>
> Everything is statically routed except for the bridge radio feeding
the
> tower.
>
> Mark McElvy
> AccuBak Data Systems, Inc.
> 573.729.9200 - Office
> 573.729.9203 - Fax
> 573.247.9980 - Mobile
> http://www.accubak.com/
> http://www.accubak.net/
> Nationwide Internet Access
> Accurate backups for your critical data!
>
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
On
> Behalf Of Lonnie Nunweiler
> Sent: Sunday, September 17, 2006 10:22 AM
> To: WISPA General List
> Subject: Re: [WISPA] Routing woes.
>
> What is the Ethernet assignment on the edge router?  What is the
> connection to the BR AP units?  Is it Ethernet or wireless?  I am
> thinking it is Ethernet since the BR AP units seem to have their
> radios in AP mode, but the BH designation on the one unit has me not
> so sure of it.
>
> My first comment is actually a question.  Why use bridging at all?
> You have subnets assigned to all devices so routing would be a snap to
> implement and you are more than half way there.  Bridging uses the IP
> strictly for configuration.  It will figure out the connections based
> on the ARP table, so in my mind you never really have routes in a
> bridge design.  The two conflict.
>
> For routing design just make sure to use subnets that are common for
> each connected device.  That means that if you connect the edge unit
> to the other units by Ethernet, they all share a unique subnet and
> when you can ping the connected units you have the basis for a routed
> backbone.
>
> Once that is done and all backbone units are pingable on Ethernet I
> would simply enable RIP and remove the bridge tags and you would be
> solid for the rest of the LAN.
>
> Just keep assigning new, unique subnets to all new devices and let RIP
> take care of it.  All you will need is a default route on each new
> device that points to the machine and IP it connects with.
>
> By moving to routed and RIP you will find your current system is
> simpler and easier and I'll bet it will have higher performance and it
> will offer you more control and troubleshooting ability.
>
> Lonnie
>
> On 9/17/06, Mark McElvy <[EMAIL PROTECTED]> wrote:
> >
> >
> >
> >
> > I am trying to add a route to my existing network and I just can't
get
> it to
> > work...
> >
> > The network I can't get to work is to network 172.22.20.0/24, all
> others
> > work fine.
> >
> >
> >
> > Edge router StarOS
> >
> >
> >
> > 0.0.0.0/0   216.229.xxx.xxxether1
> >Wan
> >
> > 172.22.255.0/29 172.22.1.3 ether2
> >Route to BR LAN
> >
> > 172.22.11.0/24   172.22.1.3 ether2
> > Route to BR AP1
> >
> > 172.22.12.0/24   172.22.1.3 ether2
> > Route to BR AP2
> >
> > 172.22.13.0/24   172.22.1.3 ether2
> > Route to BR AP3
> >
> > 172.22.22.0/24   172.22.1.9 ether2
> > Route to Atheros test
> >
> > 172.22.23.0/24   172.22.1.9 ether2
> > Route to Prism test
> >
> > 172.22.20.0/24   172.22.1.3 ether2
> > Route to Lenox BH ( does not work )
> >
> >
> >
> > BR AP1 - StarOS, 2 wireless cards
> >
> > Wpci1  172.22.11.1AP
> >
> > Wpci2   172.22.1.3 BH
> >
> > Ether1   172.22.255.1
> >
> >
> >
> > 0.0.0.0/0   172.22.1.1 wpci2
> >
> > 172.22.12.0/24   172.22.255.2 ether1
> >   Route to AP2
> >
> > 172.22.13.0/24   172.22.255.3 ether1
> >   Route to AP3
> >
> > 172.22.20.0/24   172.22.255.3 ether1
> >   Route to BH Lenox
> >
> >
> >
> > BR AP2 - Mikrotik, 1 wireless card
> >
> > Wpci1   172.22.12.1   AP
> >

Re: [WISPA] Routing woes.....

2006-09-17 Thread Lonnie Nunweiler

The bridge feeding the BRAPx units can be a problem unless it is a
true bridge, meaning it cannot be a pseudo bridge doing proxy arp or
mac cloning.   What type of unit is that bridge?

Lonnie

On 9/17/06, Mark McElvy <[EMAIL PROTECTED]> wrote:

The edge router is in my office connected to WAN and 172.22.1.0/24
There is a radio on the roof (bridge) feeding BR AP1 wireless (1.3)
The second wpci is an AP (1.12)
Ethernet connects BRAP1, BRAP2 and BRAP3 on 172.22.255.0/29
BRAP2 is an AP (12.1)
BRAP3 is an AP (13.1) and a BH to a new tower.
The back haul link is 172.22.20.0/24

Everything is statically routed except for the bridge radio feeding the
tower.

Mark McElvy
AccuBak Data Systems, Inc.
573.729.9200 - Office
573.729.9203 - Fax
573.247.9980 - Mobile
http://www.accubak.com/
http://www.accubak.net/
Nationwide Internet Access
Accurate backups for your critical data!

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Lonnie Nunweiler
Sent: Sunday, September 17, 2006 10:22 AM
To: WISPA General List
Subject: Re: [WISPA] Routing woes.

What is the Ethernet assignment on the edge router?  What is the
connection to the BR AP units?  Is it Ethernet or wireless?  I am
thinking it is Ethernet since the BR AP units seem to have their
radios in AP mode, but the BH designation on the one unit has me not
so sure of it.

My first comment is actually a question.  Why use bridging at all?
You have subnets assigned to all devices so routing would be a snap to
implement and you are more than half way there.  Bridging uses the IP
strictly for configuration.  It will figure out the connections based
on the ARP table, so in my mind you never really have routes in a
bridge design.  The two conflict.

For routing design just make sure to use subnets that are common for
each connected device.  That means that if you connect the edge unit
to the other units by Ethernet, they all share a unique subnet and
when you can ping the connected units you have the basis for a routed
backbone.

Once that is done and all backbone units are pingable on Ethernet I
would simply enable RIP and remove the bridge tags and you would be
solid for the rest of the LAN.

Just keep assigning new, unique subnets to all new devices and let RIP
take care of it.  All you will need is a default route on each new
device that points to the machine and IP it connects with.

By moving to routed and RIP you will find your current system is
simpler and easier and I'll bet it will have higher performance and it
will offer you more control and troubleshooting ability.

Lonnie

On 9/17/06, Mark McElvy <[EMAIL PROTECTED]> wrote:
>
>
>
>
> I am trying to add a route to my existing network and I just can't get
it to
> work...
>
> The network I can't get to work is to network 172.22.20.0/24, all
others
> work fine.
>
>
>
> Edge router StarOS
>
>
>
> 0.0.0.0/0   216.229.xxx.xxxether1
>Wan
>
> 172.22.255.0/29 172.22.1.3 ether2
>Route to BR LAN
>
> 172.22.11.0/24   172.22.1.3 ether2
> Route to BR AP1
>
> 172.22.12.0/24   172.22.1.3 ether2
> Route to BR AP2
>
> 172.22.13.0/24   172.22.1.3 ether2
> Route to BR AP3
>
> 172.22.22.0/24   172.22.1.9 ether2
> Route to Atheros test
>
> 172.22.23.0/24   172.22.1.9 ether2
> Route to Prism test
>
> 172.22.20.0/24   172.22.1.3 ether2
> Route to Lenox BH ( does not work )
>
>
>
> BR AP1 - StarOS, 2 wireless cards
>
> Wpci1  172.22.11.1AP
>
> Wpci2   172.22.1.3 BH
>
> Ether1   172.22.255.1
>
>
>
> 0.0.0.0/0   172.22.1.1 wpci2
>
> 172.22.12.0/24   172.22.255.2 ether1
>   Route to AP2
>
> 172.22.13.0/24   172.22.255.3 ether1
>   Route to AP3
>
> 172.22.20.0/24   172.22.255.3 ether1
>   Route to BH Lenox
>
>
>
> BR AP2 - Mikrotik, 1 wireless card
>
> Wpci1   172.22.12.1   AP
>
> Ether1   172.22.355.2
>
>
>
> 0.0.0.0/0   172.22.255.1 ether1
>
>
>
> BR AP3 - StarOS,  2 wireless cards
>
> Wpci1   172.22.13.1
>
> Wpci2   172.22.20.1
>
> Ether1   172.22.255.3
>
>
>
> 0.0.0.0/24  172.22.255.1 ether1
>
>
>
>
>
> Trace from machine on 172.22.1.0/24
>
> C:\Documents and Settings\Administrator>tracert 172.22.20.1
>
>
>
> Tracing route to 172.22.20.1 over a maximum of 30 hops
>
>
>
>   1<1 ms<1 ms<1 ms  172.22.1.1
>
>   2 1 ms 1 ms<1 ms  172.22.1.3
>
>   3 1 ms 1 ms 1 ms  172.22.1.3
>
>   4 2 ms 1 ms 1 ms  172.22.1.1
>
>   5 2 ms 2 ms 2 ms  ^C
>
>
>
> Even though I have a route pointing it to 1.3, it starts with 1.1
unlike all
> the routes in the list.
>
>

RE: [WISPA] Routing woes.....

2006-09-17 Thread Mark McElvy









BR designates one of my towers which is
fed wirelessly via BRAP1, Ethernet interconnects the 3 devices at the tower.

 

Yes I meant 255.2, 355.2 was a typo in the
email only

 

 



Mark McElvy
AccuBak Data
Systems, Inc.
573.729.9200 - Office
573.729.9203 - Fax
573.247.9980 - Mobile
http://www.accubak.com/
http://www.accubak.net/
Nationwide
Internet Access
Accurate backups for your critical data! 











From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Paul Hendry
Sent: Sunday, September 17, 2006
9:11 AM
To: 'WISPA General List'
Subject: RE: [WISPA] Routing
woes.



 

As your Edge router has 172.22.1.1 on it’s
Ethernet port then shouldn’t BR AP1 also have it’s 172.22.1.3 address on it’s
Ethernet port not wireless? If I was BR AP1 then I would be confused too ;)

 

And I’m pretty sure that the Ethernet
address of BR AP2 isn’t valid too. Did you mean 172.22.255.2 not 172.22.355.2?

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark
 McElvy
Sent: 17 September 2006 14:28
To: WISPA
 General List
Subject: [WISPA] Routing woes.



 

I am trying to add a route to my existing network and I just
can’t get it to work…

The network I can’t get to work is to network
172.22.20.0/24, all others work fine.

 

Edge router StarOS

 

0.0.0.0/0  
   
216.229.xxx.xxx   
ether1  
Wan

172.22.255.0/29
   
172.22.1.3
ether2  
Route to BR LAN

172.22.11.0/24  
172.22.1.3
ether2  
Route to BR AP1

172.22.12.0/24  
172.22.1.3
ether2  
Route to BR AP2

172.22.13.0/24  
172.22.1.3
ether2  
Route to BR AP3

172.22.22.0/24  
172.22.1.9
ether2  
Route to Atheros test

172.22.23.0/24  
172.22.1.9
ether2  
Route to Prism test

172.22.20.0/24  
172.22.1.3
ether2  
Route to Lenox BH ( does not work )

 

BR AP1 – StarOS, 2 wireless cards

Wpci1 
172.22.11.1    AP

Wpci2  
172.22.1.3 BH

Ether1   172.22.255.1

 

0.0.0.0/0  
   
172.22.1.1
wpci2

172.22.12.0/24  
172.22.255.2
ether1  
Route to AP2

172.22.13.0/24  
172.22.255.3
ether1  
Route to AP3

172.22.20.0/24  
172.22.255.3
ether1  
Route to BH Lenox

 

BR AP2 – Mikrotik, 1 wireless card

Wpci1  
172.22.12.1   AP

Ether1   172.22.355.2 

 

0.0.0.0/0  
172.22.255.1
ether1

 

BR AP3 – StarOS,  2 wireless cards

Wpci1   172.22.13.1

Wpci2   172.22.20.1

Ether1   172.22.255.3

 

0.0.0.0/24 
172.22.255.1
ether1

 

 

Trace from machine on 172.22.1.0/24

C:\Documents and Settings\Administrator>tracert
172.22.20.1

 

Tracing route to 172.22.20.1 over a maximum of 30 hops

 

  1    <1 ms    <1 ms   
<1 ms  172.22.1.1

  2 1
ms 1 ms    <1 ms  172.22.1.3

  3 1
ms 1 ms 1 ms  172.22.1.3

  4 2
ms 1 ms 1 ms  172.22.1.1

  5 2
ms 2 ms 2 ms  ^C

 

Even though I have a route pointing it to 1.3, it starts
with 1.1 unlike all the routes in the list.

 

Mark




This electronic communication (including any attached document) may contain
privileged and/or confidential information. This communication is intended only
for the use of indicated e-mail addressees. If you are not an intended
recipient of this communication, please be advised that any disclosure,
dissemination, distribution, copying, or other use of this communication or any
attached document is prohibited. If you have received this communication in
error, please notify the sender immediately by reply e-mail and promptly
destroy all electronic and printed copies of this communication and any
attached document.
Unauthorized interception of this e-mail is a violation of federal criminal
law.






This electronic communication (including any attached document) may contain privileged and/or confidential information.  This communication is intended only for the use of indicated e-mail addressees.  If you are not an intended recipient of this communication, please be advised that any disclosure, dissemination, distribution, copying, or other use of this communication or any attached document is prohibited.  If you have received this communication in error, please notify the sender immediately by reply e-mail and promptly destroy all electronic and printed copies of this communication and any attached document.
Unauthorized interception of this e-mail is a violation of federal criminal law.




--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.12.4/449 - Release Date: 15/09/2006
 

  

--
No vi

RE: [WISPA] Routing woes.....

2006-09-17 Thread Mark McElvy

The edge router is in my office connected to WAN and 172.22.1.0/24
There is a radio on the roof (bridge) feeding BR AP1 wireless (1.3)
The second wpci is an AP (1.12)
Ethernet connects BRAP1, BRAP2 and BRAP3 on 172.22.255.0/29
BRAP2 is an AP (12.1)
BRAP3 is an AP (13.1) and a BH to a new tower. 
The back haul link is 172.22.20.0/24

Everything is statically routed except for the bridge radio feeding the
tower.

Mark McElvy
AccuBak Data Systems, Inc.
573.729.9200 - Office
573.729.9203 - Fax
573.247.9980 - Mobile
http://www.accubak.com/
http://www.accubak.net/
Nationwide Internet Access
Accurate backups for your critical data! 

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Lonnie Nunweiler
Sent: Sunday, September 17, 2006 10:22 AM
To: WISPA General List
Subject: Re: [WISPA] Routing woes.

What is the Ethernet assignment on the edge router?  What is the
connection to the BR AP units?  Is it Ethernet or wireless?  I am
thinking it is Ethernet since the BR AP units seem to have their
radios in AP mode, but the BH designation on the one unit has me not
so sure of it.

My first comment is actually a question.  Why use bridging at all?
You have subnets assigned to all devices so routing would be a snap to
implement and you are more than half way there.  Bridging uses the IP
strictly for configuration.  It will figure out the connections based
on the ARP table, so in my mind you never really have routes in a
bridge design.  The two conflict.

For routing design just make sure to use subnets that are common for
each connected device.  That means that if you connect the edge unit
to the other units by Ethernet, they all share a unique subnet and
when you can ping the connected units you have the basis for a routed
backbone.

Once that is done and all backbone units are pingable on Ethernet I
would simply enable RIP and remove the bridge tags and you would be
solid for the rest of the LAN.

Just keep assigning new, unique subnets to all new devices and let RIP
take care of it.  All you will need is a default route on each new
device that points to the machine and IP it connects with.

By moving to routed and RIP you will find your current system is
simpler and easier and I'll bet it will have higher performance and it
will offer you more control and troubleshooting ability.

Lonnie

On 9/17/06, Mark McElvy <[EMAIL PROTECTED]> wrote:
>
>
>
>
> I am trying to add a route to my existing network and I just can't get
it to
> work...
>
> The network I can't get to work is to network 172.22.20.0/24, all
others
> work fine.
>
>
>
> Edge router StarOS
>
>
>
> 0.0.0.0/0   216.229.xxx.xxxether1
>Wan
>
> 172.22.255.0/29 172.22.1.3 ether2
>Route to BR LAN
>
> 172.22.11.0/24   172.22.1.3 ether2
> Route to BR AP1
>
> 172.22.12.0/24   172.22.1.3 ether2
> Route to BR AP2
>
> 172.22.13.0/24   172.22.1.3 ether2
> Route to BR AP3
>
> 172.22.22.0/24   172.22.1.9 ether2
> Route to Atheros test
>
> 172.22.23.0/24   172.22.1.9 ether2
> Route to Prism test
>
> 172.22.20.0/24   172.22.1.3 ether2
> Route to Lenox BH ( does not work )
>
>
>
> BR AP1 - StarOS, 2 wireless cards
>
> Wpci1  172.22.11.1AP
>
> Wpci2   172.22.1.3 BH
>
> Ether1   172.22.255.1
>
>
>
> 0.0.0.0/0   172.22.1.1 wpci2
>
> 172.22.12.0/24   172.22.255.2 ether1
>   Route to AP2
>
> 172.22.13.0/24   172.22.255.3 ether1
>   Route to AP3
>
> 172.22.20.0/24   172.22.255.3 ether1
>   Route to BH Lenox
>
>
>
> BR AP2 - Mikrotik, 1 wireless card
>
> Wpci1   172.22.12.1   AP
>
> Ether1   172.22.355.2
>
>
>
> 0.0.0.0/0   172.22.255.1 ether1
>
>
>
> BR AP3 - StarOS,  2 wireless cards
>
> Wpci1   172.22.13.1
>
> Wpci2   172.22.20.1
>
> Ether1   172.22.255.3
>
>
>
> 0.0.0.0/24  172.22.255.1 ether1
>
>
>
>
>
> Trace from machine on 172.22.1.0/24
>
> C:\Documents and Settings\Administrator>tracert 172.22.20.1
>
>
>
> Tracing route to 172.22.20.1 over a maximum of 30 hops
>
>
>
>   1<1 ms<1 ms<1 ms  172.22.1.1
>
>   2 1 ms 1 ms<1 ms  172.22.1.3
>
>   3 1 ms 1 ms 1 ms  172.22.1.3
>
>   4 2 ms 1 ms 1 ms  172.22.1.1
>
>   5 2 ms 2 ms 2 ms  ^C
>
>
>
> Even though I have a route pointing it to 1.3, it starts with 1.1
unlike all
> the routes in the list.
>
>
>
> Mark
>
>
>  This electronic communication (including any attached document) may
contain
> privileged and/or confidential information. This communication is
intended
> only for the use of indicated e-mail addressees. If you are not an
intend

Re: [WISPA] Initial SR9 test results

2006-09-17 Thread Lonnie Nunweiler

Vertical and horizontal were tried.  The results are the same.LonnieOn 9/17/06, Leon D. Zetekoff, NCE <
[EMAIL PROTECTED]> wrote:


  


Lonnie Nunweiler wrote:

http://forums.star-os.com/showthread.php?t=5838
  
  
I just posted our early rsults of the 900 MHz gear.  Needless to say
  
this is better than I was hoping for and this stuff has a FIRM place
  
in our tool chest.  Forget higher power on 2.4 GHz to get through some
  
trees.  This is truly NON LOS.
  
  

Hi Lonnie...what polarization did you use?

Thanks leon

-- 


  

   Leon Zetekoff
  Proprietor 
  


  
  


  
 Work:
484-335-9920
Mobile:
610-223-8642
Fax: 484-335-9921

 Email: 
[EMAIL PROTECTED]
 
http://www.linkedin.com/in/leonzetekoff

 BackWoods Wireless
 
505 B Main Street
 Blandon, PA 19510 
"Bringing
Broadband Technology to Rural Areas" 
  

  
  


  See who we
know in common
  Want a signature like
this? 

  





--WISPA Wireless List: wireless@wispa.orgSubscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wirelessArchives: http://lists.wispa.org/pipermail/wireless/
-- Lonnie NunweilerValemount Networks Corporationhttp://www.star-os.com/
-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Re: [WISPA] Initial SR9 test results

2006-09-17 Thread Leon D. Zetekoff, NCE





Lonnie Nunweiler wrote:
http://forums.star-os.com/showthread.php?t=5838
  
  
I just posted our early rsults of the 900 MHz gear.  Needless to say
  
this is better than I was hoping for and this stuff has a FIRM place
  
in our tool chest.  Forget higher power on 2.4 GHz to get through some
  
trees.  This is truly NON LOS.
  
  

Hi Lonnie...what polarization did you use?

Thanks leon

-- 

  

   Leon Zetekoff
  Proprietor 
  


  
  

  
 Work:
484-335-9920
Mobile:
610-223-8642
Fax: 484-335-9921

 Email: [EMAIL PROTECTED]
 http://www.linkedin.com/in/leonzetekoff

 BackWoods Wireless
 505 B Main Street
 Blandon, PA 19510 
"Bringing
Broadband Technology to Rural Areas" 
  

  
  


  See who we
know in common
  Want a signature like
this? 

  




begin:vcard
fn:Leon Zetekoff
n:Zetekoff;Leon
org:BackWoods Wireless
adr;dom:;;505 B Main Street;Blandon;PA;19510
email;internet:[EMAIL PROTECTED]
title:Owner
tel;work:484-335-9920
tel;fax:484-335-9921
tel;home:610-916-0230
tel;cell:610-223-8642
x-mozilla-html:TRUE
url:http://www.backwoodswireless.net
version:2.1
end:vcard

-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

[WISPA] Initial SR9 test results

2006-09-17 Thread Lonnie Nunweiler


http://forums.star-os.com/showthread.php?t=5838

I just posted our early rsults of the 900 MHz gear.  Needless to say
this is better than I was hoping for and this stuff has a FIRM place
in our tool chest.  Forget higher power on 2.4 GHz to get through some
trees.  This is truly NON LOS.

--
Lonnie Nunweiler
Valemount Networks Corporation
http://www.star-os.com/
--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Re: [WISPA] Routing woes.....

2006-09-17 Thread Lonnie Nunweiler


What is the Ethernet assignment on the edge router?  What is the
connection to the BR AP units?  Is it Ethernet or wireless?  I am
thinking it is Ethernet since the BR AP units seem to have their
radios in AP mode, but the BH designation on the one unit has me not
so sure of it.

My first comment is actually a question.  Why use bridging at all?
You have subnets assigned to all devices so routing would be a snap to
implement and you are more than half way there.  Bridging uses the IP
strictly for configuration.  It will figure out the connections based
on the ARP table, so in my mind you never really have routes in a
bridge design.  The two conflict.

For routing design just make sure to use subnets that are common for
each connected device.  That means that if you connect the edge unit
to the other units by Ethernet, they all share a unique subnet and
when you can ping the connected units you have the basis for a routed
backbone.

Once that is done and all backbone units are pingable on Ethernet I
would simply enable RIP and remove the bridge tags and you would be
solid for the rest of the LAN.

Just keep assigning new, unique subnets to all new devices and let RIP
take care of it.  All you will need is a default route on each new
device that points to the machine and IP it connects with.

By moving to routed and RIP you will find your current system is
simpler and easier and I'll bet it will have higher performance and it
will offer you more control and troubleshooting ability.

Lonnie

On 9/17/06, Mark McElvy <[EMAIL PROTECTED]> wrote:





I am trying to add a route to my existing network and I just can't get it to
work…

The network I can't get to work is to network 172.22.20.0/24, all others
work fine.



Edge router StarOS



0.0.0.0/0   216.229.xxx.xxxether1
   Wan

172.22.255.0/29 172.22.1.3 ether2
   Route to BR LAN

172.22.11.0/24   172.22.1.3 ether2
Route to BR AP1

172.22.12.0/24   172.22.1.3 ether2
Route to BR AP2

172.22.13.0/24   172.22.1.3 ether2
Route to BR AP3

172.22.22.0/24   172.22.1.9 ether2
Route to Atheros test

172.22.23.0/24   172.22.1.9 ether2
Route to Prism test

172.22.20.0/24   172.22.1.3 ether2
Route to Lenox BH ( does not work )



BR AP1 – StarOS, 2 wireless cards

Wpci1  172.22.11.1AP

Wpci2   172.22.1.3 BH

Ether1   172.22.255.1



0.0.0.0/0   172.22.1.1 wpci2

172.22.12.0/24   172.22.255.2 ether1
  Route to AP2

172.22.13.0/24   172.22.255.3 ether1
  Route to AP3

172.22.20.0/24   172.22.255.3 ether1
  Route to BH Lenox



BR AP2 – Mikrotik, 1 wireless card

Wpci1   172.22.12.1   AP

Ether1   172.22.355.2



0.0.0.0/0   172.22.255.1 ether1



BR AP3 – StarOS,  2 wireless cards

Wpci1   172.22.13.1

Wpci2   172.22.20.1

Ether1   172.22.255.3



0.0.0.0/24  172.22.255.1 ether1





Trace from machine on 172.22.1.0/24

C:\Documents and Settings\Administrator>tracert 172.22.20.1



Tracing route to 172.22.20.1 over a maximum of 30 hops



  1<1 ms<1 ms<1 ms  172.22.1.1

  2 1 ms 1 ms<1 ms  172.22.1.3

  3 1 ms 1 ms 1 ms  172.22.1.3

  4 2 ms 1 ms 1 ms  172.22.1.1

  5 2 ms 2 ms 2 ms  ^C



Even though I have a route pointing it to 1.3, it starts with 1.1 unlike all
the routes in the list.



Mark


 This electronic communication (including any attached document) may contain
privileged and/or confidential information. This communication is intended
only for the use of indicated e-mail addressees. If you are not an intended
recipient of this communication, please be advised that any disclosure,
dissemination, distribution, copying, or other use of this communication or
any attached document is prohibited. If you have received this communication
in error, please notify the sender immediately by reply e-mail and promptly
destroy all electronic and printed copies of this communication and any
attached document.
 Unauthorized interception of this e-mail is a violation of federal criminal
law.
--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/






--
Lonnie Nunweiler
Valemount Networks Corporation
http://www.star-os.com/
--
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

RE: [WISPA] Routing woes.....

2006-09-17 Thread Paul Hendry









As your Edge router has 172.22.1.1 on it’s
Ethernet port then shouldn’t BR AP1 also have it’s 172.22.1.3 address on it’s Ethernet
port not wireless? If I was BR AP1 then I would be confused too ;)

 

And I’m pretty sure that the Ethernet address
of BR AP2 isn’t valid too. Did you mean 172.22.255.2 not 172.22.355.2?

 









From:
[EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark McElvy
Sent: 17 September 2006 14:28
To: WISPA
 General List
Subject: [WISPA] Routing woes.



 

I am trying to add a route to my existing network and I just
can’t get it to work…

The network I can’t get to work is to network
172.22.20.0/24, all others work fine.

 

Edge router StarOS

 

0.0.0.0/0  
   
216.229.xxx.xxx   
ether1  
Wan

172.22.255.0/29
   
172.22.1.3
ether2  
Route to BR LAN

172.22.11.0/24  
172.22.1.3
ether2  
Route to BR AP1

172.22.12.0/24  
172.22.1.3
ether2  
Route to BR AP2

172.22.13.0/24  
172.22.1.3
ether2  
Route to BR AP3

172.22.22.0/24  
172.22.1.9
ether2  
Route to Atheros test

172.22.23.0/24  
172.22.1.9
ether2  
Route to Prism test

172.22.20.0/24  
172.22.1.3
ether2  
Route to Lenox BH ( does not work )

 

BR AP1 – StarOS, 2 wireless cards

Wpci1 
172.22.11.1    AP

Wpci2  
172.22.1.3 BH

Ether1   172.22.255.1

 

0.0.0.0/0  
   
172.22.1.1
wpci2

172.22.12.0/24  
172.22.255.2
ether1  
Route to AP2

172.22.13.0/24  
172.22.255.3
ether1  
Route to AP3

172.22.20.0/24  
172.22.255.3
ether1  
Route to BH Lenox

 

BR AP2 – Mikrotik, 1 wireless card

Wpci1  
172.22.12.1   AP

Ether1   172.22.355.2 

 

0.0.0.0/0  
172.22.255.1
ether1

 

BR AP3 – StarOS,  2 wireless cards

Wpci1   172.22.13.1

Wpci2   172.22.20.1

Ether1   172.22.255.3

 

0.0.0.0/24 
172.22.255.1
ether1

 

 

Trace from machine on 172.22.1.0/24

C:\Documents and Settings\Administrator>tracert
172.22.20.1

 

Tracing route to 172.22.20.1 over a maximum of 30 hops

 

  1    <1 ms    <1
ms    <1 ms  172.22.1.1

  2 1
ms 1 ms    <1 ms  172.22.1.3

  3 1
ms 1 ms 1 ms  172.22.1.3

  4 2
ms 1 ms 1 ms  172.22.1.1

  5 2
ms 2 ms 2 ms  ^C

 

Even though I have a route pointing it to 1.3, it starts
with 1.1 unlike all the routes in the list.

 

Mark




This electronic communication (including any attached document) may contain
privileged and/or confidential information. This communication is intended only
for the use of indicated e-mail addressees. If you are not an intended
recipient of this communication, please be advised that any disclosure,
dissemination, distribution, copying, or other use of this communication or any
attached document is prohibited. If you have received this communication in
error, please notify the sender immediately by reply e-mail and promptly
destroy all electronic and printed copies of this communication and any
attached document.
Unauthorized interception of this e-mail is a violation of federal criminal
law.








--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.12.4/449 - Release Date: 15/09/2006
 

  

--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.405 / Virus Database: 268.12.4/449 - Release Date: 15/09/2006
 
-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

[WISPA] Routing woes.....

2006-09-17 Thread Mark McElvy









I am trying to add a route to my existing network and I just
can’t get it to work…

The network I can’t get to work is to network
172.22.20.0/24, all others work fine.

 

Edge router StarOS

 

0.0.0.0/0       216.229.xxx.xxx    ether1   Wan

172.22.255.0/29     172.22.1.3 ether2   Route
to BR LAN

172.22.11.0/24   172.22.1.3 ether2   Route
to BR AP1

172.22.12.0/24   172.22.1.3 ether2   Route
to BR AP2

172.22.13.0/24   172.22.1.3 ether2   Route
to BR AP3

172.22.22.0/24   172.22.1.9 ether2   Route
to Atheros test

172.22.23.0/24   172.22.1.9 ether2   Route
to Prism test

172.22.20.0/24   172.22.1.3 ether2   Route
to Lenox BH ( does not work )

 

BR AP1 – StarOS, 2 wireless cards

Wpci1  172.22.11.1    AP

Wpci2   172.22.1.3 BH

Ether1   172.22.255.1

 

0.0.0.0/0       172.22.1.1 wpci2

172.22.12.0/24   172.22.255.2 ether1   Route
to AP2

172.22.13.0/24   172.22.255.3 ether1   Route
to AP3

172.22.20.0/24   172.22.255.3 ether1   Route
to BH Lenox

 

BR AP2 – Mikrotik, 1 wireless card

Wpci1   172.22.12.1   AP

Ether1   172.22.355.2 

 

0.0.0.0/0   172.22.255.1 ether1

 

BR AP3 – StarOS,  2 wireless cards

Wpci1   172.22.13.1

Wpci2   172.22.20.1

Ether1   172.22.255.3

 

0.0.0.0/24  172.22.255.1 ether1

 

 

Trace from machine on 172.22.1.0/24

C:\Documents and Settings\Administrator>tracert
172.22.20.1

 

Tracing route to 172.22.20.1 over a maximum of 30 hops

 

  1    <1 ms    <1
ms    <1 ms  172.22.1.1

  2 1
ms 1 ms    <1 ms  172.22.1.3

  3 1
ms 1 ms 1 ms  172.22.1.3

  4 2
ms 1 ms 1 ms  172.22.1.1

  5 2
ms 2 ms 2 ms  ^C

 

Even though I have a route pointing it to 1.3, it starts
with 1.1 unlike all the routes in the list.

 

Mark






This electronic communication (including any attached document) may contain privileged and/or confidential information.  This communication is intended only for the use of indicated e-mail addressees.  If you are not an intended recipient of this communication, please be advised that any disclosure, dissemination, distribution, copying, or other use of this communication or any attached document is prohibited.  If you have received this communication in error, please notify the sender immediately by reply e-mail and promptly destroy all electronic and printed copies of this communication and any attached document.
Unauthorized interception of this e-mail is a violation of federal criminal law.


-- 
WISPA Wireless List: wireless@wispa.org

Subscribe/Unsubscribe:
http://lists.wispa.org/mailman/listinfo/wireless

Archives: http://lists.wispa.org/pipermail/wireless/

Re: [WISPA] I need a climber / tower maintainer...

Re: [WISPA] Initial SR9 test results

Re: [WISPA] Initial SR9 test results

Re: [WISPA] Initial SR9 test results

Re: [WISPA] Initial SR9 test results

Re: [WISPA] Initial SR9 test results

Re: [WISPA] Initial SR9 test results

RE: [WISPA] Routing woes.....

Re: [WISPA] Initial SR9 test results

RE: [WISPA] Routing woes.....

RE: [WISPA] Routing woes.....

Re: [WISPA] Routing woes.....

RE: [WISPA] Routing woes.....

RE: [WISPA] Routing woes.....

Re: [WISPA] Initial SR9 test results

Re: [WISPA] Initial SR9 test results

[WISPA] Initial SR9 test results

Re: [WISPA] Routing woes.....

RE: [WISPA] Routing woes.....

[WISPA] Routing woes.....

20 matches

Site Navigation

Mail list logo

Footer information