[avahi] Running avahi

[Steev]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Lennart Poettering wrote:
> Yes, avahi accepts traffic only from interfaces it considers
> "relevant", i.e. not from the loopback device (you scanned "localhost"
> with nmap, didn't you?)

Heh, yes, yes I did, was just to see if the port was even open.


> avahi still doesn't subscribe to any the multicast group on any
> interface. Everytime avahi finds a new "relevant" interface it prints
> a line like "New relevant interface dummy0.2 (#4)" to syslog (or
> STDERR).
> 
> Interfaces are considered relavant iff:
> 
>  - the interface has the flag  UP set
>  - AND it has the flag MULTICAST set
>  - AND it has the flag LOOPBACK *not* set
>  - AND it has the flag POINTOPOINT *not* set
>  - AND it has at least one address assigned with scope "global".
> 
> It seems as if avahi ignores the eth0 interface on your machine. To
> check why, please post the output of "ifconfig eth0". It should look
> like this:

eth0      Link encap:Ethernet  HWaddr 00:40:D0:33:FD:E1
          inet6 addr: fe80::240:d0ff:fe33:fde1/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:11 Base address:0x4000


> To check if avahi's netlink support works, please run "ifconfig dummy0
> 1.1.1.1 multicast". Then avahi should print the line "Interface
> dummy0.2 no longer relevant". After that run "ifconfig dummy0 down"
> which should bring avahi to print "Interface dummy0.2 no longer
> relevant".

It worked!  When I did the ifconfig dummy0 1.1.1.1 multicast
avahi-discover popped up 2 entries under ssh (Remote Terminal on mebius)
and 1 under workstation!

>>Jul  2 12:01:58 mebius avahi[10956]: iface.c: avahi_server_add_service()  failed.
> 
> 
> You seem to have a very interesting network configuration, haven't
> you? Something with empty MAC addresses or similar? Please post an
> "ifconfig -a" output, too.

dummy0    Link encap:Ethernet  HWaddr DE:89:2B:F1:EE:78
          inet addr:1.1.1.1  Bcast:1.255.255.255  Mask:255.0.0.0
          BROADCAST NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:105 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:14150 (13.8 Kb)

eth0      Link encap:Ethernet  HWaddr 00:40:D0:33:FD:E1
          inet6 addr: fe80::240:d0ff:fe33:fde1/64 Scope:Link
          UP BROADCAST MULTICAST  MTU:1500  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
          Interrupt:11 Base address:0x4000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:14130 errors:0 dropped:0 overruns:0 frame:0
          TX packets:14130 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:592720 (578.8 Kb)  TX bytes:592720 (578.8 Kb)

ppp0      Link encap:Point-to-Point Protocol
          inet addr:4.245.70.100  P-t-P:63.215.29.111  Mask:255.255.255.255
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:2095 errors:0 dropped:0 overruns:0 frame:0
          TX packets:1881 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:3
          RX bytes:230332 (224.9 Kb)  TX bytes:141040 (137.7 Kb)

sit0      Link encap:IPv6-in-IPv4
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

tunl0     Link encap:IPIP Tunnel  HWaddr
          NOARP  MTU:1480  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)


I am thinking it might ahve to do with the sit0 and/or tunl0 devices ?


> By default if an application binds on an IPv6 port its binds to the
> same port on IPv4, too. So if you bind on "::" (which is the IPv6
> equivalent of 0.0.0.0, i.e. all local addresses) you bind on 0.0.0.0
> too. It seems like you have an explicit line for binding to 0.0.0.0 in
> your sshd_config, so this conflicts.

Apparently it is a default setting in ssh as its actually commented out
in the config file.  Not a huge deal, as it is running and I can ssh in.

- -- Steev
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)

iD8DBQFCxuy71c+EtXTHkJcRAvvFAJsFfvjY26bHYgMtomDeOeJuh/3hAwCeIolM
FTmSo5YLw8vlKZg03zwdvVU=
=LoSS
-----END PGP SIGNATURE-----