Setting Static IP on Meru

[marekbrad]

Hi Guys

There maybe a simple solution to this but ... I am having a weird issue with our Meru setup and before I go back to Meru I thought I'd ask here.

I am trying to set a static IP on a wireless client, however once the static is set the client can no longer access the internet/resources etc..

I have checked that the ip is free and all other settings are correct, In fact if i set the same static IP on a wired client all is good and happy in the world.

I can only assume therefore it is something in the Meru setup that will not allow statics?

Anyone any the wiser

Cheers

Mark

[psydii]

I'll look at this another way... can you not set the client to DHCP and a reservation for it in the DHCP scope to eliminate the problem?

[marekbrad]

@psydii true indeed sir .. and that is indeed what I shall be doing .. but the problem still remains and I was hoping someone would be able to shed some light

[lelsbecker]

We've had the same issue for well over a year and were told the latest firmware would fix that. We've been told that several times. I have been setting DHCP reservations and that works but it's more management that we shouldn't have to do.

[twin--turbo]

Works fine here?

Is the subnet / vlan correct ?

Rob

[lelsbecker]

Yes. We've tried on several different subnets, vlans, different campuses, same thing on all. Meru has identified this as an issue just haven't fixed it. We had an engineer on site who saw the same thing and had no answer.

[SuperfluousAdjective]

I would check to see if the wireless NIC has a driver update. I'd also run a packet tracer. Depending on your Meru configuration it will not beacon itself until the client announces itself. And when it does beacon it will send out a unique MAC address/wifi network for the individual client. Your host device may not be passing the traffic needed to get a response/connection from the Meru system. I'm sure one of their engineers can assist you best, but dealing with these inconsistencies is part of the deal when going with a single channel system that breaks away from the wireless protocol standards.

[SuperfluousAdjective]

What device, wireless nic, nic driver version are you using? Have you run a packet tracer to monitor the authentication process if there is one?

[mhowell]

Marekbrad,
Feel free to contact me directly mhowell@merunetworks.com and we'll have a look at whats going on, just send me your full contact details and some brief details.
For the record single channel solutions do not break away from any wireless protocol standards.

[twin--turbo]

Can I contact you on other issues, thoughts, Ideas..

The suppot guys are gr8 but a UK contact to pop q's at would be gr8.

Chrs

Rob

[mhowell]

Of course, feel free, thats what we're here for and I'd love to know which of the Carlisle customers you are of ours! There's quite a group of you up there (compared to Cambridge that is) so there'll always be local schools to sound ideas off too.
Thx
Mak

[SuperfluousAdjective]

For the record single channel solutions do not break away from any wireless protocol standards.

Single channel networks do not comply with the expectations of the 802.11 protocols and client devices. The changes that Meru makes to enhance their single channel product makes it an unpredictable environment for drivers/clients creating connectivity/authentication issues that would not exist on other networks. Because of this it also makes troubleshooting more difficult. This is well documented throughout the field.