It's less elegant, but it may be adequate for your situation. This allows you to connect using the external IP address when on the internal network, and still get a correctly routed connection. I'd recommend looking at pfSense or some other form of router/gateway firmware which makes it a whole lot easier.Īs an alternative, see if you router/gateway supports a feature called "NAT-reflection". Setting up a DNS server may of course add a level of complexity to the situation beyond what you are willing to deal with. This means I can simply use for all of my scripts/configurations, and the IP address used is determined by the DNS server, based on whether I am at home or external. On my home DNS server, I manually add a DNS record for and have it point to the local address, which overrides the public DNS record. When I am not at home, resolves to my public IP address, and I connect remotely through the relevant forwarded ports. (Version 1 was also often called 'CIFS', although to my knowledge the standards-defined CIFS is not 100 identical to Windows SMBv1. It may run over a 'NetBIOS Session' layer (TCP port 139), but more commonly used over raw TCP (port 445). The way that I solve it is by having a domain name for my home external IP address, and by hosting my own DNS server on my home network. The Windows file sharing protocol is called SMB, once upon a time short for 'Server Message Block'. I also have a number of services I host on a server at home, and I am faced with the same situation. One problem is determining when you are on your local network, as opposed to someone else's local network.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |