| 1 |
On 12 Jun 2009, at 00:38, Grant wrote: |
| 2 |
>>> ... |
| 3 |
>>> I've almost got this working, but I don't know what to include in |
| 4 |
>>> the |
| 5 |
>>> /etc/conf.d/hostapd INTERFACES variable since I don't have a br0 |
| 6 |
>>> device or configuration. Do I need one? If I leave INTERFACES |
| 7 |
>>> empty |
| 8 |
>>> and I don't start net.wlan0, I don't have a way to define the IP |
| 9 |
>>> address for the AP, and shorewall's "loc" zone is empty because |
| 10 |
>>> net.wlan0 hasn't started. |
| 11 |
>> |
| 12 |
>> What do you want to do with your accesspoint. You will need a |
| 13 |
>> bridge to a |
| 14 |
>> wired network if you want your ap attached to that wired network. |
| 15 |
>> This is |
| 16 |
>> quite usual though... |
| 17 |
>> Without a bridge to a wired network, only the wlan systems are |
| 18 |
>> connected and |
| 19 |
>> can not connect to your wired systems. |
| 20 |
> |
| 21 |
> That's no problem, I'm OK with keeping eth1 and wlan0 separate. Right |
| 22 |
> now I just want to get wlan0 working. Do you know how to do that? I |
| 23 |
> can't start net.wlan0 because it chokes on master mode, so I don't |
| 24 |
> know how to specify an IP for the AP or how to fill shorewall's "loc" |
| 25 |
> zone as that is normally filled by net.wlan0. |
| 26 |
|
| 27 |
Hi there, |
| 28 |
|
| 29 |
I haven't used Shorewall, but for this you probably want to use |
| 30 |
bridging. I fear that may not be available in Shorewall's UI. |
| 31 |
|
| 32 |
I originally wrote <http://en.gentoo-wiki.com/wiki/Wireless/ |
| 33 |
Access_point>, but that was some years ago now. It has had many |
| 34 |
contributions since, but I have no idea if it's up to date. |
| 35 |
|
| 36 |
Anyway, using the "simple NAT-forwarding setup" described in that |
| 37 |
article (surely possible in Shorewall) the wireless laptop can access |
| 38 |
the internet and wired PCs on the LAN. However it is not possible for |
| 39 |
wired PCs to (say) browse to file shares on the laptop without port- |
| 40 |
forwarding - because you use a NAT, you have exactly the same problem |
| 41 |
as accessing your home-server from the office. |
| 42 |
|
| 43 |
Bridging brings the wireless clients *seamlessly* into the wired LAN - |
| 44 |
they behave exactly like the wired clients do. One can install Apache |
| 45 |
on the wireless laptop and immediately connect to it from a wired PC. |
| 46 |
This is how all standalone ADSL wireless routers (eg Netgear DG834G) |
| 47 |
operate. |
| 48 |
|
| 49 |
I can't be of much practical help, as I have for some time been using |
| 50 |
a Fon access-point, which is plugged into a network switch near my |
| 51 |
desk and which gives me NATted wifi. It works, but I sure do miss |
| 52 |
teleportd <http://abyssoft.com/software/teleport/>, which is crippled |
| 53 |
without bridging. |
| 54 |
|
| 55 |
Stroller. |
Archives