Posted: Sat Jun 20, 2009 10:49 Post subject: PS5 commercial use
Hi all
I bought 4 PS5 (2*EXT + 2*22V) to build 2 links for 2* about ~20 customers. At the end of the 5GHz link I think I'll use 2.4GHz hw to send Internet to final customers (NS2 or wrt54gl)
I'd like to have advises about DD-WRT:
1) Benefits of dd-wrt against of stock 3.3 AirOS or free 3.4 upgrade.
2) Which release of dd-wrt?
3) benefit of superchannel option? I searched google to find if that is a specific commercial dd-wrt feature or a generic name but didn't find something clear.
4) Should I flash from AirOS-3.3.2 to AirOS-3.4 before I flash to dd-wrt?
3) benefit of superchannel option? I searched google to find if that is a specific commercial dd-wrt feature or a generic name but didn't find something clear.
unused channels.no noise. but illegal in the EU
Quote:
4) Should I flash from AirOS-3.3.2 to AirOS-3.4 before I flash to dd-wrt?
Thanks Sash.
What is the outdoor band option (the "more" help link won't work in the demo)?
thats a reg dom etsi/fcc thing....just google
Bib wrote:
Is there support for the licenced ddwrt in PS5... I mean more support than the one above?
what do u mean with support?
im not here to teach dd-wrt. that something anybody must learn by himself. im just helping on bugs or real problems....atm i'm losing my time in level1 problems which makes me not amused....which u can see on my posts... _________________ Forum Guidelines...How to get help
&
Forum Rules
&
RTFM/STFW
&
Throw some buzzwords into the WIKI search
_________________
I'm NOT rude, just offer pure facts!
_________________
Atheros (TP-Link & Clones, etc ) debrick service in EU
_________________
Guide on HowTo be Safe, Secure and Protect Your Online Anonymity!
I can understand.
I tested this day AirOS-3.4 and it seems to everything I need to build my long link: AP-wds at one end and Station wds bridge on the other with WPA2 and port forward.
As the dd-wrt demo cannot simulate that, I know I could try the 24h trial, but to spare myself unuseful flash + time to test (and eventually backflash), if you tell me this config works with ddwrt on PS5, I'll be glad to spend my 80€ for 4*PS5 licences just for the happiness to support DD-WRT with some money because I already use several tens of free builds.
I reached to flash the trial version on 2 of my PS5. After fighting with google and the wiki and the 29 answers for wds on the ddwrt Ubiquity forum, 17 hours remaining
Is it possible to have the wdsSTA assigned an IP by the wdsAP DHCPserver?
When I enabled the WAN connexion type to DHCP on the wdsSTA I was locked out the PS5: no ethernet access, no wireless access from the wdsAP (the wl link was OK but no client were listed). So I reset the wdsSTA, resetup again, but this time I used extra settings that are not in the dedicated WDS Ubiquity wiki:
Quote:
* Only set the ap to "wds ap" and the clients to "wds station". Put all on the same SSID.
I did (easy). Done with the "Join button", then changed Client -> WDS Station (had to change the strange wl net mode from mixed to A only (this is a PS5 not a 2 wl buff)
Quote:
Now set your prefered wireless encryption.
I did (WPA2-PSK AES only) (easy too)
Quote:
Don´t set the wds mac table! This always causes trouble so stay away from it.
I did ...(not)
Quote:
* WDS between different chip vendors (atheros, broadcom, ralink) will not work since its INCOMPATIBLE and no we will NOT fix it
I hope both the PS5 have the same chip
Quote:
* WDS-Sta will not work as AP simultaneously. This is not possible @ atheros
I don't understand that... maybe it's about virtual AP?
Extra settings I tried (from various pages)
wdsAP WAN type: DHCP (from my FAI dsl modem dhcp server 192.168.222.254 in my 192.168.222.0/24 LAN)
wdsAP LAN: 192.168.0.1/24 GW & DNS left blank
wdsSTA WAN type: Disabled
wdsSTA LAN: 192.168.0.2/24
wdsSTA GW: 192.168.0.1 DNS left blank
wdsSTA DHCP server: Disabled and DNSMasq for DHCP too. Just left enabled DNSMasq for DNS.
I didn't applied things about the netmask /30 I read because it't irrelevant (192.168.222.0/24 and 192.168.0.0/24 have nothing overlapping)
Why both WAN leds blink ~1Hz?
Why does the upper bargraph led (signal strength) blinks ~1Hz and sometimes ~2Hz?
Why does the wl link sometimes breaks (~30dB SNR)? I need to reassociate to bring it up (seems with no wl secu it's stable, whatever Sach you're saying! How did you get your own link working with WPA2?
Is it possible to have the wdsSTA assigned an IP by the wdsAP DHCPserver like AirOS does? I hoped ddwrt would be better than AirOS here, allowing DHCP reservation for the wdsSTA? I just can't access the STA config from the wdsAP wan side for remote mgmt purposes.
If the issues can't be solved (at least WPA2 and remote mgmt), I'll keep AirOS for the long link.
Maybe the Ubiquity is not a good recommended solution for use with ddwrt i such a aim, doing a long link as bridge then spread the Internet with another classic AP to classic client routers?
Thanks anybody for help, I get only 15 hours of remaining trial.
In the end my trail DL did expire and I didn't reached having my test positive. Anyway I buy now the 4 more licences to go on testing, whatever if I can use ddwrt on these devices or not. See that as if I do a donation for free releases.
Maybe there is something else broken in trial release (like telnet not working)...why not?
* WDS-Sta will not work as AP simultaneously. This is not possible @ atheros
I don't understand that... maybe it's about virtual AP?
no. broadcom wds can do wds and ap simultaniously. for atheros u must do vap
Quote:
Extra settings I tried (from various pages)
wdsAP WAN type: DHCP (from my FAI dsl modem dhcp server 192.168.222.254 in my 192.168.222.0/24 LAN)
wdsAP LAN: 192.168.0.1/24 GW & DNS left blank
wdsSTA WAN type: Disabled
wdsSTA LAN: 192.168.0.2/24
wdsSTA GW: 192.168.0.1 DNS left blank
wdsSTA DHCP server: Disabled and DNSMasq for DHCP too. Just left enabled DNSMasq for DNS.
I didn't applied things about the netmask /30 I read because it't irrelevant (192.168.222.0/24 and 192.168.0.0/24 have nothing overlapping)
Why both WAN leds blink ~1Hz?
Why does the upper bargraph led (signal strength) blinks ~1Hz and sometimes ~2Hz?
Why does the wl link sometimes breaks (~30dB SNR)? I need to reassociate to bring it up (seems with no wl secu it's stable, whatever Sach you're saying! How did you get your own link working with WPA2?
Is it possible to have the wdsSTA assigned an IP by the wdsAP DHCPserver like AirOS does? I hoped ddwrt would be better than AirOS here, allowing DHCP reservation for the wdsSTA? I just can't access the STA config from the wdsAP wan side for remote mgmt purposes.
If the issues can't be solved (at least WPA2 and remote mgmt), I'll keep AirOS for the long link.
Maybe the Ubiquity is not a good recommended solution for use with ddwrt i such a aim, doing a long link as bridge then spread the Internet with another classic AP to classic client routers?
Thanks anybody for help, I get only 15 hours of remaining trial.
the dws-sta cant get dhcp leases. only fixed ones. for dhcp u MUST use client-mode or a 2nd device behind the wds-sta that gets the ip.
btw after trial u can reset to defaults and start again....
Too late: I activated (in fact I beleived -but not sure- I could reset the trial counter as I saw in my tests when did a reset with the button.
But too much borring to rerereset all parameters.... ooops I forgot the backup feature... but maybe disabled in trial version? But don't care,
1 activation is "only" 4 days of cigarettes for me (2 when testing dd-wrt ).
Here is the art (binary).
It seems there are no more link break (with WPA2psk-aes) now that devices are activated (don't want to flash back - but maybe if the weather
and the moon are fine with me one of these days, I'll check again with my 2 remaining unflashed devices).
Further more, now the STA appears some times in wireless status as a client (not specified as wds, but maybe this is normal wdsAP behaviour).
Before it did not and I couldn't even ping the devices from each other. Now I can.
I try disabling wds/conn watchdog to see if the link remains OK.
Now I notice that the wdsSTA is 2 hours behind the AP... grrrrr this brings back to my mind a bad chat I had with u Sash about NS2 (classic) clients. But they did even get NTP time at all.
