Wireless *switch*?

Matt Brodeur mbrodeur at NextTime.com
Tue Dec 7 11:21:01 EST 2004


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Tue, Dec 07, 2004 at 10:10:07AM -0500, Cole Tuininga wrote:

> I don't have a lot of experience with wireless access points, but I'd
> gotten the impression that most (if not all?) of them act as a router. 
> For instance, the one I have right now gets a single IP on the existing
> network (specifically, 192.168.101.100) and then all devices that
> wirelessly connect are NAT'd behind it on their own class C
> (specifically, 192.168.0.0/24).  
> 
> Am I making sense?

   You're making sense, but you're also making this harder than it
needs to be.  Assuming you already have a wireless router
(residential gateway, broadband sharing device, whatever), you can do
the following:
   1. Log in to the admin interface
   2. Disable DHCP service
   3. Set the LAN IP to something in your existing network.
      I like to use the top or bottom of the range for network
      devices, in your case 192.168.101.254 might work.
   4. Disconnect the WAN side of the router and reconnect your
      existing private network to a LAN port instead.

   That should be it.  If you ignore the WAN side of these devices
they're nothing more than a combined access point and 4+ port switch.
You just want to make sure that the router's DHCP is disabled so that
your existing DHCP server will be the only one on that network.

- -- 
Matt Brodeur                                                       RHCE
MBrodeur at NextTime.com                           http://www.NextTime.com

Time sure flies when you don't know what you're doing.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iD8DBQFBtdhKc8/WFSz+GKMRAlATAJ0We5wCxvGAXBfBGxvCPea7mnIrlgCbB196
iosJU/FCAbGCnJ6sVhWBCBs=
=ZQNI
-----END PGP SIGNATURE-----



More information about the gnhlug-discuss mailing list