topic Re: Force Static IP in Wireless

Force Static IP

Asavoy — Wed, 13 Nov 2019 21:55:27 GMT

Anybody have any idea how to force my MR34s to use the static IP that has been set on them?

The amount of "bad IP/bad DNS", when there's no underlying issue, is getting pretty ridiculous these days.

Re: Force Static IP

Nolan H. — Wed, 13 Nov 2019 22:13:03 GMT

I don't have any bad IP/bad DNS issues, and I've got lots of sites and been around a while. It sounds like an underlying issue that has nothing to do with the AP having a static or dynamic IP.

I will say that the static IP is a pain to deal with and as long as they get any IP to get Internet, it shouldn't matter.

However if you insist, you can either configure it yourself on the AP page by clicking on the pencil icon, or go to your DHCP server and set reservations for the AP mac addresses.

Re: Force Static IP

Nash — Wed, 13 Nov 2019 22:24:39 GMT

How's your switchports configured? Trunk vs. access? What's your vlan situation?

If you connect another device, with the AP's static IP configured, to that AP's switchport, what happens? Can you ping gw? Can you talk out?

Re: Force Static IP

BlakeRichardson — Wed, 13 Nov 2019 22:36:16 GMT

@Asavoy I've had this issue in the past with a couple of switches. Can you provide some screenshots of the settings so we can have a closer look.

Re: Force Static IP

Asavoy — Wed, 13 Nov 2019 22:42:08 GMT

@Nolan Herring Oh, they're set in that section of the individual setup page! I had an problem with an AT&T supplied switch that caused issues with my DHCP/DNS for a few sites. It was a MetroLan mesh network with MS320s at the edge of each site relaying DHCP to a Windows server. Long story short, reservations that had existed before me were failing, so I had to change some devices to static IP and remove the reservations. Worked fine for devices like network printers and computers, but the MR34s refused to accept or use their static settings.

I recently switched to a new mesh and equipment, still using the MS320s at the sites, and still have multiple random 'bad ip assignment' or 'bad DNS' for no discernible reason. Some will be fine for 3+ days and then just decide 'whatever dude, here's a message'. Could be a single one at 4am, or multiple, or varying times between 80% at one site. If it was all WAPs attached to a specific switch, somewhere along the line, doing it at the same time, at least I'd know what the heck to trace. But this? Quite aggravating, really.

Re: Force Static IP

Asavoy — Wed, 13 Nov 2019 22:57:42 GMT

@Nash- I eliminated every single trunk port in my networks except at the edge uplinks. Each site utilizes 1 VLAN on the interior, and 1 VLAN on the exterior- no tagging. 90% of the traffic is wireless, with no VOIP or anything else substantial, so no point to over-complicate it. It's a mix of two point-to-point sites and three in a mesh, all connecting to a single switch before control is handed off to the county network. Sites are on separate scopes via the Windows server and the MS320s.

Re: Force Static IP

Asavoy — Wed, 13 Nov 2019 22:59:47 GMT

@BlakeRichardson Screenshots of the overall picture of the WAPs, and then a specific WAP or two?

Re: Force Static IP

ww^ — Wed, 13 Nov 2019 23:01:21 GMT

set ip in native vlan. make sure the vlan field on the ap is empty

Re: Force Static IP

Asavoy — Wed, 13 Nov 2019 23:39:50 GMT

@jdb1

Interesting! I just compared two WAPs in the same building, one had VLAN specified and one didn't. So, removed VLAN from the one, reboot, and presto.

Re: Force Static IP

PacerX — Mon, 13 Apr 2020 16:49:19 GMT

This helped me also thanks @jdb1