Hi.
For a test network, internal 192.168..x subnet, I've got some boxes that are connected to a dhcp server that I have no control of.
I'm looking to test/play with some services on the different boxes, but would like to have other boxes be able to reference the boxes running the services. My issue, the box running service X could have ip1 which could then change to ip2 the next day..
I'm considering some sort of cheap/fast broadcast process where the machines running the given services, broadcast out to the network "i'm boxA running service Foo on ipXX" and the listening machine would then decouple the message, and update the resolve.conf file, or whatever the required file is to then be able to use the required name/ip for the service..
Thoughts/comments??
Would nc be good for this, would there be a better solution?
Should I create a limited user on each box, and have a process attached to the user listen, and process the messages?
Thanks guys..
On Mon, 2014-10-13 at 13:26 -0400, bruce wrote:
Hi.
For a test network, internal 192.168..x subnet, I've got some boxes that are connected to a dhcp server that I have no control of.
I'm looking to test/play with some services on the different boxes, but would like to have other boxes be able to reference the boxes running the services. My issue, the box running service X could have ip1 which could then change to ip2 the next day..
I'm considering some sort of cheap/fast broadcast process where the machines running the given services, broadcast out to the network "i'm boxA running service Foo on ipXX" and the listening machine would then decouple the message, and update the resolve.conf file, or whatever the required file is to then be able to use the required name/ip for the service..
Thoughts/comments??
Would nc be good for this, would there be a better solution?
Should I create a limited user on each box, and have a process attached to the user listen, and process the messages?
Thanks guys..
Isn't that pretty much what Avahi does? Why reinvent the wheel?
poc
Hey patrick.
couldn't really find any good pointers on this.
any step by steps you can point me to.
ie, boxA with ipA is running mysql and has name boxA
the dhcp of boxA might change day to day
user on boxB wants to be able to get ip of boxA
how can avahi be used in this case?
thanks
On Mon, Oct 13, 2014 at 6:50 PM, Patrick O'Callaghan pocallaghan@gmail.com wrote:
On Mon, 2014-10-13 at 13:26 -0400, bruce wrote:
Hi.
For a test network, internal 192.168..x subnet, I've got some boxes that are connected to a dhcp server that I have no control of.
I'm looking to test/play with some services on the different boxes, but would like to have other boxes be able to reference the boxes running the services. My issue, the box running service X could have ip1 which could then change to ip2 the next day..
I'm considering some sort of cheap/fast broadcast process where the machines running the given services, broadcast out to the network "i'm boxA running service Foo on ipXX" and the listening machine would then decouple the message, and update the resolve.conf file, or whatever the required file is to then be able to use the required name/ip for the service..
Thoughts/comments??
Would nc be good for this, would there be a better solution?
Should I create a limited user on each box, and have a process attached to the user listen, and process the messages?
Thanks guys..
Isn't that pretty much what Avahi does? Why reinvent the wheel?
poc
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 10/14/14 06:50, Patrick O'Callaghan wrote:
On Mon, 2014-10-13 at 13:26 -0400, bruce wrote:
Hi.
For a test network, internal 192.168..x subnet, I've got some boxes that are connected to a dhcp server that I have no control of.
I'm looking to test/play with some services on the different boxes, but would like to have other boxes be able to reference the boxes running the services. My issue, the box running service X could have ip1 which could then change to ip2 the next day..
I'm considering some sort of cheap/fast broadcast process where the machines running the given services, broadcast out to the network "i'm boxA running service Foo on ipXX" and the listening machine would then decouple the message, and update the resolve.conf file, or whatever the required file is to then be able to use the required name/ip for the service..
Thoughts/comments??
Would nc be good for this, would there be a better solution?
Should I create a limited user on each box, and have a process attached to the user listen, and process the messages?
Thanks guys..
Isn't that pretty much what Avahi does? Why reinvent the wheel?
It may be easier for him to use a Dynamic DNS service, such as http://www.dnsdynamic.org/, and ddclient on the Fedora side.
Allegedly, on or about 13 October 2014, Patrick O'Callaghan sent:
Isn't that pretty much what Avahi does? Why reinvent the wheel?
Does Avahi even do anything on a system which has already been set up by DCHP?
Allegedly, on or about 13 October 2014, bruce sent:
any step by steps you can point me to.
ie, boxA with ipA is running mysql and has name boxA
the dhcp of boxA might change day to day
user on boxB wants to be able to get ip of boxA
Does your unmanageable DHCP server do name resolution, as well? If so, then you can just use the client hostnames, already, without having to do anything else.
Allegedly, on or about 14 October 2014, Ed Greshko sent:
It may be easier for him to use a Dynamic DNS service, such as http://www.dnsdynamic.org/, and ddclient on the Fedora side.
Wouldn't that just return the public facing address of the network, rather than the individual client addresses?
On 10/14/14 11:39, Tim wrote:
Allegedly, on or about 14 October 2014, Ed Greshko sent:
It may be easier for him to use a Dynamic DNS service, such as http://www.dnsdynamic.org/, and ddclient on the Fedora side.
Wouldn't that just return the public facing address of the network, rather than the individual client addresses?
No.....
You would request sign-up for the service and use their internal domain of dnsdynamic.com and request a subdomain of that. Then you'd give you systems hostname.mysub.dnsdynamic.com. Then you'd configure ddclient to send you system's IP address to dnsdynamic.com when it changes.
Typically, you'd then send it your internal, non-routeable IP address such as 192.168.0.12. You'd do this for all of your systems and then have them address the other systems by these assigned names.
so essentially,
the process would have each system in the sub net, report it's address/name to the external dyndns service, where it would be managed/returned as a subname, which would then populate the local/internal resolv.conf (or whatever is required) to allow the local services/users of the subnet the ability to access the boxes by the "subnames"...
could work..
On Mon, Oct 13, 2014 at 11:49 PM, Ed Greshko ed.greshko@greshko.com wrote:
On 10/14/14 11:39, Tim wrote:
Allegedly, on or about 14 October 2014, Ed Greshko sent:
It may be easier for him to use a Dynamic DNS service, such as http://www.dnsdynamic.org/, and ddclient on the Fedora side.
Wouldn't that just return the public facing address of the network, rather than the individual client addresses?
No.....
You would request sign-up for the service and use their internal domain of dnsdynamic.com and request a subdomain of that. Then you'd give you systems hostname.mysub.dnsdynamic.com. Then you'd configure ddclient to send you system's IP address to dnsdynamic.com when it changes.
Typically, you'd then send it your internal, non-routeable IP address such as 192.168.0.12. You'd do this for all of your systems and then have them address the other systems by these assigned names.
-- If you can't laugh at yourself, others will gladly oblige.
-- users mailing list users@lists.fedoraproject.org To unsubscribe or change subscription options: https://admin.fedoraproject.org/mailman/listinfo/users Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines Have a question? Ask away: http://ask.fedoraproject.org
On 10/14/14 12:19, bruce wrote:
so essentially,
the process would have each system in the sub net, report it's address/name to the external dyndns service, where it would be managed/returned as a subname, which would then populate the local/internal resolv.conf (or whatever is required) to allow the local services/users of the subnet the ability to access the boxes by the "subnames"...
could work..
First, it may or may not be a subdomain.... But it would be a unique FQDN (Fully Qualified Domain Name).
Second, there is no need to alter any resolv.conf since the hostname is held in the standard DNS.
Just do some common name lookups....
host roger.dnsdynamic.com host maria.dnsdynamic.com host sam.dnsdynamic.com
You'll find the IP addresses associated with the hosts are not within the range owned by dnsdynamic.com.
Typically, this method is used for allowing for name resolution to route-able IP addresses so folks on the internet can assess you systems.
But, there is nothing wrong with sending internal non-route-able addresses so you could access internal systems by name without too much hassle.
On Tue, 2014-10-14 at 14:05 +1030, Tim wrote:
Allegedly, on or about 13 October 2014, Patrick O'Callaghan sent:
Isn't that pretty much what Avahi does? Why reinvent the wheel?
Does Avahi even do anything on a system which has already been set up by DCHP?
My understanding of this is pretty vague, but I believe it does allow things like service discovery (i.e. using a service name rather than a host name).
poc