On Mon, 1 Apr 2002, at 11:00pm, Larry A. Duncan wrote:
> I've tried every combination of the standard ports, the uplink port & the
> WAN port between the LAN hub and the WAP and none of them are simply
> "plug-n-play, life is good".
Do you get a link light on both your existing wired hub and the BEFW11S4
when you cable them?
> There's obviously some static mapping or something that the WAP has to
> know about to send the traffic to the other LAN.
I've used that unit myself, and there was nothing special to configure.
It was just a simple layer two bridge between two networks. I'm not sure
why you are having trouble. Try to isolate the problem:
#1: Give the BEFW11S4 an unused IP address on your existing LAN. Plug a
wired device into the switch. Can you ping the BEFW11S4?
#2: Configure a wireless device with another unused IP address on your
existing LAN. Can you ping the BEFW11S4?
#3: Can you ping from the first device to the second device, using the
BEFW11S4 as a bridge?
Which step fails?
> Why would I want to turn off the DHCP in the WAP?
Oh. I was assuming you already had a DHCP server on your LAN. If you do
not, then you can leave the DHCP server on the WAP enabled. Indeed, you
would likely want to. Sorry, my bad.
> You stated that NAT is not a good idea and that it doesn't work well with
> Microsoft's protocols. This WAP is NAT-based, as are many other things
> that exist quiet nicely in the Microsoft world. I've used NAT for this
> small LAN for two years now and have had no problems. What have you seen
> that would cause you to speak against it?
Okay, say system FOO is on the "WAN" side of a simple NAT router, and
system BAR is on the "LAN" side of the same router:
<-- NAT
(WAN) (LAN)
FOO <----------------> router <----------------> BAR
.2 x.y.z.0/24 .1 .1 10.0.0.0/24 .2
BAR will be able to address FOO by IP address. However, FOO will not be
able to reach BAR, since BAR is behind the NAT. LAN protocols, which
generally depend on systems having unique addresses, will be confused by
this. Sure, you can make some of it work, and kludge more of it, but in
general, you will find many things do not work right.
Unless you have a really pressing need to do so, I would not try to use
NAT *within* your LAN. (Between your LAN and the Internet is another matter
entirely.)
--
Ben Scott <[EMAIL PROTECTED]>
| The opinions expressed in this message are those of the author and do not |
| necessarily represent the views or policy of any other person, entity or |
| organization. All information is provided without warranty of any kind. |
------
You are subscribed as [email protected]
Archives: http://www.swynk.com/sitesearch/search.asp
To unsubscribe send a blank email to [EMAIL PROTECTED]
