[avahi] adding a zeroconf network to an existing private network
j2u44u at gmail.com
Mon Mar 1 10:10:16 PST 2010
On Sun, Feb 28, 2010 at 3:57 PM, Lennart Poettering
<lennart at poettering.net>wrote:
> On Sun, 28.02.10 15:53, j2u4 j2u4 (j2u44u at gmail.com) wrote:
> > I have 3 machines on a private 192.168.0.0 network. I have a device that
> > only exposes a zerconf 169.254.0.0 interface.
> > What is the best way to make the zeroconf device visible to hosts on my
> > private network? Is it just a matter of running avahi daemon on all of
> > and adding a route to 169.254.0.0 on their default ethernet interfaces?
Thanks, that is exactly what I was looking for. I'm having a bit of trouble
debugging it, though, as I can't seem to find the zeroconf device on the
network now. Here's my config:
eth0 Link encap:Ethernet HWaddr 00:11:11:b2:e6:38
inet addr:192.168.100.2 Bcast:192.168.100.255 Mask:255.255.255.0
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use
192.168.100.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 1000 0 0 eth0
0.0.0.0 192.168.100.1 0.0.0.0 UG 0 0 0 eth0
0.0.0.0 0.0.0.0 0.0.0.0 U 1000 0 0 eth0
Do you see anything wrong here? The gateway route to 192.168.100.1 is used
to get out to the internet through NAT. I can remove that route, but still
can't discover my zeroconf device (it's an hdhomerun).
I *can* see the hdhomerun if a reconfigure eth0 to be a ipv4ll instead of
static 192.168.100.2, but then that breaks the rest of the network.
Any ideas or tips?
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the avahi