Is there a way to stop FLM taking over as DNS provider for my wired network?

by jasonp on

I have reset the FLM's wired and wifi network addresses to 10.10.0.4 (wifi) and 10.10.0.5 (wired) so it I can access it from my 10.10.0.*/24 home network.

BUT my wifes PC started using the FLM as it DNS provider. After I turned my PC on this morning it also grabbed the FLM as it's DNS provider. I have noe hardcoded my PC and wifey's PC to use my router as the DNS provider, but was wondering if there is a way to get around this?

My have adjusted the network settings to (bold are the new settings):
Local Network
IPv4-Address: 10.10.0.5
IPv4-Netmask: 255.255.255.0
IPv4-Gateway (optional): 10.10.0.1
DNS-Server (optional): 10.10.0.1
Internet Connection
Protocol: manual
IPv4-Address: 10.10.0.5
IPv4-Netmask: 255.255.255.0
IPv4-Gateway (optional): 10.10.0.1
DNS-Server (optional): 10.10.0.1
Clamp Segment Size: unchecked.

I have the FLM operating in wifi mode.

Should I be expecting any more dramas or is there something else I can do to ensure that the FLM is not acting as a DNS provider? Does it need to be a DNS provider now that it is on my network.

Thanks all. Apologies for being a pain :-(

‹ No FLM2 data being logged! Heartbeat good. Devices and sensors registering. re-install firmware ›
icarus75's picture
icarus75 |

When using the FLM in wifi mode, the ethernet port will indeed be running a DHCP server. When the FLM is toggled to ethernet mode, the eth port will be configured as a DHCP client instead. You're then able to access the local web interface via ethernet as well. You just have to find out the IP address that's been allocated to your FLM.

jasonp's picture
jasonp |

Aaaah. I see.

As soon as I've got my setup dramas sorted out I will pick either wifi or ethernet, rather than have both connected as I do now.

Thanks,
JasonP