Posted: Fri Sep 19, 2008 22:20 Post subject: NS2 as AP and primary router
Strange issue: the throughput is very poor when the single port is used for WAN. The conf is
1)WAN dhcp client(no stp), it receives 192.168.2.3 (reserved)
2)Router local ip 192.168.3.1/24 and has to run as Auth dhcp itself for 3.100->149
3)WAN port is assigned eth0
4)ath0 is unbridged 3.1/24
So LAN mac is 00:00:00:00:00:00 and WAN & WLAN are different.
I tried bridged, but it's the same.(but lan mac=wlan and still different from WAN), very long and poor throuhtput.
pings issued from diags.asp (3.1 I presume) to 2.3 are veeeeeryyyy looonnnngggg:
PING 192.168.2.3 (192.168.2.3): 56 data bytes
64 bytes from 192.168.2.3: seq=0 ttl=64 time=50.177 ms
64 bytes from 192.168.2.3: seq=1 ttl=64 time=15.358 ms
64 bytes from 192.168.2.3: seq=2 ttl=64 time=36.241 ms
--- 192.168.2.3 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 15.358/33.925/50.177 ms
ping 127.0.0.1 are the same
Any idea of what I missed?
PS: I manage the beast from the WAN side.
Thanks for help _________________ ): FoReVeR nEwB
Posted: Mon Sep 22, 2008 6:52 Post subject: Re: NS2 as AP and primary router
Bib wrote:
Strange issue: the throughput is very poor when the single port is used for WAN. The conf is
1)WAN dhcp client(no stp), it receives 192.168.2.3 (reserved)
2)Router local ip 192.168.3.1/24 and has to run as Auth dhcp itself for 3.100->149
3)WAN port is assigned eth0
4)ath0 is unbridged 3.1/24
So LAN mac is 00:00:00:00:00:00 and WAN & WLAN are different.
wan asignment AND unbridged wlan?just do one thing at the same time. plz rebridge the wlan.
set the ns to a static ip. maybe enable stp.
Quote:
I tried bridged, but it's the same.(but lan mac=wlan and still different from WAN)
this is correct
Quote:
, very long and poor throuhtput.
pings issued from diags.asp (3.1 I presume) to 2.3 are veeeeeryyyy looonnnngggg:
PING 192.168.2.3 (192.168.2.3): 56 data bytes
64 bytes from 192.168.2.3: seq=0 ttl=64 time=50.177 ms
64 bytes from 192.168.2.3: seq=1 ttl=64 time=15.358 ms
64 bytes from 192.168.2.3: seq=2 ttl=64 time=36.241 ms
--- 192.168.2.3 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 15.358/33.925/50.177 ms
ping 127.0.0.1 are the same
Any idea of what I missed?
PS: I manage the beast from the WAN side.
Thanks for help
Posted: Mon Sep 22, 2008 15:22 Post subject: Re: NS2 as AP and primary router
Sash wrote:
i think the problems are the wlan settings at your ap and ns. give us screenshots of them
THanks fo reply Sash. I think there is misunderstand: there is a single device (the AP is the NS2: one single NS2 as {AP & router} should be the title ). I lost the device trying with bridges and vlans and tags... I have to go to the site to recover it. _________________ ): FoReVeR nEwB
Ok, I'll give snaps in the beginning of the afternoon. The pings above were issued from the NS2 GUI itself, which was itself very long to open from WAN side. At wlan side, there are (trying unsuccessfully to connect as clients since I enabled wan as dhcp client at .../Setup.asp and/or unbridged wlan) another NS2 and my Asus eeepc. Before that they could connect, so no problem with wlan settings but maybe the [un]bridge one at the bottom of .../Wireless_Basic.asp. _________________ ): FoReVeR nEwB
Sorry for the delay Sash, I could not make the snaps on the site, so I replaced the NS2 with a wrt54gl1.1 and it works OK now. I will try to reproduce the issue at home and post the snaps. _________________ ): FoReVeR nEwB
I reset the NS2 to fw defaults. It works OK for it's own wireless clients (they are assigned IP address by a buffalo gateway lan-wired to the NS2 RJ45 port), but I don't know how to manage the NS2 settings from a pc wired to the buffalo lan, as the NS2 WAN is disabled. I must unplug the ns2 out of the buff and plug it into a pc to access settings.
Now I set a static IP to WAN, and I can't no more connect to the ns2 wirelessly, nor the clients access the web. A look at networking.asp shows WAN port assignment disabled. Maybe here was my mistake: I set it the other day to eth0 which I thought to be the RJ45(ethernet) when ath0 would be atheros wireless interface. Please can you confirm this was the error Sash? _________________ ): FoReVeR nEwB
I searched the forum, and found eth0 seems to be what I thought, so I retried assigning WAN to eth0 and now it works smoothly (either from a wl pc client or directly from the wired wan side or the buff's wan through a nat rule), even with the ns2 WAN set at dhcp client (reserved in the buff). I really don't understand what append. I check further with adding an other ns2 as client of the first (2 wl clients). All that with no STP. _________________ ): FoReVeR nEwB
No more problems @ home even with an other ns2 added as wl client of the 1st one.
Sorry for disturbing you Sash.
Maybe I met the "hidden node problem", or was it because the ns2 AP was just beside a strong shouting SD19 (although on a very different channel) that would have produce EMC issues inside the wired interface of the ns2. _________________ ): FoReVeR nEwB
