[avahi] Strange MDNS response from Axis cameras

[Iván Sánchez Ortega]

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

El Miércoles 08 de Febrero de 2006 00:47, Marc Krochmal escribió:
[...]
> Right, you don't need to configure an additional IP address on your
> box.  You just need to add a routing table entry indicating that
> 169.254 addresses are local.

Right, I see.

But, let's suppose that I'm a lazy sysadmin that doesn't want to modify the 
routing tables of a non-trivial number of windows workstations. So I set up 
my router to forward all traffic to 169.254.0.0 *BACK* to the local network. 
It may also add 1 to the TTL so the packet doesn't get dropped.

Yes, I've been reading RFC 3927, 2.6 and 2.7. Yes, I do know that this goes 
completely against that RFC. Yes, I shouldn't do stuff this way. Yes, I know 
that this is a complete hack. But it's fun to go against the rules :-)

But, in theory, a host unaware of Link-Local address routing will route 
traffic to 169.254.0.0 to the default gateway, my router, that would leave 
the TTL untouched, ARP to get the MAC address, and deliver the packet.

Would this (hackish) setup work, or am I mising something??


/me keeps on thinking...


After all, it may be simplier to change the routing table, and/or install 
Rendezvous for Windows...


Regards,
- -- 
- ----------------------------------
Iván Sánchez Ortega <ivansanchez at escomposlinux.org> <i.sanchez at mirame.net>

http://acm.asoc.fi.upm.es/~mr/ 
Proudly running Debian Linux with 2.6.12-1-686 kernel, KDE3.5.0, and PHP 
5.1.2-1 generating this signature.
Uptime: 01:33:40 up  3:54,  1 user,  load average: 0.29, 0.23, 0.39
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQFD6UHZ3jcQ2mg3Pc8RAuo7AJ4uLRpZqV6hYTOp58d45embI7UEBgCdF8/q
vV92e8cvSu54CW9mVjXEDTY=
=KejR
-----END PGP SIGNATURE-----