From: "Terry L. Ridder" <terrylr@blauedonau.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] routing problem with multiple connections
Date: Fri, 06 Apr 2001 08:19:46 +0000 [thread overview]
Message-ID: <marc-lartc-98654506816215@msgid-missing> (raw)
In-Reply-To: <marc-lartc-98654195309645@msgid-missing>
hello;
i may have found part of the problem.
each interface in the laptop router has
an unique ip address. i.e.
eth0 = x.y.z.202
eth1 = x.y.z.208
eth2 = x.y.z.209
eth3 = x.y.z.210
in rereading the linux wireless howto
the example router has the same ip address
on all interface. i.e.
eth0 = x.y.z.202 netmask 255.255.255.255
eth1 = x.y.z.202 netmask 255.255.255.255
eth2 = x.y.z.202 netmask 255.255.255.255
eth3 = x.y.z.202 netmask 255.255.255.255
with a default route on eth2.
i would assume that eth0, eth1, and eth3
are all proxy-arped.
On Fri, 6 Apr 2001, terrylr@blauedonau.com wrote:
terrylr> hello;
terrylr>
terrylr> here is the problem.
terrylr>
terrylr> i have a laptop running linux-2.4.3 with three wireless
terrylr> ethernet cards installed and an actual ethernet card
terrylr> acting as a router.
terrylr>
terrylr> eth0 connects to the wired ethernet in my home.
terrylr>
terrylr> eth1 connects to the first orinoco card which is
terrylr> the local wireless cell this is in home use.
terrylr>
terrylr> eth2 connects to the second orinoco card which has
terrylr> and 24dbi gain parabolic directional antennea and
terrylr> will eventually be a 512mbs connection to the internet.
terrylr>
terrylr> eth3 connects to the third orinoco card which has
terrylr> an external antennea so i am able to sit outside and
terrylr> work on the computers.
terrylr>
terrylr> any computers on the wired ethernet are able to ping
terrylr> the laptop router but are unable to ping any wireless
terrylr> computer.
terrylr>
terrylr> any computer on the local in home wireless are able
terrylr> to ping the laptop router but are unable to ping
terrylr> any computer on the wired ethernet.
terrylr>
terrylr> any computer on the wireless networks with external
terrylr> antennea is able to ping any other wireless computers
terrylr> and the laptop router but unable to ping the wired
terrylr> ethernet computers.
terrylr>
terrylr> the ip numbers are valid internet numbers. it is
terrylr> my legacy class c ip range. there are no subnets.
terrylr>
terrylr> all wireless cards are in ad-hoc mode with 128bit
terrylr> encryption enabled.
terrylr>
terrylr> i am trying to route any wireless computer to the
terrylr> wired ethernet.
terrylr>
terrylr> i am trying to route the wired ethernet to eth2
terrylr> as internet default gateway.
terrylr>
terrylr> what am i missing?
terrylr>
terrylr>
--
Terry L. Ridder
Blue Danube Software (Blaue Donau Software)
"We do not write software, we compose it."
digging deep, i feel my conscience burn
i need to know who and what i am
this hunger jolts me from complacency
rocks me, makes me meet myself
----kendall payne---closer to myself---
_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/
prev parent reply other threads:[~2001-04-06 8:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-04-06 7:26 [LARTC] routing problem with multiple connections terrylr
2001-04-06 8:19 ` Terry L. Ridder [this message]
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-98654506816215@msgid-missing \
--to=terrylr@blauedonau.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.