home :: software :: zeroconf
Thu, 03 Nov 2005
IPv4 Link Local addresses
James Henstridge notes that zeroconf can cause large amounts of network traffic. Yes, that was true back in July. A bug was filed and then fixed within 2 days.
This was because I was at DebConf and able to see how zeroconf performed in a large environment. Basically there are two tests you do to determine whether an ARP packet is destined for you. And at the time, zeroconf, was only doing one of them.
Update: 18:20 AESTDavyd asks why would you use zeroconf over NetworkManager. I haven't been able to put my finger on exactly why, but I feel the design is wrong.
I do believe there should be an overall co-ordinating process looking after networking on the user-space side of the fence though. I've been thinking about writing something which would do it too; but I haven't fleshed out my ideas enough to commit my editor to coding.
Oh, one bug that NetworkManager does have is that it only allocates IPv4LL addresses when it fails to acquire one from the DHCP server. This is wrong and goes against RFC3927.
[ / software / zeroconf] Trackbacks (0) Comments (0) permanent link permanent link
About
ॐ (aum) - what was, what is and what will be, wildfire's musings
Anand Kumria
wildfire@progsoc.org
Calendar
Topics
- beauty - 1
- blogging - 4
- books - 1
- comms - 1
- debian - 7
- django - 4
- ebay - 1
- edinburgh - 8
- finance - 1
- freedom - 2
- general - 4
- hardware - 3
- dell - 2
- disks - 1
- health - 3
- helsinki - 1
- learning - 1
- london - 1
- review - 1
- movies - 1
- salsa - 1
- security - 2
- software - 22
- blosxom - 2
- gnome - 1
- moblog - 1
- ubuntu - 1
- vcs - 2
- zeroconf - 1
- sydney - 8
- isp - 3
- thisisbroken - 2
- travel - 1
- work - 2
- awayphone - 1
- general - 1
Subscribe
Subscribe to a syndicated feed of my weblog, brought to you by the wonders of Atom.
Music
Blosxom
Rendered in only 0.5679 seconds.
Web Standards
