X
xane
Guest
Not just a jumble of search keywords.
Get ready ...
My home network involves a Linux Router/Firewall that also operates as a DHCP server, the Windows and FreeBSD machines get their local IP addresses from it and use it as a Gateway for internet.
Because the local IP addresses (192.168.x.x) are dynamically allocated, is there a way of referencing each of the local network machines by name rather than IP, a kind of "local DNS" as it were. I was assuming, with my limited knowledge of networking, that this would be a function of DHCP.
For example: assume "alpha" is my Linux DHCP and gateway machine, and "beta" and "delta" are Windows boxes, amd "gamma" is a FreeBSD box. How can I get "ping beta" to work on the FreeBSD "gamma" machine ?
As non-Windows machines are involved, I can't use WINS or NetBIOS trickery. I'm looking to avoid using static IPs and a hosts file for the name resolution, can anyone suggest another way ?
TIA
Get ready ...
My home network involves a Linux Router/Firewall that also operates as a DHCP server, the Windows and FreeBSD machines get their local IP addresses from it and use it as a Gateway for internet.
Because the local IP addresses (192.168.x.x) are dynamically allocated, is there a way of referencing each of the local network machines by name rather than IP, a kind of "local DNS" as it were. I was assuming, with my limited knowledge of networking, that this would be a function of DHCP.
For example: assume "alpha" is my Linux DHCP and gateway machine, and "beta" and "delta" are Windows boxes, amd "gamma" is a FreeBSD box. How can I get "ping beta" to work on the FreeBSD "gamma" machine ?
As non-Windows machines are involved, I can't use WINS or NetBIOS trickery. I'm looking to avoid using static IPs and a hosts file for the name resolution, can anyone suggest another way ?
TIA