What now?

[cpeterson]

I've had my PS2s for about six months and FINALLY got them working, somewhat, about a month ago. Then a few days ago I decided I needed to set security on them. While attempting to do that I lost my internet connection and then neither antenna would show up with the Discovery Tool. I had to reset both of the antennas in order to see them. That worked fine for the Station antenna (hooked to the wildblue cable), but the Access Point antenna at the other end can still not be seen by the Discovery Tool. It only has one green light lit. I've unplugged and replugged several times, and reset it several times (holding in for less than 10 seconds), and I've tried two different cables. Nothing seems to be working. Is there something I'm forgetting?

[WHT]

No idea what you might have accidentally done. Bring both units back to bench, default them with a full thirty second reset, start from scratch..without any encryption yet.

You need to get back to a known working starting point. Shouldn't take you more than a few minutes to get everything back to normal.

[UBNT-Mike.Ford]

Hello Cpeterson,

Any update?

Thanks,

Mike

[cpeterson]

I spent the entire day yesterday trying to get my antennas up and running. I took them both off the roofs and set them up in the house, then did a factory reset and configured them in the web guii according to the instructions. The lights were all lit and both showed up in the Discovery Tool. So I put them back on their roofs, but only the Station end (connected to wildblue) showed up in the Discovery Tool. Couldn't see the Access Point end in the Discovery Tool and couldn't get online. Here's the thing - when I have the Access Point antenna plugged into the POE, and a cable coming from there to the Linksys router, the LAN light on the antenna goes out and I can't get online. If I unplug the Linksys router, the LAN light on the antenna goes on. When the antennas were working (somewhat) several weeks ago, that was how I had it set up - the Linksys unplugged. I've asked this question several times, but never gotten an answer - do I need a router on the Access Point end???
The other problem I run into is getting IP address conflicts. What I finally had to do to avoid that was set the Station end as a static IP and the Access Point end as DHCP. But then - in trying to get the system up and running I looked at the SSID and there were two with my SSID name. Thinking I maybe had the wrong one checked, I checked the other, then instantly got the IP address conflict message. What am I doing wrong??? Please, please, please would somebody give me some answers. I've had these antennas for six months and have only had intermittent success with them. My husband is taking college courses online and we rely on reliable, fast internet for him to do his homework.

[UBNT-keba]

It would be nice to know firmware version of your antennas? You can see it on System tab.

[cpeterson]

I installed the latest version three weeks ago - can't remember what the number is.

[WHT]

cpeterson...

Give a me a little time and I'll work up a solution for you. Check back here in about an hour. I think I see what your problem is.

[WHT]

Cancel that...my fire pager is going off. Check back tomorrow morning.

[UBNT-Mike.Ford]

Hello,

Can you please post the configuration file from each unit, along with the EXACT firmware version number (the whole string of numbers)

Thanks,

Mike

[CDX825]

I'm going to take a stab at this. My guess is the discovery tool will not locate any units on the other side of anything acting as a router. So if you have the station unit set to router your only going to see it. Your IP issues may also be related to more than one device trying to act as a router. Try pinging an address on the internet with your computer. If you can reach it through ping but not on your browser you have DNS issues also caused by to many device trying to act as a router. Put your power stations in bridge mode and give it a shot. As for the linksys well don't get me started on them :shock: :lol:

[WHT]

OK, let's take this one step at a time.

"there were two with my SSID name."
That is normal. If the STATION has never been associated with an AP, then the Base Station SSID (of said STATION) in the Main tab and the ESSID in the Link Setiup tab will both match the Host Name in the Servcies tab.

Once your STATION associates with an AP, it will inherit the ESSID of the AP and now the AP ESSID in the Main and Link Setup tabs now, and the Host name will still be the original name.

"the Station end (connected to wildblue)"
While it can be down that way, it limits some functionality in some situations. Best to stay with a known topology and use the radio at the internet (WIldblue) end as the AP and the remote radio as Station.

Since you've recently defaulted the radios, you need to get back to a KNOWN WORKING starting point before setting security.
Please review what I posted a month go.
http://forum.ubnt.com/forum/viewtopic.php?t=6337&highlight=

[cpeterson]

I haven't had much time this week to work on the antennas. Tonight I tried to log in and get the config files. The Station end showed up for about 1 minute in the Discovery Tool, then disappeared, and I was not able to log into the web guii after repeated tries, even though I was plugged directly to it. What's happening with that? I don't know what else to do. We reset it twice this week and had the same results every time.
Here's the config file for the Access Point end, which I downloaded earlier in the week:

