The Shop > CNC

Stopping a PC accessing the Internet ?

<< < (3/7) > >>

NeoTech:
Easiest way of having the ethernet controller not bleeding into your routed network is to run it in its own network.

192.168.1. is the common routed network. But the uncommon one that is open for use is 10.10.10.  and if it sits in a completely different network with a 255.255.255.0 netmask and a 10 series broadcast adress it will not bleed into your other network.

hanermo:
Stve post # 14 has the answer.

If You donīt have a gateway defined, the PC will not be able to access the internet.
Just leave it blank.

Also, you can be on many subnets at the same time.
Your CNC machine can be on say 10.10.1.0 - network address, and your PCs on another.

If your primary IP address is on the non-internet connected one, even the more clever programs wont be able to use it.

Do this:
/cp/network/properties/add ip address
e.g. 192.168.1.254 as a secondary ip to your plasma PC.
It will then see network shares, and can share files, but wont be able to access the internet.
The solution is perfectly safe.

Some rare mac-based stuff like auto-finding printers/pokeys autoconfig/csmio-ip-s autoconfig did not work, in the past, with 2 ip addresses.
I donīt know if they have fixed these bugs.

awemawson:
There isn't a post #14  yet - do you mean post #6 :scratch:

Yes but see post #8 above  :scratch:

BTW my actual gateway / router is 192.168.1.254 so probably not a good idea to add it it to the Plasma PC - but I assume you mean an address in the 192.168.1.XXX rather than that specific one ?

Can't do much testing at the moment as the specific PC is being mechanically embodied in the plasma table at the moment.

stvy:
Andrew,

If your PC still got off of its local network and out on to the internet then it must have still had the gateway set. No question. If you take out the gateway and have that applied it cannot get out.

If you are getting your IP via a DHCP server then you are going to constantly get a gateway after every renewal if that is specified within the scope of the DHCP servers configuration. One way around this is to set this PC up with a static. If it is always connected and on there is no risk that the DHCP server will issue that same address out to another DHCP client. A correctly implemented DHCP client and server protocol involves the server first checking if an IP is free before issuing it.

You can be sure if a gateway is configured in windows using the command (run the "cmd" program) and type:

# route PRINT

if you have a gateway in place this will list it.

You can double check the running settings of the network with

# ipconfig /all

and you can see the entries.


If you do have some software that still finds its way on to the internet then this software is not written following the standards. Some software will discover a gateway by trying every valid address on a network until it succeeds and cache it. If you have something doing things like that then uninstall it from a PC that is dedicated to this type of work as you can not guarantee any behaviour with it.


Pete,

127.0.0.1 is a special IP address. It means the localhost. You should not put that as the gateway. Best practice is if you don't want a gateway set don't set one. Having an empty field is perfectly acceptable.






Regards,
Steve
 

Pete.:

--- Quote from: stvy on December 08, 2016, 06:43:25 PM ---Pete,

127.0.0.1 is a special IP address. It means the localhost. You should not put that as the gateway. Best practice is if you don't want a gateway set don't set one. Having an empty field is perfectly acceptable.

Regards,
Steve
 
--- End quote ---

I think you might have to disable upnp or something to stop the gateway being discovered if the field is left blank.

Navigation

[0] Message Index

[#] Next page

[*] Previous page