public inbox for linux-newbie@vger.kernel.org
 help / color / mirror / Atom feed
From: James Miller <jamtat@mailsnare.net>
To: linux-newbie@vger.kernel.org
Subject: Re: making a gateway with eth0 wired eth1 wireless
Date: Thu, 30 Dec 2004 11:52:59 -0600 (CST)	[thread overview]
Message-ID: <Pine.LNX.4.58.0412301148281.7477@localhost.localdomain> (raw)
In-Reply-To: <Pine.LNX.4.58.0412301114280.7477@localhost.localdomain>

On Thu, 30 Dec 2004, James Miller wrote:

> ------------BEGIN LINKSYS MANUAL EXCERPT-------------------------
<snip>
>   Note: For all modes of operation EXCEPT Access Point, the remote access
> point must be a second Linksys Wireless-B Access Point (WAP11). The Access
> Point will not communicate with any other kind of remote access

Oops. I overlooked that note this time. This is probably why I earlier
determined I could not use this thing as a wireless client: what are the
chances the network it's on is going to have exactly the same Linksys
wireless B access point? Is this really the show-stopper it seems to be,
or is this just some corporate posturing attempt to keep people from using
other companies' hardware?

James
-
To unsubscribe from this list: send the line "unsubscribe linux-newbie" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.linux-learn.org/faqs

  reply	other threads:[~2004-12-30 17:52 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-12-30 15:03 making a gateway with eth0 wired eth1 wireless James Miller
2004-12-30 16:36 ` Ray Olszewski
2004-12-30 17:43   ` James Miller
2004-12-30 17:52     ` James Miller [this message]
2004-12-30 18:40     ` Ray Olszewski
2004-12-31  5:18 ` chuck gelm
2004-12-31 15:24   ` James Miller
2004-12-31 19:18     ` chuck gelm
2004-12-31 19:34       ` Ray Olszewski
2004-12-31 20:15         ` chuck gelm

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=Pine.LNX.4.58.0412301148281.7477@localhost.localdomain \
    --to=jamtat@mailsnare.net \
    --cc=linux-newbie@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