Posted: Sun Jan 31, 2010 8:20 Post subject: Setting up Chillispot on virtual interface only
Hi,
I would like to set up hotspot on my Buffalo WHR-G54S device. After reading wikis@dd-wrt.com there are several configurations available like:
One Network Subnet-move all clients (LAN & WIFI) to Chilli
Two Networks, WiFi separated from LAN-move only wireless users to Chilli.
What I want is a third scenario and that is create additional wireless virtual interface and apply Chilli on itself only. How would I accomplish this, is that possible?
Posted: Sun Jan 31, 2010 8:25 Post subject: Re: Setting up Chillispot on virtual interface only
dpetrek wrote:
Hi,
I would like to set up hotspot on my Buffalo WHR-G54S device. After reading wikis@dd-wrt.com there are several configurations available like:
One Network Subnet-move all clients (LAN & WIFI) to Chilli
Two Networks, WiFi separated from LAN-move only wireless users to Chilli.
What I want is a third scenario and that is create additional wireless virtual interface and apply Chilli on itself only. How would I accomplish this, is that possible?
Thank you.
Regards,
Drazen
this is not a third choice but only the second! ;)
when separate lan from Wlan, Chillispot act on a Vlan separate from your local network.
after adding wl0.1 interface, i have LAN, WLAN and WLAN under "DHCP interface" on Chilli settings page.
tried choosing third option, however after router restarted i can't connect to my default wireless network anymore only to hotspot network.
after i disable chillispot i can connect to both networks without problems.
i could also manually create additional bridge br1 and assign wl01 to it. is it neccessary to manually create bridge after adding additional virtual interface for Chilli?
after adding wl0.1 interface, i have LAN, WLAN and WLAN under "DHCP interface" on Chilli settings page.
tried choosing third option, however after router restarted i can't connect to my default wireless network anymore only to hotspot network.
after i disable chillispot i can connect to both networks without problems.
i could also manually create additional bridge br1 and assign wl01 to it. is it neccessary to manually create bridge after adding additional virtual interface for Chilli?
what kind of relaase do you use? V24 ? V24 SP1? V24 SP2?
You need to read the forum announcements and update to a current version to be able to choose a VAP interface for chillispot. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
Add wl0.1 to a bridge (br1) like you talked about above. Wireless interfaces, especially VAP's, have trouble being unbridged. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
I notice that you are a VAP guru, so I thought I should make your life interesting. Regrettably, I am fresh out of e-beer, so I am falling back on asking you a challenging question instead.
Works perfect. I am using same authentication (WPA2 Personal) on both the VAP(wl0.1) and physical AP (wl0).
When I turn on Chillispot, and point the Chillispot DHCP to br1 (the VAP) then the problems start.
br1 works fine. The authenticated wireless user on the VAP gets Worldspot, logs on, and all is good. However on wl0 (first SSID) an attempt to associate results in "Acquiring IP Address", followed by connection drop, followed by "Acquiring IP Address" and then a final drop.
I have seen this behavior before, and have come to associate it with an explicit DHCP request rejection. So my present working theory is that the explicit bridging specified on the SSID config page for first SSID (Physical Interface wl0) is getting hosed up by the Chillispot configuration. (Yes I did specify "Separate" on the Chillispot config)
I suppose the easiest way to work around this to turn off the bridge button on the first SSID (not the VAP) and then assign an explicit DHCPd in the Multiple DHCP Server dialog box for br0, same as I did for br1?
I will try this tonight, but in the meantime, is there a better way to do it using the GUI?
It looks like dpetrek (in this thread) is seeing this same issue.
I notice that you are a VAP guru, so I thought I should make your life interesting. Regrettably, I am fresh out of e-beer, so I am falling back on asking you a challenging question instead.
Works perfect. I am using same authentication (WPA2 Personal) on both the VAP(wl0.1) and physical AP (wl0).
When I turn on Chillispot, and point the Chillispot DHCP to br1 (the VAP) then the problems start.
br1 works fine. The authenticated wireless user on the VAP gets Worldspot, logs on, and all is good. However on wl0 (first SSID) an attempt to associate results in "Acquiring IP Address", followed by connection drop, followed by "Acquiring IP Address" and then a final drop.
I have seen this behavior before, and have come to associate it with an explicit DHCP request rejection. So my present working theory is that the explicit bridging specified on the SSID config page for first SSID (Physical Interface wl0) is getting hosed up by the Chillispot configuration. (Yes I did specify "Separate" on the Chillispot config)
I suppose the easiest way to work around this to turn off the bridge button on the first SSID (not the VAP) and then assign an explicit DHCPd in the Multiple DHCP Server dialog box for br0, same as I did for br1?
I will try this tonight, but in the meantime, is there a better way to do it using the GUI?
It looks like dpetrek (in this thread) is seeing this same issue.
Posted: Tue Mar 09, 2010 2:56 Post subject: Disabling br1 makes it worse
Bonjour yzy-oui-sans-fil,
I have followed you recommendation. Specifically:
a) Configured two SSIDs, both bridged
b) Set DHCP interface on Chillispot to wl0.1
c) On the Networking tab, removed all special DHCP and extra bridges - default config.
d) Apply Settings + Reboot
e) Power Cycle
Now both SSID interfaces are behaving badly, namely they will associate, reject the DHCP request and drop.
Also, in this same thread, I note that phuzi0n comments:
phuzi0n Posted: Mon Feb 01, 2010 1:17 am Post subject:
Add wl0.1 to a bridge (br1) like you talked about above. Wireless interfaces, especially VAP's, have trouble being unbridged.
