Joined: 18 Jun 2006 Posts: 308 Location: Coswig, S-A, Germany
Posted: Wed Jun 04, 2008 15:47 Post subject:
I tested the vintage build from 20 May (9217) and it works . I flashed back to std gen and it has the apply problem. I made a reboot, apply, changed something (Timeserver) and press apply again and it works after that.
The same problem with gen newd from may 21th.
nvram get corerev -> 9 _________________ Wer HF mißt, mißt Mist!
1 AP mit WRT54GL und Tomato 1.13
5 Clients mit WRT54GL dd-wrt v24RC62
1 NSLU2
I got this mostly working with v24 final (build 9513) on a Buffalo WHR-HP-G54, but when I am on a client connected wirelessly to the virtual SSID and try to ping a machine connected by ethernet, occasionally a packet gets through, perhaps 1-3% of packets attempted, so the blockage is not working completely. When I ping in the other direction, I see a similar effect.
I configured as suggested by the tutorial, with these specific settings:
Local IP Address 192.168.0.1
Subnet Mask 255.255.255.0
Virtual Interface wl0.1
AP Isolation Disabled
Unbridged
Multicast forwarding Disabled
IP Address 192.168.1.1
Subnet Mask 255.255.255.0
DNSMasq: Enable
Local DNS: Disable
Additional DNSMasq Options
.. I have painstakingly read and tried some variations to no avail.
I can connect to wl0.1, and I receive an IP in the 192.168.2.x range, so I know that's working.
But I cannot connect to the internet, can't ping the router, can't ping the gateway, zip .. which sounded like the same issue that others were having last month.
Joined: 12 Jun 2006 Posts: 24 Location: Wisconsin, USA
Posted: Tue Jul 08, 2008 13:04 Post subject:
Sorry, but I have to bump this. I've read a dozen threads on the subject now .. and many have the same issue, able to create a VLAN, connect, get a DHCP address, yet no connection to the internet. -- No ping to the router, either the wl0, nor wl0.1 IPs.
There's gotta be something preventing the conversation from wl0.1 to the WAN.
The info Wrathchild25 provided worked for me. I had to upgrade to the final v24 for the router. So far everything works with the VAP I setup with one exception - I can ping the primary router IP address and even log onto the router while connected to the VAP. I suspect I either need to check the "isolate AP" box on the VAP or enter in some additional firewall rules but I'm not sure what would need to be entered.
I tried three different sets of iptables commands, all with the same 2%-3% packet leakage when I try to ping from wireless laptop on virtual SSID to wired computer.
The issue I have is that when connected to the test VAP signal, I can ping the router. I cannot ping a single machine on the network (I don't get any leaks either) but I can access the router. Need to fix that.
The issue I have is that when connected to the test VAP signal, I can ping the router. I cannot ping a single machine on the network (I don't get any leaks either) but I can access the router. Need to fix that.
Which version of DD-WRT are you on (include build number). I wouldn't care if I can ping the router as long as I can stop the packet leaking. BTW, to see the leaking, I need to leave the ping command run long enough to try 100 or so packets, then I see two or three leak in a row usually.
On my WRT54G v2 I'm running the v24_9517_VINT_std. On my WAP54G v2 I'm running the v24_9517_VINT_micro.
I have now setup two additional VAP's but have not fully tested ping from either yet. I'd still like to find a way to lock down ping to the router as well as prevent access to the main router from the VAP's. I figure this is a command for the firewall but I simply do not know the commands to make it work.
I upgraded to V24 TNG build 9856 standard on my Buffalo WHR-HP-G54 and reconfigured the same way to have a virtual SSID, hoping to fix the packet leaking issue on V24 final 9513 and find that when a client connects to the virtual SSID it cannot access the internet. This is even if I take out the IP tables rules altogether. I configured the other settings as I had done in the older build, according to the tutorial.
What builds does this feature work properly in? The last build I saw work properly is RC7. Should I go back to that one? Ever since V24 final came out and I thought I should upgrade to final, I've had nothing but problems that seem to be getting worse with newer builds. First its packet leaking, then it don't work at all.
I switched to V24 Final build 9526 and eliminated the leaking package problem, but I have a new problem to take its place - some internet requests from the virtual SSID do not go out properly. See http://www.dd-wrt.com/phpBB2/viewtopic.php?t=35245
WRT54Gv4 running DD-WRT v24 (05/24/2008) std (SVN revision 9526) is dropping my Virtual Interface wl0.1 SSID [Guest] "guest account".
The connection will work for about 30sec to 1min then drop. The connection is secured w/ WPA2 personal mixed. I have tried several wireless devices and the problem is repeated on all, 2 iPhone's and 2 laptop's.
Why is this happening and how do I fix this issue?
Also, I have no problems/drops with the Physical Interface wl0 - SSID. Thanks in advance for any replies.
Thanks for the great software! Just got it set-up on my WRT-54GS (v1.1) with the vintage bin.
Working on multiple SSIDs (WPA2 for lappy and WEP for TiVo).
QUESTION:
Does anyone know if there are COMMANDS to throttle the bandwidth for the virtual SSID?
I looked, but only saw instructions for FON; not sure if it would work (what is "DEV=tun0"?; I assume that my DEV is not tun0, right?)
Would the following command work just for wl0.1 (where I could adjust the DOWNLINK and UPLINK numbers)?
DEV="tun0"
# change UP/DOWNLINK values (in kbps) to alter hotspot users up/download speeds
DOWNLINK="1024"
UPLINK="256"