[Voyage-linux] Wrap Voyage 2.6.20-486-voyage DHCP relay howto?

Kim-man 'Punky' TSE (spam-protected)
Wed Feb 27 18:44:35 HKT 2008


Hi,

Clear enough, I use ONE of the following ways.  My setup is different 
than your, so you need some explorations.

1) set up wireless client in 10.1.20.x, all wireless traffic NAT'd from 
10.1.20.x to eth0 (internet outbound).  (I run dnsmasq to provide dhcp 
for 10.1.20.x, see  /etc/dnsmasq.more.conf)

auto ath0
iface ath0 inet static
        address 10.1.20.1
        netmask 255.255.255.0
        broadcast 10.1.20.255
         madwifi-base wifi0
         wireless-mode Master
        up iwpriv ath0 mode 3
        up iwconfig ath0 mode master
        up iwconfig ath0 essid voyage channel 1
        up iwconfig ath0 txpower auto
        up iwconfig ath0 enc off
        up iwconfig ath0 rate auto
        up nat.sh ath0 eth0 "10.1.20.0/24"

2.  Set up wireless bridge on 192.168.1.2, bridging eth0 and ath0 to br0
auto br0
iface br0 inet static
       address 192.168.1.2
       netmask 255.255.255.0
       network 192.168.1.0
       broadcast 192.168.1.255
       gateway 192.168.1.1
       bridge_ports eth0 ath0
       pre-up wlanconfig ath0 create wlandev wifi0 wlanmode ap
       pre-up iwpriv ath0 mode 11g
       pre-up iwconfig ath0 essid "voyage" channel 1
       up ifconfig ath0 down ; ifconfig ath0 up # this is a workaround
       post-down wlanconfig ath0 destroy

Regards,
Punky

Joost Kraaijeveld wrote:
> Hi Punky, 
>
>
> On Sun, 2008-02-17 at 21:15 +0800, Kim-man 'Punky' Tse wrote:
>   
>> Hi,
>>
>> You have 2 method to do so.
>>
>> 1. Use voyage to provide DHCP service to your wireless client.  You can 
>> start dnsmasq for this purpose.  Read /etc/dnsmasq.more.conf and 
>> /etc/network/interfaces has some sample conf for setting up 10.1.x.x 
>> network.
>>     
> This is not option as my laptops need to be in the same network.
>
> So
>   
>> 2. Make your wrap AP as bridge, read /etc/network/interface, there is an 
>> example to run atheros card as AP.
>>     
> The sample is not clear enough for me (nor am I smart enough ;-))
>
> Maybe you can help me a bit.
>
> My current setup is like this (and working ok, except for the wireless):
>
> etho: uplink to internet
> eth1: 192.168.0.254, (NAT) router for the 192.168.0.0/24 network
> eth2: 192.168.1.254, (NAT) router for the 192.168.1.0/24 network
> ath0: Doing nothing right now, but it has an address in the
> 192.168.0.0/24 network and it is visible by the wireless laptops. There
> is even communication which is visible when I use tcpdump on the laptops
> and /or on wrap router. Should provide access for wireless laptops to
> the 192.168.0.0/24 network and internet.
>
> My current settings for eth1/ath0:
>
> auto eth1
> iface eth1 inet static
>     address 192.168.0.254
>     network 192.168.0.0
>     netmask 255.255.255.0
>
> auto ath0
> iface ath0 inet static
>         address 192.168.0.253
>         netmask 255.255.255.0
>         broadcast 192.168.0.255
>         #pre-up wlanconfig ath create wlandev wifi1 wlanmode ap
>          madwifi-base wifi0
>          wireless-mode Master
> #         wireless-mode Adhoc
> #         wireless-mode Managed
>         up iwpriv ath0 mode 3
>         up iwconfig ath0 mode master
>         up iwconfig ath0 key s:XXXXXXXXXXXX
>         up iwconfig ath0 essid XYZ
>         up iwconfig ath0 txpower auto
> #        up iwconfig ath0 enc off
>         up iwconfig ath0 rate auto
> #        up nat.sh ath0 eth0 "10.1.20.0/24"
>
>
> 2 questions:
> 1. Which of the WDS bridge samples should I use: madiwifi-ng WDS bridge
> or the hostap WDS bridge?
> 2. Could you spell out the exact (as possible) settings  I must use? I
> really have tried a lot of combinations/settings, but up to now, they
> all lead to some kind of "must use a terminal because I lost network
> connection" or "where is the on/of switch"???? I even tried sacrificing
> a young goat on the wireless antenna but that did not work either....
>
> TIA
>
>   


-- 
Regards,
Punky

Voyage Solutions (http://solution.voyage.hk)
* Embedded Solutions and Systems
  - Mesh Networking, Captive Portal, IP Surveillance, VoIP/PBX
  - Network Engineering, Development Platform and Consultation
  
	





More information about the Voyage-linux mailing list