WS-12-250-DC 1.5.5 - Can't talk to airFiber 11

[mhoppes]

Something is wrong here. I've never had this issue before and I just spoke with someone else who had the exact same issue.

airFiber 11x or airFiber 5x - Doesn't matter what firmware
Netonix WS-12-250-DC - Firmware 1.5.5

Connect to port 1 (although it doesn't seem to matter).
Power up at 48VH.

With the default configuration on both (changing the IP of either one though to .21) from my laptop plugged into any other port I can:

* Manage the switch
* Not talk to the 11x (no ping, no web).
* From the switch I can discover the airFiber and see the MAC and IP address.

Turning Port Isolation ON on only the port connected to the airFiber allows me to talk to it.

Something is wrong here....

[mhoppes]

Anyone?

[Omniflux]

I have not seen this. Is this a new switch that shipped with 1.5.5? If so, it could need the downgrade to 1.5.3 re-upgrade to 1.5.5 fix.

[mhoppes]

Yes it shipped with 1.5.5. Can you explain the downgrade upgrade fix?

[sakita]

Basically just that: Downgrading to 1.5.3 and upgrade back to 1.5.5 seems to correct the VLAN peculiarities:

viewtopic.php?f=17&t=6031&start=10#p32628

[sirhc]

So Matt the default IP of UBNT products is 192.168.1.20 and the default IP of the switch is 192.168.1.20 so there would be a conflict.

Or if there is any other device with an IP conflict strange things occur.

You would want to change the IP of the switch from 192.168.1.20 before you plug in the UBNT product or the UBNT product would need changed before plugin into a Netonix switch to prevent an IP conflict.

The idea of a default IP is to know where it is to start and one should always simply talk to it directly via a laptop to configure the IP before attaching to any network.

Plugging the switch to a network then trying to go to the default IP only works if your 100% sure the default IP is not used by anyone.

When I use a NEW UBNT product or Netonix I first plug into it directly not on network and set up IP info then plug it into network, I never plug it in to the network then try to make changes just as a rule of thumb.

Once a MAC entry is defined in any device that is an IP conflict it has to expire from the table or be manually flushed for things to resume normally.

I guess in hind site I should have made our default IP differnt but I thought all being the same would make life easier if procedure was followed as I was used to default of 192.168.1.20, in hind sight I wish I would have made it 192.168.255.20 or something vastly differnt.

[JustJoe]

In the OP didn't he say:

"With the default configuration on both (changing the IP of either one though to .21) from my laptop plugged into any other port I can ..."

I can understand explanations for new users, but I think Matt has done one or two of these so knows of ..1.20 and arp table behavior :)

[mhoppes]

Yes... it's not an ARP table issue. Today I enabled ISOLATION on Port 1 and I can suddenly talk to the 11x.

Where can I get 1.5.3 to do the downgrade/upgrade fix? Looks like old firmware is removed from the website.

[Stephen]

You can get it here: firmware/archive/wispswitch-1.5.3.bin

Also, check this thread for more information: viewtopic.php?f=17&t=6243