From: "George J. Jahchan, Eng." <LARTC@Compucenter.org>
To: lartc@vger.kernel.org
Subject: RE: [LARTC] Routing problem
Date: Fri, 22 Nov 2002 00:32:40 +0000 [thread overview]
Message-ID: <marc-lartc-103792641804687@msgid-missing> (raw)
In-Reply-To: <marc-lartc-101530055025659@msgid-missing>
Mauro,
Unless both Aironets have routes to each other (either default or static) they cannot communicate, and AFAIK, the Aironets are layer-2 devices with no routing capabilities. Wireless hosts behind AP1 should be able to communicate with wireless hosts behind AP2 though. Just make sure hosts at both ends have appropriate routes to each other.
-----Original Message-----
From: lartc-admin@mailman.ds9a.nl [mailto:lartc-admin@mailman.ds9a.nl] On Behalf Of Mauro Cerboni
Sent: Wednesday, November 20, 2002 7:32 pm
To: lartc@mailman.ds9a.nl
Subject: [LARTC] Routing problem
Hi everybody,
I have 3 routers (Linux boxes with Red Hat 8.0 server), with iproute2 and ip_forward activated; they are linked together in this way:
AP1------Router1---------Router2----------Router3---------AP2
AP1 and AP2 are WLAN 802.11b Cisco Aironet 350 access points.
I can't ping AP2 from Router1 and Router2 and AP1 from Router3 and Router2.
Changing one of the AP with a laptop connected to Router (1 or 3) results in no effects.
The routing tables seem correct.
Router1 and Router3 can ping each other, so Router2 seems to make right routing.
The dotted lines above are 4 different subnets.
Any suggestion would be of great help!
Jhonatan
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://lartc.org/
next prev parent reply other threads:[~2002-11-22 0:32 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-05 3:55 [LARTC] routing problem suresh
2002-03-05 17:28 ` Ard van Breemen
2002-03-06 6:44 ` suresh
2002-11-20 17:31 ` [LARTC] Routing problem Mauro Cerboni
2002-11-22 0:03 ` Jose Luis Domingo Lopez
2002-11-22 0:32 ` George J. Jahchan, Eng. [this message]
2002-12-17 16:53 ` [LARTC] ROUTING Problem Andre Lorenz
2003-09-05 16:12 ` [LARTC] Routing problem gaston
2003-09-07 23:03 ` Damion de Soto
2003-09-08 6:41 ` Ronny Aasen
2003-09-08 14:46 ` gaston
2003-09-09 13:59 ` gaston
2003-11-10 12:29 ` [LARTC] routing problem Meretei Balázs
2003-11-10 23:55 ` Damion de Soto
2003-11-11 4:22 ` Martin A. Brown
2004-04-06 11:09 ` [LARTC] Routing problem huffo
2004-04-06 12:28 ` huffo
2004-04-06 23:32 ` Damion de Soto
2004-04-07 1:16 ` huffo
2004-04-07 1:26 ` huffo
2006-12-12 13:07 ` [LARTC] Routing Problem Javier A Toledano
2006-12-13 15:05 ` Taylor, Grant
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=marc-lartc-103792641804687@msgid-missing \
--to=lartc@compucenter.org \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox