befw11s4 as an access point only

Hello,

I have a BEFW11S4 with firmware 1.50 that I want to use as an access
point only.

I have disabled the DHCP and connected it to the network via one of the
LAN ports. Nothing is connected to the WAN port. The DHCP has been
disabled as there are two other, more powerful DHCP servers on the
network. I need the wireless clients to use these servers and the
assigned addresses as there are other WAP11s and they need to have a
consistent address across the points.

Is there anything else that needs to be set so the BEFW11S4 doesn't try
to appear as a (dead) gateway/router on the network?

Thanks.

Roger Vicker, CCP

--
*** Vicker Programming and Service *** Have bits will byte *** www.vicker.com ***
Congress hammers out budget; we get nailed.

Roger Vicker, CCP <(E-Mail Removed)> wrote:
> I have a BEFW11S4 with firmware 1.50 that I want to use as an access
> point only.

> I have disabled the DHCP and connected it to the network via one of the
> LAN ports. Nothing is connected to the WAN port.

Sounds good to me. If you want to use all of the LAN ports, there is even
an option to make the befw11s4 a normal router instead of a gateway. Then
you could still ignore the DHCP and NAT, and use the WAN connection to the
rest of the network. "Working Mode" on the Dynamic Routing page of the
configuration.

--
---
Clarence A Dold - Hidden Valley (Lake County) CA USA 38.8-122.5

On 12/23/2003 1:56 PM, (E-Mail Removed) wrote:

>Roger Vicker, CCP <(E-Mail Removed)> wrote:
>
>
>>I have a BEFW11S4 with firmware 1.50 that I want to use as an access
>>point only.
>>
>>
>
>
>
>>I have disabled the DHCP and connected it to the network via one of the
>>LAN ports. Nothing is connected to the WAN port.
>>
>>
>
>Sounds good to me. If you want to use all of the LAN ports, there is even
>an option to make the befw11s4 a normal router instead of a gateway. Then
>you could still ignore the DHCP and NAT, and use the WAN connection to the
>rest of the network. "Working Mode" on the Dynamic Routing page of the
>configuration.
>
>
>
I only need the one port as the befw11s4 is remotely placed and powered
with a PoE. However on the setup/advanced routing/dynamic section there
is only RIP settings as of version 1.50. Also, as a router don't the two
sides (wan/lan) have to be different sub-nets in order to be "routed"?

Thanks.

Roger Vicker, CCP

--
*** Vicker Programming and Service *** Have bits will byte *** www.vicker.com ***
Congress hammers out budget; we get nailed.

Roger Vicker, CCP <(E-Mail Removed)> wrote:
> I only need the one port as the befw11s4 is remotely placed and powered
> with a PoE. However on the setup/advanced routing/dynamic section there
> is only RIP settings as of version 1.50. Also, as a router don't the two
> sides (wan/lan) have to be different sub-nets in order to be "routed"?

I was looking at a version 2 manual. I haven't actually used that mode.

I used it like you are doing for a while. I was told about the router
option later, and told that it would function in that mode as a switch
on the same subnet.

--
---
Clarence A Dold - Hidden Valley (Lake County) CA USA 38.8-122.5

On 12/23/2003 3:00 PM, (E-Mail Removed) wrote:

>Roger Vicker, CCP <(E-Mail Removed)> wrote:
>
>
>>I only need the one port as the befw11s4 is remotely placed and powered
>>with a PoE. However on the setup/advanced routing/dynamic section there
>>is only RIP settings as of version 1.50. Also, as a router don't the two
>>sides (wan/lan) have to be different sub-nets in order to be "routed"?
>>
>>
>
>I was looking at a version 2 manual. I haven't actually used that mode.
>
>I used it like you are doing for a while. I was told about the router
>option later, and told that it would function in that mode as a switch
>on the same subnet.
>
>
>
This is actually Version 4 of the hardware with firmware 1.50.

I don't really want to use another valid address as the firewall is
licensed by address and nearing the limit.

BTW I tried setting the Internet Connection to "Obtain an IP
automatically" and it locked up within the hour. Set it back to "Static
IP" with a dummy private sub-net address and it seems to be staying up.

Thanks.

Roger Vicker, CCP

--
*** Vicker Pony Farm *** www.vicker.com/vpf ***
*** Vicker Programming and Service *** Have bits will byte *** www.vicker.com ***
Congress hammers out budget; we get nailed.

Roger Vicker, CCP <(E-Mail Removed)> wrote:

> This is actually Version 4 of the hardware with firmware 1.50.

I sort-of spotted that possibility when I saw another posting that listed
the hardware and software versions.

> I don't really want to use another valid address as the firewall is
> licensed by address and nearing the limit.

That would tend to have me leaning the other way. If you let the WAP do
NAT, you would only be using one address from the "main" network.
Depending on what you wireless systems are doing on the rest of your local
network, this might work just fine. You could even add some other machines
to the private hard-wired network.

If you connect your existing router (possibly via a crossover cable, maybe
not) to the WAN port, and enable DHCP on the Linksys, can you do what you
need to do to the rest of the network?

I also ran in this mode for a while in a couple of situations. In one cas,
I moved. In the other case, I could connect out just fine for everything
that I needed, but I couldn't connect back the other way to run VNC.

> BTW I tried setting the Internet Connection to "Obtain an IP
> automatically" and it locked up within the hour. Set it back to "Static
> IP" with a dummy private sub-net address and it seems to be staying up.

Which Internet Connection are you talking about? If you have DHCP
disabled, and your company LAN is plugged in to a LAN port on the Linksys,
the internal router has nothing to do, and the IP address goes unused. If
you set that to DHCP, it might get annoyed if it can't find one.

--
---
Clarence A Dold - Hidden Valley (Lake County) CA USA 38.8-122.5

<(E-Mail Removed)> wrote in message news:bsag04$imi$(E-Mail Removed)...
Roger Vicker, CCP <(E-Mail Removed)> wrote:

> I don't really want to use another valid address as the firewall is
> licensed by address and nearing the limit.

That would tend to have me leaning the other way. If you let the WAP do
NAT, you would only be using one address from the "main" network.
Depending on what you wireless systems are doing on the rest of your local
network, this might work just fine. You could even add some other machines
to the private hard-wired network.

If you connect your existing router (possibly via a crossover cable, maybe
not) to the WAN port, and enable DHCP on the Linksys, can you do what you
need to do to the rest of the network?

I also ran in this mode for a while in a couple of situations. In one cas,
I moved. In the other case, I could connect out just fine for everything
that I needed, but I couldn't connect back the other way to run VNC.

The wireless clients roam between access ports (including WAP11s that
don't NAT) and for various security and management reasons they need to
keep static addresses.

Funny you should mention VNC. I've been using it on several PCs for help
desk uses. With NAT or a firewall you have to set up mappings of the
incoming port (which can be varied by screen#) to the internal address.
Map port 5900 to 5900 and internal address for screen 0 (default), 5901
to 5901 for screen 1 and so forth.



> BTW I tried setting the Internet Connection to "Obtain an IP
> automatically" and it locked up within the hour. Set it back to "Static
> IP" with a dummy private sub-net address and it seems to be staying up.

Which Internet Connection are you talking about? If you have DHCP
disabled, and your company LAN is plugged in to a LAN port on the Linksys,
the internal router has nothing to do, and the IP address goes unused. If
you set that to DHCP, it might get annoyed if it can't find one.


With the new GUI of firmware 1.50 they call the WAN port the Internet
Connection. Probably for the homeys that don't know what they are really
doing. The version 4 hardware has a problem of locking up. One of the
work arounds has been to use Static IP on the WAN port even with nothing
connected to it. Firmware 1.50 has helped but it is still a problem
without the Static IP.

Roger Vicker, CCP



--
*** Vicker Programming and Service *** Have bits will byte *** www.vicker.com ***
He who hesitates is lost.