cant access ns2 and no ping

[qmax]

this is my scenario

server nat--PC--switch--APsmartbridge----NS2---cable---AP aphelion---NS2 (have 3 ns2)

i cant ping or access web gui From my pc to the NS2 behind the Ap aphelion
I CAN ping the first NS2 and the aphelion
All network are in the same subnet
all NS are in station mode
the AP smartbridge is very transparent bridge
all equipment have the same gateway
but all NS2 can ping to the nat server


any idea ??

[UBNT-Mike.Ford]

this is my scenario

server nat--PC--switch--APsmartbridge----NS2---cable---AP aphelion---NS2 (have 3 ns2)

i cant ping or access web gui From my pc to the NS2 behind the Ap aphelion
I CAN ping the first NS2 and the aphelion
All network are in the same subnet
all NS are in station mode
the AP smartbridge is very transparent bridge
all equipment have the same gateway
but all NS2 can ping to the nat server


any idea ??


Hello,

Please post your configuration files for both units.

Thanks,

[qmax]

Sorry for respond too late

this is the configuration file from the First nano (can ping and acces)
XS2.ar2316.v3.5-rc.4448.090910.1708

the other one i cant get acces so i cant get the config file , but is a simple station whit router enable the wan interface have 192.168.2.101/24 gw is 192.168.2.1

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=enabled
bridge.status=enabled
dhcpc.1.devname=br0
dhcpc.1.status=disabled
dhcpc.status=disabled
dhcpd.1.status=disabled
dhcpd.status=disabled
dnsmasq.1.devname=eth0
dnsmasq.1.status=enabled
dnsmasq.status=disabled
ebtables.1.cmd=-t nat -A PREROUTING --in-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.1.status=enabled
ebtables.2.cmd=-t nat -A POSTROUTING --out-interface ath0 -j arpnat --arpnat-target ACCEPT
ebtables.2.status=enabled
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.alias.1.status=disabled
netconf.1.alias.2.status=disabled
netconf.1.alias.3.status=disabled
netconf.1.alias.4.status=disabled
netconf.1.alias.5.status=disabled
netconf.1.alias.6.status=disabled
netconf.1.alias.7.status=disabled
netconf.1.alias.8.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.alias.1.status=disabled
netconf.2.alias.2.status=disabled
netconf.2.alias.3.status=disabled
netconf.2.alias.4.status=disabled
netconf.2.alias.5.status=disabled
netconf.2.alias.6.status=disabled
netconf.2.alias.7.status=disabled
netconf.2.alias.8.status=disabled
netconf.2.allmulti=enabled
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=disabled
netconf.3.devname=br0
netconf.3.ip=192.168.2.24
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
pwdog.delay=300
pwdog.host=192.168.2.1
pwdog.period=300
pwdog.retry=3
pwdog.status=enabled
radio.1.ack.auto=enabled
radio.1.ackdistance=4050
radio.1.acktimeout=70
radio.1.ani.status=enabled
radio.1.chanshift=0
radio.1.clksel=0
radio.1.countrycode=840
radio.1.devname=ath0
radio.1.dfs.status=
radio.1.ext_antenna=enabled
radio.1.frag=off
radio.1.ieee_mode=b
radio.1.mcastrate=11M
radio.1.mode=managed
radio.1.rate.auto=enabled
radio.1.rate.max=11M
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=209.13.172.3
resolv.nameserver.1.status=enabled
resolv.nameserver.2.status=disabled
resolv.status=enabled
route.1.devname=br0
route.1.gateway=192.168.2.1
route.1.ip=0.0.0.0
route.1.netmask=0
route.1.status=enabled
route.status=enabled
sshd.port=22
sshd.status=enabled
tshaper.status=disabled
users.1.name=admin
users.1.password=OoGVzQ8eBxpZ2
users.1.status=enabled
users.status=enabled
wireless.1.addmtikie=enabled
wireless.1.ap=
wireless.1.authmode=1
wireless.1.compression=0
wireless.1.devname=ath0
wireless.1.fastframes=0
wireless.1.frameburst=0
wireless.1.hide_ssid=disabled
wireless.1.l2_isolation=enabled
wireless.1.macclone=disabled
wireless.1.scan_list.status=disabled
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=COSTELHO
wireless.1.status=enabled
wireless.1.wds=disabled
wireless.1.wmm=disabled
wireless.1.wmmlevel=-1
wireless.status=enabled
wpasupplicant.device.1.status=disabled
wpasupplicant.status=disabled

[UBNT-Mike.Ford]

Hello,

Please disable client isolation at the AP and test again.

Thanks,

[qmax]

Hi Mike thks for response , do you say in the SmartBridge AP ? or in the Aphelion ?

[UBNT-Mike.Ford]

Hello,

Please disable this in all of the AP's.

Thanks,

[qmax]

Dear Mike, I have already disable the client isolation but still can not work , does the nano2 make a nat mac addresses translation in the bridge mode? perhaps this is the problem because if I ask the client to ping to my PC then begins to respond also.

reggards

[UBNT-Mike.Ford]

Dear Mike, I have already disable the client isolation but still can not work , does the nano2 make a nat mac addresses translation in the bridge mode? perhaps this is the problem because if I ask the client to ping to my PC then begins to respond also.

reggards

Hello,

It will not create a NAT translation unless you check the "Nat" box. If you still cannot access the unit i would recommend resetting to defaults and setting the unit back up again.

Thanks,

Mike

[qmax]

Dear Mike:

I understand what you say, but in bridge mode this option is not available (nat), I refer to a translation at layer 2 , no IP, if I perform the command arp-an in the first pc or at the server take a look the result which gives me

"? (192.168.2.24) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.46) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.49) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.55) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.62) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.91) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.93) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.97) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.101) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.144) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.190) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.206) at 00:15:6d:d6:64:c2 on vr0 [ethernet]


so I understand that the NanoStation performs a "mac address" translation when it is configured as station-bridge

but i cant understand why i can ping from the server to the nanostation(192.168.2.101) behind the station-bridge(192.168.2.24) but i cant ping from my pc to teh client(192.168.2.101)


Reggars

Sorry for my english I'm learning

[UBNT-Mike.Ford]

Dear Mike:

I understand what you say, but in bridge mode this option is not available (nat), I refer to a translation at layer 2 , no IP, if I perform the command arp-an in the first pc or at the server take a look the result which gives me

"? (192.168.2.24) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.46) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.49) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.55) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.62) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.91) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.93) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.97) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.101) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.144) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.190) at 00:15:6d:d6:64:c2 on vr0 [ethernet]
? (192.168.2.206) at 00:15:6d:d6:64:c2 on vr0 [ethernet]


so I understand that the NanoStation performs a "mac address" translation when it is configured as station-bridge

but i cant understand why i can ping from the server to the nanostation(192.168.2.101) behind the station-bridge(192.168.2.24) but i cant ping from my pc to teh client(192.168.2.101)


Reggars

Sorry for my english I'm learning

Hello,

Is your PC firewall blocking ICMP ping requests?

Thanks,

Mike

[qmax]

Dear Mike , of course not , i can get ping to another devices behind the AP-aphelion

[UBNT-Mike.Ford]

Dear Mike , of course not , i can get ping to another devices behind the AP-aphelion

Hello,

Can you verify that the gateway of the Nano is not incorrect?

Thanks,

Mike

[qmax]

dear mike , all devices had the same gateway , 192.168.2.1 , that is the first server

[UBNT-Mike.Ford]

Hello,

Can you get us SSH access into the problem unit?

Thanks,

Mike