aaa.1.status=disabled
aaa.status=disabled
bridge.1.devname=br0
bridge.1.fd=1
bridge.1.port.1.devname=eth0
bridge.1.port.1.status=enabled
bridge.1.port.2.devname=ath0
bridge.1.port.2.status=enabled
bridge.1.stp.status=disabled
bridge.status=enabled
dhcpc.1.devname=br0
dhcpc.1.status=disabled
dhcpc.status=disabled
dhcpd.1.status=disabled
dhcpd.status=disabled
ebtables.1.cmd=-t nat -A PREROUTING --in-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.1.status=disabled
ebtables.2.cmd=-t nat -A POSTROUTING --out-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.2.status=disabled
ebtables.3.cmd=-t broute -A BROUTING --protocol 0x888e --in-interface ath0 -j DROP
ebtables.3.status=disabled
ebtables.50.status=disabled
ebtables.51.status=disabled
ebtables.52.status=disabled
ebtables.status=enabled
httpd.port=80
httpd.status=enabled
igmpproxy.status=disabled
iptables.3.status=disabled
iptables.status=disabled
netconf.1.devname=eth0
netconf.1.ip=0.0.0.0
netconf.1.netmask=255.255.255.0
netconf.1.promisc=enabled
netconf.1.status=enabled
netconf.1.up=enabled
netconf.2.allmulti=disabled
netconf.2.devname=ath0
netconf.2.ip=0.0.0.0
netconf.2.netmask=255.255.255.0
netconf.2.status=enabled
netconf.2.up=enabled
netconf.3.autoip.status=enabled
netconf.3.devname=br0
netconf.3.ip=192.168.1.101
netconf.3.netmask=255.255.255.0
netconf.3.status=enabled
netconf.3.up=enabled
netconf.status=enabled
netmode=bridge
ppp.1.password=
ppp.1.status=disabled
ppp.status=disabled
radio.1.ack.auto=disabled
radio.1.acktimeout=48
radio.1.channel=11
radio.1.chanshift=0
radio.1.clksel=0
radio.1.countrycode=840
radio.1.devname=ath0
radio.1.dfs.status=
radio.1.ext_antenna=disabled
radio.1.frag=off
radio.1.ieee_mode=g
radio.1.mcastrate=1M
radio.1.mode=master
radio.1.rate.auto=enabled
radio.1.rate.max=54M
radio.1.rts=off
radio.1.rx_antenna=1
radio.1.rx_antenna_diversity=disabled
radio.1.status=enabled
radio.1.thresh62a=28
radio.1.thresh62b=28
radio.1.thresh62g=28
radio.1.tx_antenna=1
radio.1.tx_antenna_diversity=disabled
radio.1.txpower=16
radio.countrycode=840
radio.ratemodule=ath_rate_minstrel
radio.status=enabled
resolv.nameserver.1.ip=0.0.0.0
resolv.nameserver.1.status=enabled
resolv.nameserver.2.status=disabled
resolv.status=enabled
route.1.devname=br0
route.1.gateway=192.168.1.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
tshaper.status=disabled
users.1.name=ubnt
users.1.password=VvpvCwhccFv6Q
users.1.status=enabled
users.status=enabled
wireless.1.addmtikie=enabled
wireless.1.ap=
wireless.1.authmode=1
wireless.1.autowds=disabled
wireless.1.compression=disabled
wireless.1.devname=ath0
wireless.1.fastframes=enabled
wireless.1.frameburst=enabled
wireless.1.hide_ssid=disabled
wireless.1.l2_isolation=enabled
wireless.1.mac_acl.1.mac=
wireless.1.mac_acl.1.status=disabled
wireless.1.mac_acl.10.mac=
wireless.1.mac_acl.10.status=disabled
wireless.1.mac_acl.11.mac=
wireless.1.mac_acl.11.status=disabled
wireless.1.mac_acl.12.mac=
wireless.1.mac_acl.12.status=disabled
wireless.1.mac_acl.13.mac=
wireless.1.mac_acl.13.status=disabled
wireless.1.mac_acl.14.mac=
wireless.1.mac_acl.14.status=disabled
wireless.1.mac_acl.15.mac=
wireless.1.mac_acl.15.status=disabled
wireless.1.mac_acl.16.mac=
wireless.1.mac_acl.16.status=disabled
wireless.1.mac_acl.2.mac=
wireless.1.mac_acl.2.status=disabled
wireless.1.mac_acl.3.mac=
wireless.1.mac_acl.3.status=disabled
wireless.1.mac_acl.4.mac=
wireless.1.mac_acl.4.status=disabled
wireless.1.mac_acl.5.mac=
wireless.1.mac_acl.5.status=disabled
wireless.1.mac_acl.6.mac=
wireless.1.mac_acl.6.status=disabled
wireless.1.mac_acl.7.mac=
wireless.1.mac_acl.7.status=disabled
wireless.1.mac_acl.8.mac=
wireless.1.mac_acl.8.status=disabled
wireless.1.mac_acl.9.mac=
wireless.1.mac_acl.9.status=disabled
wireless.1.mac_acl.policy=allow
wireless.1.mac_acl.status=disabled
wireless.1.macclone=disabled
wireless.1.scan_list.status=disabled
wireless.1.security.1.key=10293847561029384756102938
wireless.1.security.default_key=1
wireless.1.security=none
wireless.1.signal_led1=94
wireless.1.signal_led2=80
wireless.1.signal_led3=73
wireless.1.signal_led4=65
wireless.1.sper=disabled
wireless.1.ssid=Brady
wireless.1.status=enabled
wireless.1.wds.1.peer=
wireless.1.wds.2.peer=
wireless.1.wds.3.peer=
wireless.1.wds.4.peer=
wireless.1.wds.5.peer=
wireless.1.wds.6.peer=
wireless.1.wds=enabled
wireless.1.wmm=disabled
wireless.1.wmmlevel=-1
wireless.status=enabled
wpasupplicant.device.1.status=disabled
wpasupplicant.status=disabled

