Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Mon May 18, 2009 11:48 Post subject:
i'm uploading a new build now to others/eko/brainslayer-presp2. wpa2 should be fixed in it. please test and keep me up to date _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
I too can confirm WPA2 (both TKIP and AES) is working.
I have another problem. I have two of these units, one in AP mode the other in Repeater Bridge mode. Whenever I access the RB router from the AP side I receive packet errors.
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Mon May 18, 2009 16:06 Post subject:
since you always have inteferences, packet errors will always happen. thats normal _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
since you always have inteferences, packet errors will always happen. thats normal
I understand that Packet Loss is normal, but what I am saying is that it is more consistent when I access the remote rb router. I can have the routers up for 4 hours and no packet loss. Immediately upon accessing the remote rd (through the webgui) I will lose ~20 packets. And there won't be any packet lose for another 4 hours, assuming I don't connect to that router anymore.
DD-WRT v24-sp2 (05/18/09) std
Working good now Thx.
Set to G,B,N mix with WPA2-PSK Mix Mode and TKIP+AES
WPA-PSK AES client -- ok
WPA2-PSK AES client -- ok
SSH -- ok, SSH TCP Forwarding -- ok
DynDNS -- ok (new ip), ok (same ip)
Load Average Display back down to 0% when idle.
However, I SHOULD mention that I had several problems initially but it was probably because I had flashed the firmware using the web interface (from 05/16/09) WITHOUT resetting NVRAM to factory defaults. The router locked up after flashing so I reflashed using TFTP but still had some intermittent problems after that. For example, rebooting the router (from the admin screen) or saving and then restoring router config would lock up the router again. Power-cycling the router did not work. I had to do a hard-reset to clear NVRAM each time before I was able to get a DHCP address. Finally, the web interface locked up even though the router was forwarding traffic. SSH'd into router and issued "httpd -h /www" but received a segmentation-fault. I killed the process and power-cycle the router and magically my previous problems disappeared.
Last edited by wandering on Fri May 22, 2009 18:53; edited 1 time in total
Joined: 06 Jun 2006 Posts: 7492 Location: Dresden, Germany
Posted: Mon May 18, 2009 22:49 Post subject:
sterlingh wrote:
BrainSlayer wrote:
since you always have inteferences, packet errors will always happen. thats normal
I understand that Packet Loss is normal, but what I am saying is that it is more consistent when I access the remote rb router. I can have the routers up for 4 hours and no packet loss. Immediately upon accessing the remote rd (through the webgui) I will lose ~20 packets. And there won't be any packet lose for another 4 hours, assuming I don't connect to that router anymore.
whatever you mean with "rb" and "rd". if your router is up you have no packet loss, sure. because no data is flowing and if you connect to it, voila you have data. a typical packet loss is about 5 - 10% since not all packets will survive the long way to you. your mobile uses bluetooth -> inteferences. your 20 neighbors are using wireless too -> more inteferences
this all creates packet loss, its just the question how much. if a packet was not transmitted, it will be repeated. so its not really lost _________________ "So you tried to use the computer and it started smoking? Sounds like a Mac to me.." - Louis Rossmann https://www.youtube.com/watch?v=eL_5YDRWqGE&t=60s
since you always have inteferences, packet errors will always happen. thats normal
I understand that Packet Loss is normal, but what I am saying is that it is more consistent when I access the remote rb router. I can have the routers up for 4 hours and no packet loss. Immediately upon accessing the remote rd (through the webgui) I will lose ~20 packets. And there won't be any packet lose for another 4 hours, assuming I don't connect to that router anymore.
whatever you mean with "rb" and "rd". if your router is up you have no packet loss, sure. because no data is flowing and if you connect to it, voila you have data. a typical packet loss is about 5 - 10% since not all packets will survive the long way to you. your mobile uses bluetooth -> inteferences. your 20 neighbors are using wireless too -> more inteferences
this all creates packet loss, its just the question how much. if a packet was not transmitted, it will be repeated. so its not really lost
rd (typo) == rb == repeating bridge
I just transferred Ubuntu Netbook Remix (~900MB) from my computer which is conncected directly to the Buffalo Access Point (192.168.1.2) to my media center which is connected directly to another WHR-G300N (192.168.1.3) in repeating bridge mode. I did not have any packet errors during the transfer.
I then navigated to 192.168.1.3 (webgui) from the same computer which resulted in about 15 packets being lost (with the understanding that they eventually made it there). Every subsequent page resulted in another ~15 packet errors.
I just noticed that I cannot access the webgui of the AP (192.168.1.2) from the repeating bridge. My media center is connected directly to the repeating bridge. The firewall is off and I am able to access it from wireless devices connected to the wireless router (192.168.1.1). I can, however, connect to the repeating bridge from the AP side of this though...
You should start a new topic with your issue. You may then attract the attention of people with a similar issue.
"Wireless bridging connection problem with v24 preSP2" may be a good title. This topic was focussed on the fact that WPA2 was out of action on the RALINK hardware i.e. WHR-G300N and now appears to be solved.
My unit has now been up for over a day with the 051809 build. Great work guys.
13064: breaks video streaming on my iPhone, otherwise works fine.
12255: Works great with iPhone, but GUI access locks up when connected through Ethernet or for a long period. Timesout on pings when wirless client is far away.
Waiting for a build that supports, iPhone video streaming , any other recommendations?
, any other recommendations?