Device lock/unlock on the network through DNS monitoring.
-
Hi everyone!
I need to lock/unlock a device on my LAN through DNS monitoring 1.1.1.1 or 8.8.8.8 for exemple.
The case: I have a device that should only have access to the LAN if the internet connection is lost. But when the connection in on, the device will can't to connect to the LAN.
Anyone can help me?
-
Pfsense doesn't control access of a device on the lan to other devices on the same lan. Is this device on different vlan than actual "lan"?
Also just out of pure curiosity - why would anyone want to do this? Do you mind sharing the use case of why you would want to prevent access to local resources if internet works, but if internet down allow?
-
I need this as I have a Dedicated EFT that works via satellite by default via a network route. But when the satellite connection is lost, the TEF starts working via the internet through a virtual machine.
But I want it to work the other way around: the satellite connection device should only enter the network if the internet goes down.
-
@felipesmith said in Device lock/unlock on the network through DNS monitoring.:
EFT
Ok your going to have to be a bit more explicit here.. EFT? This not networking or device acronym familiar with. Electronic funds transfer is first thing that comes to mind here..
And then did you typo it with TEF?
If you could explain how you have it working now.. And what network its on.. How exactly is it connected to the network, and where is the is VM machine it uses to get to the internet?
Do you have a model number of this device? etc.
-
How litteraly should the "not allowed on lan" be taken ?
1:
If really litteraly , you could acheive the "allowed on lan" via an "intelligent snmp write capable switch" and have the switchport in shutdown state , until the condition arises , where you then send a snmp comand to open the switchport interface.
1.a:
This will still require some pfSense magic , to switch the default gateway, from the "landline gw" to the "sat gw"2:
Leave both "gw's" turned on , and control the dataflow via pfSense routes , and some "ping magic"
.... See 1.a@johnpoz
Would know more abut the 1.a pfSense stuff/Bingo