[UBNT-keba]

But it is not default cfg

[cpeterson]

I had already changed some of the settings when they asked me to send in the config files. I'm back to having it work on the laptop if I sit on just the right place on the couch. I can pick up the Access Point antenna in the Discovery Tool, but not the antenna on the roof.

[WHT]

I really think you need to get back to a known working starting point. See my above posts as you seem to give conflicting information.

[cpeterson]

The conflicting information comes from the fact that it works sometimes, then it doesn't, then it does, etc., etc. I can do a factory reset on both the antennas, again, but then what should I do?

[WHT]

Oh...no, what I meant was at first you had the NS at the Wild Blue end as an AP, then you made it as a Station.

[cpeterson]

That was my mistake. If I recall correctly, I originally had the wildblue end set as the AP and other end set as the station. When I did the factory reset I inadvertently switched them. Now I've switched them back.

So what's next????

[WHT]

From http://forum.ubnt.com/forum/viewtopic.php?t=6337&highlight=

Wildblue -> Linksys -> PS#1 ~> PS#2 -> computer

Lets narrow the scope of the issue.

1) Wildblue -> computer set for DHCP and server DNS. Try surfing.
Run ipconfig /all and you should see something like:

Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.252.57.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . : 10.252.57.1
DHCP Server . . . . . . . . . . . : 10.233.40.14
DNS Servers . . . . . . . . . . . : 75.104.128.61


2) Wildblue -> WAN side of Linksys -> LAN side of Linksys -> PC
WAN side of Linksys set for: DHCP. [Edited Jan 6 to include "of Linksys"]
LAN side of Linksys set: [Edited Jan 6 to include "of Linksys"]
IP addy: 192.168.1.1
Subnet: 255.255.255.0
Gateway: 192.168.1.1
DNS: 208.67.222.222 and 208.67.220.220 (free DNS servers)

Computer set to DHCP and server assigned DNS.
Run ipconfig /all and you should see something like:

Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.1.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.1.1
DHCP Server . . . . . . . . . . . : 192.168.1.1
DNS Servers . . . . . . . . . . . : 208.67.222.222 and 208.67.220.220


At this point you should be able to surf from you PC.

3) Wildblue -> WAN side of Linksys -> LAN side of Linksys -> PS #1
If yer PS #1 is still set to[/i]192.168.1.20 [i][EDITED Jan 6 for the corrected IP address], you should be able to ping it from the PC, or you can see it with the Discovery tool.
Now unplug the PS #1 and plug in PS #2, its prolly at 192.168.1.21 (if you've already changed it to Station and new IP), you should be able to ping it from the PC, or you can see it with the Discovery tool.

4) Wildblue -> WAN side of Linksys -> LAN side of Linksys -> PS #1 ~> PS #2 -> PC
You should be able to ping the Linksys at 1.1, PS#1 at 1.20, and PS #2 at 1.21.
If that all works, try a ping to 206.190.60.37 that is the IP for yahoo.com. You should get some replies - this means you're connect to the internet.
Now try a ping to yahoo.com, and you should get a reply - if you don't, you have a DNS number or setting wrong.

5) Now as for the Laptops on the couch....They are picking up either the signal from the PS #1 (which may be too far away) or PS #2 (which may be shooting over or away from the couch.