Archived from groups: alt.internet.wireless (
More info?)
On 10 Nov 2004 06:10:42 -0800, jjcuzz@hotmail.com (Giovanni) wrote:
>Ok, I will explain what I need to do. We have a novell network with
>bordermanager.
Hopefully, you're running IP as a protocol, not IPX/SPX. IPX/SPX does
work with access points (that work on layer 2 MAC and don't know
anything about higher level protocols), but the timing is really
bizarre. When I tried it, performance was really erratic. Of course,
none of the cheapo wireless routers will work because they route only
IP.
>I have recycled 3 linksys wireless router g( for this I
>know I should have got access point). The novell bordermanager does
>not use dhcp. I need wireless company wide, so that people with wi-fi
>Pocket PCs and people with laptop can connect wireless if they need
>and authorized.
You can assign fixed IP address to every wireless client and device,
but I don't recommend it. The labour and complications (along with
potential mistakes) is far to great. Portable clients, such as
laptops and PDA's should use DHCP to get their IP numbers.
If you don't currently have a DHCP server, I suggest you setup one.
Some companies do not enable DHCP servers as some kind of
authentication and security measure, so be careful here with policy
issues.
If a central DHCP server is not possible or practical, you can enable
the DHCP servers in the wireless routers (used as access points) if
make absolutely sure they don't have overlapping ranges. This works
fine for a small number of access points, but rapidly becomes a mess
with anything over perhaps 5 access points. I would suggest a single
central DHCP server.
>Now that I think of, I might not need to use the same subnetwork. The
>main reason was: I need to VNC the clients for support, but as long I
>have the port forwarding I should be able to shadow those clients. The
>wireless router can have any subnetwork, and I would still be able to
>do the job.
>
>Am I correct ?
No. The problem with using an NAT router for wireless is that you can
open a port to single specific client computah, but with DHCP, you
could never be sure that the forwarded port leads to the specific
client (as the IP address might change). Similarly, you don't know
which router would have client connected. Lastly, you can open only
ONE port from a router WAN port to specific client computah. If you
wanted to connect to another client, you would need either a different
port number, or need to reconfigure the router every time you try and
connect. All you've done is transfer the fixed IP administration mess
to the port number management mess. Not recommended. Use access
points and a central DHCP server.
VNC port forwarding using SSH.
http://www.ltsp.org/contrib/vnc.html
--
Jeff Liebermann jeffl@comix.santa-cruz.ca.us
150 Felker St #D
http://www.LearnByDestroying.com
Santa Cruz CA 95060 AE6KS 831-336-2558