dick hoogendijk <[EMAIL PROTECTED]> wrote:

> The situation:
> A server with two wired Ethernet cards
> rl0 to the outside (ISP)
> rl1 to the local network (192.168.11.1)
> The server does routing NAT and DHCP; pf is enabled (quite a normal
> situation ;-)
> 
> The NEW situation (802.11-to-ethernet bridge)
> I will add a wireless card to the server. This way my notebook and my
> (nintendo) DS will have access to the internet.
> 
> As I understand it after reading articles, the handbook and man
> if_bridge it goes like this:
> 
> NOW I have in rc.conf:
> defaultrouter="82.74.2.1"
> hostname="lothlorien.nagual.st"
> ifconfig_rl0="inet 82.74.2.186 netmask 255.255.254.0"
> ifconfig_rl1="inet 192.168.11.1 netmask 255.255.255.0"
> 
> After adding the WiFi card this whould be:
> defaultrouter="82.74.2.1"
> hostname="lothlorien.nagual.st"
> ifconfig_rl0="inet 82.74.2.186 netmask 255.255.254.0"
> ifconfig_rl1="inet 192.168.11.1 netmask 255.255.255.0"
> ifconfig_ath0="ssid airport01 media autoselect mode 11g mediaopt \
>       hostap wepmode on wepkey `cat /etc/wepkey` channel 1 up"
> 
> And than I bridge the two "internal" cards with:
> cloned_interfaces="bridge0"
> ifconfig_bridge0="addm ath0 addm rl1 up"
> 
> Once the interfaces are bridged I should be golden (I'm told).
> But I still have some questions:
> 
> (1) Is the above syntax OK? Did I understand it all correctly?

You didn't specify the default wepkey, but the syntax looks
OK to me.

> (2) Will the IP of the wireless card be the same as the cabled (rl1)
> card (192.168.11.1)? So, a cabled workstation contacting 192.168.11.1
> would reach rl1 and a wireless one ath0? Is this correct?

The wireless NIC doesn't get rl1's ip address,
it just sees more or less the same traffic. 

BTW don't bridge your wireless and wired networks if you don't have to.
If your only goal is to get internet access for your wireless
clients, it's probably safer to just add another NAT zone.

Fabian
-- 
http://www.fabiankeil.de/

Attachment: signature.asc
Description: PGP signature

Reply via email to