"Benedict Verheyen" <[EMAIL PROTECTED]> writes:
> my current LAN looks like this:
>
> cable ----- eth0 (public ip) -server
> modem eth1 (192.168.0.1)
> |
> hub
> |
> |
> pc 1
>
> My server runs dhcp, apache, exim, fetchmail, webmail and so on.
> Now the wife is fed up with the cable running through our living room
> up the stairs to my room where the server, the hub and pc1 are.
> Now we (she) wants to go wireless. I asked a local dealer and he
> works with D-Link equipment more specifically the Di-714P+ or
> the Di-614+. This would be the future setup:
>
> cablemodem --- router --wireless-- server -- hub -- pc 1
> |
> -----wireless-- clients
It looks like your local dealer is selling you the wrong product. :-)
You don't want a "wireless router"; in your situation, you want a
bare-bones "wireless access point". So my home network looks like:
cable --- server --- hub --> pc 1
+ --> pc 2
\ --> wireless
\ --> laptop
I can't really recommend any specific products in this space, but they
definitely do exist. If you've already bought it, you might see
whether you can turn off ~all of its features (it's probably set up as
a NAT box that does DHCP on the internal side) and deploy it in this
position on your network.
> 1. The server acts as a gateway now where eth0 is an ip from my
> isp and eth1 is a fixed internal ip where a DHCP daemon is listening
> to distribute ip's to the clients (currently pc1 but 1 other pc will
> follow and will be placed downstairs). Now i think i can still use
> the server as gateway with the new setup but i will not be able to
> secure the LAN with the firewall script that runs on it, correct?
In the diagram you have, "clients" gateway would be "router"; "hub"
wouldn't be used at all, except by "pc 1".
> 3. Is the network traffic encrypted by default?
Probably not. You can almost certainly enable WEP on the AP and on
the client machines, and with a sufficiently reputable product you
could probably also enable a MAC ACL ("limit which hardware addresses
can talk to the wireless network").
[My impression is that these are both useless steps, though: WEP is
almost trivially cracked, and many network cards let you change their
MAC address in software. So you still want to make sure that machines
inside the network are secure, and use end-to-end security if you're
transmitting sensitive data, even within the local net.]
> 4. What kernel options do i have to activate to be able to use a
> wireless usb card (DWL-120+) . Usb is already compiled in. I'm
> not even sure these will function under Linux. Any place i can
> find out?
I thought "USB network interface" was actually a somewhat standard
thing, so you might not need special drivers. In any case, looking on
http://www.linux-usb.org/ does seem to be informative, and support
does seem to exist for that particular card.
--
David Maze [EMAIL PROTECTED] http://people.debian.org/~dmaze/
"Theoretical politics is interesting. Politicking should be illegal."
-- Abra Mitchell
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
