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\Administratortracert 172.22.20.1 Tracing route to 172.22.20.1 over a maximum of 30 hops 11 ms1 ms1 ms 172.22.1.1 2 1 ms 1 ms1 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.....
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\Administratortracert 172.22.20.1 Tracing route to 172.22.20.1 over a maximum of 30 hops 11 ms1 ms1 ms 172.22.1.1 2 1 ms 1 ms1 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
RE: [WISPA] Routing woes.....
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 its Ethernet port then shouldnt BR AP1 also have its 172.22.1.3 address on its Ethernet port not wireless? If I was BR AP1 then I would be confused too ;) And Im pretty sure that the Ethernet address of BR AP2 isnt 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 cant get it to work The network I cant 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\Administratortracert 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 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/
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 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\Administratortracert 172.22.20.1 Tracing route to 172.22.20.1 over a maximum of 30 hops 11 ms1 ms1 ms 172.22.1.1 2 1 ms 1 ms1 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
RE: [WISPA] Routing woes.....
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 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
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\Administratortracert 172.22.20.1 Tracing route to 172.22.20.1 over a maximum of 30 hops 11 ms1 ms1 ms 172.22.1.1 2 1 ms 1 ms1 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
RE: [WISPA] Routing woes.....
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\Administratortracert 172.22.20.1 Tracing route to 172.22.20.1 over a maximum of 30 hops 11 ms1 ms1 ms 172.22.1.1 2 1 ms 1 ms1 ms 172.22.1.3 3 1 ms 1 ms 1 ms 172.22.1.3 4 2 ms 1 ms 1 ms
