1 This file states changes as of version 0.2.4:
2 $Id: CHANGELOG,v 1.47 2005/05/25 14:51:37 kattemat Exp $
4 0.4.10 --------------------------------------------------------------------
8 olsrd now also compiles on OpenBSD systems. Thanks a lot to Holger
9 Mauermann for the patches! Use 'make OS=obsd' to build.
13 Olsrd now maintains a set of IP addresses that is considered
14 invalid. Checks against this set is done on all received
15 OLSR packets announced originator addresses. The dataset can
16 be updated dynamically.
20 Updated interface version to 3 and added more noticeable warning
21 for version missmatch.
25 The dependency on the math lib came from the use of pow(3) in hte
26 mantissa/exponent calculation. The calls to pow in this long forgotten
27 code, was very unnessecarry. The pow calls are replaced with bitwise
28 shifts and -lm is no longer needed.
32 - Fixed crash when changing IPv6 address at run-time
33 - Fixed a bug that prevented setting willingness 0 in the configfile
34 - Did various updates to prevent assertion when a neighbor
35 has changed IP and sends HELLO before its olsrd precess has detected
38 0.4.9 ---------------------------------------------------------------------
42 The MID database is now also indexed by alias addresses. this makes
43 look-ups of main addresses based on alias addresses _much_ faster.
44 The mid_lookup_main_addr function alone has gone from >30% of the
45 total CPU time used by olsrd to <1%.
46 PLUGIN DEVELOPERS: datatypes for MID entries has been changed.
48 Routing table calculation in the LQ case now uses balanced binary
49 trees instead of linked lists, which makes look-ups much faster.
51 The debug output function olsr_printf() is not used by olsrd
52 internals any more. Instead the macro OLSR_PRINTF is to be used.
53 This macro does debug level testing _before_ doing any function
54 calls(both printf itself and parameters to printf). This is a much
55 more optimized way of doing debug output. In addition olsrd can
56 be built without any debug output code if doing 'make NODEBUG=1'.
60 Validity times for dataset entries are now set using the clock_t type
61 (used to be struct timeval). This data is now fetched from the times(2)
62 function instead of gettimeofday(2). This prevents possible problems
63 if the system time is changed.
64 PLUGIN DEVELOPERS: Note that datatypes for close to all dataset entries
65 (link, neighbor, mid, hna, tc etc.) has been changed!!
69 Multiple interfaces can now use the same interface configuration block.
71 Interface "if0" "if1" "if2"
76 Interface configurations now also support the "Weight" directive. When
77 olsrd finds multiple links to a neighbor it will choose the link
78 going via the interface with the lowest weight. Olsrd normally
79 sets this weight dynamically based on interface characteristics,
80 but if the user wishes to set a fixed weight in a interface(or
81 a group of interfaces), this directive is now available.
83 Moreover, interface configurations now support the "LinkQualityMult"
84 directive. It takes an IP address and a multiplier as arguments.
92 LinkQualityMult 192.168.0.1 0.7
93 LinkQualityMult default 0.5
98 The idea is to make certain links via the configured interface
99 artificially worse or better than they really are. The first parameter
100 specifies the IP address of a neighbour interface. The second
101 parameter is the multiplier to be applied to the link to the specified
104 After we have derived the link quality from the packet loss among the
105 packets received from the specified neighbour interface, we multiply
106 the link quality by the given multiplier. So, the multiplier changes
107 the LQ value that we use when determining the ETX, which is 1 / (LQ *
110 If "default" is given as the IP address then the multiplier applies to
111 all links via the configured interface. Note, however, that olsrd only
112 assigns one multiplier to each link. It does so in the following way.
114 * If there is a "LinkQualityMult" line that matches the IP address of
115 the link's neighbour interface, then use the multiplier in this
118 * If there isn't any matching line, then look for a "default" line. If
119 there is a "default" line, then use the multiplier in this "default"
122 * Otherwise use 1.0, i.e. do not modify the LQ value at all.
124 Hence, a line with an IP address has priority over a "default" line.
126 In the above example, the LQ value of the link between the local
127 interface if0 and the neighbour interface 192.168.0.1 would be
128 multiplied by 0.7. All other links between the local interface if0 and
129 a neighbour interface would be multiplied by 0.5.
133 The socket option IPV6_V6ONLY is now set on IPv6 sockets in linux.
134 This means that olsrd will no longer receive IPv4 traffic when
135 running in IPv6 mode.
136 This should enable users to actually run one olsrd instance using
137 IPv6 and one using IPv4 at the same time :)
141 The httpinfo, dyn_gw and dot_draw plugins now all include olsrd
142 headerfiles directly. A plugin should define OLSR_PLUGIN before
143 including olsrd headers. Doing things this way removed the
144 redundant datatype definitions that has so often caused trouble
145 when things has been updated in olsrd.
149 olsrd now also compiles on NetBSD systems. Use 'make OS=nbsd' to
150 build. This port is not very well tested and feedback is greatly
153 EXPERIMENTAL MULTI-INTERFACE CODE FOR FREEBSD
155 Experimental code using libnet can be compiled in allowing multiple
156 interfaces to be used in FreeBSD. You enable this by compiling using
157 OS=fbsd-ll. You must have libnet-devel installed for this to work
158 (/usr/ports/net/libnet-devel).
162 - WLAN devices are now detected in FreeBSD
163 - First specified interfaces IP is used as main address.
164 - Broadcastflag is not checked on interface if fixed broadcast is
166 - Removed Linux link layer code as this was not really in use.
167 - Added -nofork command line option
171 - Link sensing now works according to announced vtime from
172 neighbors. Previously links going symmetric->asymmetric
173 were not necessarily detected until the holding time expired.
174 - A bug in route addition/removal that could lead to routes
175 using GWs being added before the actual route to the GW
176 was set up, has been fixed.
177 - A bug in the interface selection in route calculation has been
178 fixed. New routes are no longer added prior to deleting old ones,
179 since this caused trouble.
180 - A bug in the IPv6 multicast address configuration has been fixed.
181 This caused olsrd not to work with global IPv6 addresses.
182 - A bug in the IPv6 prefix-from IPaddr function has been fixed. This
183 bug caused HNA prefixes to always be calculated to 0.
184 - If a 2-hop neighbor is also a 1-hop neighbor, a bug made olsrd
185 prefer a bad direct link to a better link via an MPR.
186 - If a link or interface lookup failed, olsrd crashed.
187 - Fixed a crash in the LQ packet generation code based on a
188 signed/unsigned integer comparison.
191 0.4.8 ---------------------------------------------------------------------
195 Olsrd is now distributed under a BSD style license. We believe olsrd will
196 be better off using this license as it opens up for commercial players
197 to use olsrd freely in their products. In the end this will lead to
198 this kind of users doing serious testing and bug fixing of olsrd.
200 ETX-LIKE LINK QUALITY DETECTION
202 We can now determine the packet loss on a link by looking at the serial
203 numbers of the OLSR messages received from a neighbor. This tells us how
204 many packets get through from our neighbor to us. We use a new extended
205 kind of HELLO messages (LQ_HELLO messages, LQ = link quality) to broadcast
206 the link quality that we have determined on our end of the link to our
207 neighbors. So do our neighbors, and we as well as they end up with an
208 idea of how good the link is in both directions. From the LQ_HELLOs we
209 also learn the link quality between our neighbors and our two-hop neigh-
210 bors. In this way we can select those neighbors as MPRs that have the
211 best links to our two-hop neighbors. To distribute the link quality
212 throughout the network, we use a new extended version of TC messages
213 (LQ_TC messages). They contain the qualities at both ends of each of our
214 links. Nodes can then run Dijkstra's algorithm to find a path between
215 themselves and other nodes that minimizes the packet loss.
217 If the newly introduced "LinkQualityLevel" is set to zero in the
218 configuration file, link quality is not used and the daemon behaves as
219 before, i.e. as specified by the OLSR RFC. If this parameter is set
220 to 1, LQ_HELLOs and LQ_TCs are used instead of HELLOs and TCs, link
221 quality is measured and MPRs are selected based on the link qualities.
222 If this parameter is set to 2, the routing table is additionally
223 calculated based on the link qualities.
225 Setting "LinkQualityLevel" to a non-zero value BREAKS COMPATIBILITY. You
226 will then not be able to participate in RFC-conformant OLSR networks
227 any longer. This is because we use LQ_HELLOs and LQ_TCs instead of HELLOs
228 and TCs in this case.
230 It's best practice to set "LinkQualityLevel" to the same value on all
233 When determining the quality of a link olsrd only considers a given
234 number of most recent OLSR packets received from its neighbors. By
235 default, olsrd looks at the 10 most recent OLSR packets. This can be
236 changed via the "LinkQualityWinSize" configuration option. Values
237 between 3 and 128 are legal.
239 NEW CONFIGFILE PARSER/FORMAT/SCHEME
241 A whole new config file syntax and parser is introduced with this
242 release. The parser is generated using flex and bison and it is
243 designed to be very modular. The parser can be compiled as either
244 a standalone binary, a shared library or as part of olsrd. This way
245 other applications can parse and generate olsrd configuration files
246 only by linking to the dynamic library.
247 In the new configfile options can be set pr. interface, plugin
248 parameters can be set, more IPC options can be set...and more.
249 The syntax is documented in the olsrd.conf(5) manual page found
250 in the files/ directory.
251 Olsrd internals now uses a single struct, as returned by the config
252 parser, for all configuration in runtime. this means that updating
253 values in this struct will dynamically update olsrd operation. It
254 also means that all configuration is now kept in one place instead
255 of spread all across the place.
257 FREEBSD AND MAC OSX PORT
259 This version offers an initial port of olsrd to FreeBSD and Mac OS
260 X. Like the Windows port it currently does not support IPv6. As this
261 is a very first try at supporting FreeBSD and Mac OS X, this port is
262 probably not as reliable as the Linux version. We'd greatly appreciate
263 feedback and bug reports. To compile you need GNU make. Then simply
264 run "gmake OS=fbsd" to build the executable.
268 The makefiles used to build olsrd have been rewritten and now includes
269 dependency file generation using makedep.
273 Tables are now only printed if changes occur, so there are no longer
274 any periodical output when using a debuglevel >0. A "heartbeat" is
275 now printed to STDOUT(if it is a terminal) in the form of a rotating
276 line to show that olsrd is actually operating.
277 Adding "ClearScreen yes" to the configuration file clears the screen
278 each time before the debug output shows updated information. This
279 makes the debug output easier to read in many cases. "ClearScreen no"
280 is the default, if no "ClearScreen" directive is given in the
285 There are some changes in the plugin interface. It is now at
286 version 2. Plugin specific parameters from the configfile
287 using the PlParam option, will now be passed on to plugins.
288 To receive such parameters a plugin must implement a function:
290 register_olsr_param(char *key, char *value)
291 to which parameter pairs will be passed.
295 Olsrd no longer uses any thread library on its operation. Everything
296 now happens in the main thread allowing for use of olsrd on platforms
297 with no thread library.
299 ACPI SUPPORT IN WILLINGNESS CALCULATION(LINUX)
301 The willingness calculation for Linux, now also supports the more
302 modern ACPI proc interface in addition to APM. This is not well
303 tested and feedback is appreciated!
307 Various options regarding IPC connections can now be set in the
308 configfile. The options are max connections, allowed unicast
309 hosts and allowed net-ranges.
313 Much of the message generation and net output code is rewritten.
314 Sending of partial messages should now work 100%. Also TC, MID
315 and HNA messages are now cached for a random amount of time
316 before transmitted - this often leads to the situation where these
317 messages are sent together with an HELLO message, which is highly
318 desirable since it saves network resources.
319 PLUGIN DEVELOPERS must note that the buffers and size variables
320 used in net output is no longer directly accessible!
322 NET OUTPUT CODE REWRITTEN
324 Every interface now has one outputbuffer registered. This allows
325 messages to be "cached" as explained above, so that multiple
326 messages are stacked together.
327 Also the outputbuffer and size are no longer accessible directly,
328 an API is available to plugins(and olsr code).
330 OS DEPENDENT NETWORK INTERFACE
332 The OS dependent network functions are now defined in net_os.h
333 instead of being mixed up with internal network functions
338 A bug that caused the announced ANSN sequence number to never stop
339 being increased when a change in the MPR selector set was detected
340 has been fixed. Another TC related bug that caused timed out TC
341 entries not to be deleted from the routing table in certain cases
342 has also been fixed. These bugs could cause unstable routes.
343 A bug that in many cases caused the wrong routes to be deleted
344 when using IPv6 has been fixed.
347 0.4.7 ---------------------------------------------------------------------
349 NATIVE WINDOWS GUI AND INSTALLER
351 We now have a native Windows GUI. The GTK+ version is no longer
352 supported on Windows. The new native GUI is pretty compact as it does
353 not require the GTK+ runtime DLLs. In addition to monitoring olsrds
354 state the GUI offers an easy way for novice users to configure
355 olsrd. It's pretty self-explanatory. Have a look at README-WIN32.txt
356 for details. The Windows version now also comes with an installer
357 based on the freely available Nullsoft Scriptable Install System
358 (NSIS). Looks like the Windows port is becoming more and more
361 WIRELESS INTERFACE DETECTION ON WINDOWS
363 Like the Linux version the Windows port is now able to tell WLAN
364 interfaces from wired interfaces. We can now, for example, set
365 different HELLO intervals for WLAN interfaces and wired interfaces,
370 The order of updates of calculated routes is swapped. Now new routes
371 are added prior to deleting old ones. This could fix issues where
372 in some very very few cases one could experiment loss of routes.
376 There were quite some bugs in IPv6 operation in 0.4.6. These are
377 the bugs that were fixed:
378 - HNA message parsing did not work.
379 - Some IPv6 addresses were printed as IPv4 addresses in the
381 - The '-dispin' option now works again.
382 - A filedescriptor leak in the IPv6 interface detection caused
386 0.4.6 ---------------------------------------------------------------------
390 Read the README-WIN32.txt file!
392 DYNAMIC NETWORK INTERFACE UPDATES
394 Network interfaces can now be updated and removed/added at
395 runtime. Olsrd will check all interfaces specified in the config
396 file or on the command-line, every 5 seconds. If updates
397 occur, olsrd will register this and update the necessary data.
398 If interfaces are removed or added, olsrd will detect this
399 and configure the interfaces. If an interface is removed
400 olsrd will continue to check the interface, so if say, a PCMCIA
401 card is removed and later on reinserted(and given the same name),
402 olsrd will detect this and start running on it again.
404 Note that olsrd will now run even if no interfaces are detected.
406 ROUTE CALCULATION UPDATE
408 All 1 hop neighbor addresses that are not directly reachable trough
409 a symmetric link in the link set will now be added with a GW in the
410 routing table. this GW will be an interface address from a registered
411 symmetric link to the neighbor.
415 Alias addresses are now registered in the link set processing
416 if available. This is not to pretty(since the vtime has to
417 be a mere guess) but it gives faster initial route updates.
418 If a HELLO is received(at initial registration) from an IP
419 that is not the same as the one set as main address in the
420 received HELLO header, then the IP from which the HELLO was
421 received will be registered as an alias of the main address
422 set in the HELLO header. The default vtime is set to 15 secs.
426 All OS dependent interface configuration code is now located in
427 OS/ifnet.c(that would be linux/ifnet.c if using GNU/Linux).
428 The functions are available trough the headerfile src/ifnet.h
432 - Some timer issues fixed
433 - Got rid of the global socket descriptors
434 - Updated indexing of network interfaces
435 - Introduced a global socket to use for ioctl calls(ioctl_s)
436 - Removed upper limit for interfaces to use
437 - Point-to-point interfaces are now allowed
438 - The main select(2) loop now uses a timeout
439 - A small bugfix in the select fd-set update code
440 - Some bugfixes in the configuration file parsing
441 - stdout/stderr are now set to not be buffered
442 - A bugfix in the MID generation regarding seq. numbering
446 A new set of functions that are called whenever a change in the
447 interface configuration(update, addition, removal) is made is
449 These functions are added and removed very much like the ptf
450 functions. Available trough the functions add_ifchgf and del_ifchgf.
452 OBS OBS OBS!!! PLUGIN DEVELOPERS READ THIS!!!!
454 The interface struct(declared in interfaces.h) has changed.
455 Plugin developers must update plugins that uses the interface
458 The headerfile olsr_plugin_io.h which contains the plugin interface
459 commands now contains a revision list where all changes are
463 0.4.5 ---------------------------------------------------------------------
467 A plugin that generates and checks message signatures is added.
470 PLUGIN: TOPOLOGY GRAPH
472 A plugin that generates output of the topology in the dot format
473 is added. See lib/dot_draw
477 Some optimizations done that should cause fewer route recalculations.
481 Some bugs reported by Takafumi Tanaka fixed.
483 RESTORATION OF NETWORK SETTINGS
485 Network settings like disabling of ICMP redirects and spoof filter, are
486 now restored at exit by olsrd.
490 Nodes would in certain scenarios retransmit messages originating for
491 themselves. This was a RFC incompliance. Reported by Ingmar Baumgart.
495 No longer setting the HELLO interval of non-wlan interfaces as a multiplier
496 of the wlan interval. The interval is set seperatly now.
497 Due to this there are some updates in the configfile imperatives.
501 Some new macros introduced for table insertion and removal and IP
502 copying and comparison.
506 IPv6 bugfixes in the GUI.
509 0.4.4 ---------------------------------------------------------------------
513 Routes are no longer added via neighbors declaring a willingness
516 LINK SENSING AND ROUTE CALCULATION
518 Link sensing and route calculation has been updated to handle
519 multiple links between hosts in a sane way.
523 IP spoof filtering is disabled on the interfaces which olsrd runs.
524 These settings are not restored!
528 ICMP redirect message generation is disabled on the interfaces
530 These settings are not restored!
532 CONFIGFILE OPTIONS FOR MID AND HNA ADDED
534 Options to set the MID and HNA emission intervals and
535 validity time in the configfile added.
539 Option to set what IPv6 address type(scope) to use in the
540 configfile added. It can be set to either global or site-local.
544 Options to set site-local and global multicast addresses
545 in the configfile added.
547 EMISSION INTERVAL FUNCTION
549 Functions to set emission intervals at runtime added.
551 LINK LAYER NOTIFICATIONS
553 If started with the -llinfo switch olsrd will collect and display
554 link-layer information on neighbors. This is no longer limited to
555 one interface. But no action is taken based on this info - and
556 there is a upper limit of 8 neighbors from which this info can
557 be collected pr. interface. This limitation is inherited from the
558 WLAN drivers and is not something imposed by the olsrd code!
560 IPv6 HNA MESSAGE FORMAT
562 IPv6 HNA messages now contains 128-bit netmask instead of prefix.
566 Added "packet transform functions" which allow plugins to alter all
567 outgoing OLSR traffic.
571 Moved most headers out of OS dependent directories. The tunneling
572 and link-layer notification interface is not yet separated from
573 the /linux directory.
577 A manpage(olsrd(8)) describing olsrd has been created. It is installed
578 when using 'make install'.
581 0.4.3 ---------------------------------------------------------------------
585 Olsrd now supports runtime-loadable plugins! A couple of example plugins
586 are located in the lib/ directory. Read the README files in the various
587 plugin directories for more info. A directive to load plugins have been
588 added to the configfile as well.
589 Documentation of the plugin interface can be fount at http://www.olsr.org.
591 The plugin interface is designed to be extendable. But it should _always_
592 be backwards compatible with the interface used in this release!
594 LINK-LAYER NOTIFICATION
596 Some preliminary link-layer notification code has been added. Link quality
597 can be written to stdout if olsrd is started with the -llinfo switch.
598 No action is currently taken based on this info. And info will only
599 be retrieved from the interface named "eth1".
600 This code is not usable for users as of yet!
604 Neighbors with willingness set to WILL_ALWAYS is now always added. The
605 MPR selection is optimized as described in RFC3626 section 8.3.1
610 There was a couple of bugs in the MPR selection code. All fixed.
614 Users could not run olsrd on multiple interfaces using the Linux 2.6 kernel
615 series. This is now fixed.
619 One small bug in link hysteresis initialization and one in HNA route
622 MESSAGE-SEQUENCENUMBER INCOMPLIANCE
624 Message-seqnos was implemented on a pr. messagetype and pr. interface
625 basis. This is not RFC3626 compliant and has been updates. All messages
626 and interfaces now uses a global seuencenumber.
628 RANDOM SEQUENCENUMBERS
630 Sequencenumbers are now initialized using a random value.
634 Fixes for running olsrd in daemon mode(debug 0).
638 Optimizations based on profiling implemented.
642 Message size is checked for every message before passing it to the
643 appropriate message parsing function. If the size is bigger than the
644 remaining size of the olsr packet then the message is discarded.
648 Some minor modifications done to the gui.
652 Lots of changes in handling of registration and unregistration of
653 scheduler, socketparser, parser and local hna set.
654 Some restructuring and movement of functions.
657 0.4.2 ---------------------------------------------------------------------
661 0.4.1 ---------------------------------------------------------------------
665 0.4.0 ---------------------------------------------------------------------
669 Link hysteresis as described in the RFC added.
673 TC redundancy as described in the RFC added
677 MPR redundancy as described in the RFC added
681 The scheduler has been rewritten to register scheduled
682 events(function pointers) dynamically.
686 The parser has been rewritten to register parse functions
687 on a pr. messagetype dynamically
691 A wrapper for the malloc(3) syscal has been introduced.
692 olsr_malloc(size_t, const char *) should ALWAYS be used.
696 Lots of restructuring in headerfiles.
697 Linux spesific code moved to subdirectory linux/
698 FreeBSD code to be put in freebsd/
699 LOTS of code restructured due to the rexrite of the scheduler
704 Optimizing the MPR set as suggested in the RFC section
709 Some bugs in MPR selection fixed.
712 0.3.8 ---------------------------------------------------------------------
716 HNA code completely rewritten!
717 The old code was really bad! Now it is much cleaner implemented and
719 One- and two-hop neighbor list structures rewritten. They now use
720 the same hashed double-linked lists as the rest of the information
725 Some code restructuring which resulted in the new files: timer.h,
726 mantissa.c, mantissa.h, hashing.c, hashing.h, linux/net.c
727 linux/net.h, linux/kernel_routes.c, linux/kernel_routes.h and some
732 The bug causing errormessages on exit is fixed.
733 The bug that caused initial HNA routes in the GUI to display a hopcount
735 IPv6 HNA netmasks were all added as /128. It's fixed now.
739 Turns out sitelocal address had to be preferred to avoid IPv6 header
740 messing up link-sensing. Bug fixed
743 0.3.7 ---------------------------------------------------------------------
747 The entire TC set and MPR selector set code rewritten. Hashing and
748 double linked lists added to the MID code.
749 Lots of HNA code has been rewritten as well.
753 When a node lost connectivity to a HNA GW all HNA entries to that gw
754 was deleted. This has been fixed - and HNA entries only gets deleted
756 Other HNA bugs have been fixed as well. But the whole HNA implementation
761 There was a bug that caused holdingtime not to be properly recalculated
762 when using non-default emission intervals.
764 Forwarding and symmetric neighbors
766 Seems I had misread the RFC on what a 1-hop symmetric neighbor is.
767 Now the link-set is checked when a check for a symmetric neighbor
768 is done. Not the 1 hop neighbor set as it used to be. This way
769 the hack when receiving MID messages could be removed.
773 Global addresses are now preferred. Sitelocal addresses are only used
774 if no global addresses are found. There have been problems where
775 the address set in the IP header of IPv6 packets do not match the
776 address chosen by OLSR.
780 The GUI is finally updated! It can now handle piggybacked messages
781 and link sensing HELLO message format.
784 0.3.6 ---------------------------------------------------------------------
786 HNA support using IPv6
788 HNA now works using IPv6 as well! Just add the network address and
789 prefix in the HNA6 section in the configfile. The IPv6 HNA packets differ
790 some from the IPv4 as they don't send the netmask but the prefix.
793 NEW FILENAME FOR THE BINARY AND CONFIG FILE
795 They are now called olsrd and olsrd.conf. I figured I'd use the olsrd
796 name before somebody else started using it ;-)
801 New options: DEBUG, HNA6 and IPC-CONNECT added to config file.
806 A printf-wrapper has been introduced - debug level output handling
807 is much more uniform now.
808 The daemon should run fine in detached mode now(DEBUG 0)
812 The GUI front-end can now connect and disconnect at any time while the
813 daemon is running, if started using the -ipc switch or with IPC set to
814 'yes' in the configfile.
819 A small HNA bug fixed.
822 0.3.5 ---------------------------------------------------------------------
826 Forwarding jitter added. Messages are piggybacked if they arrive(and are to
827 be forwarded) while there is data to be forwarded buffered.
828 Added some bugfixes to support parsing of piggybacked messages as well.
832 Fixed route calculation so that 2 hop neighbors are added. This smooths
833 changes from 1 hop to 2 hop neighbor out. The old way one had to wait for
834 a TC before the 2 hop neighbors were added.
838 All neighbors received in HELLO messages are added to the two hop
839 neighborhood. This helps smoothing out the 1-to-2 hop transition as well.
843 MID calculation had to be updated due to the registering of two hop neighbors
844 that are already one hop neighbors. They should not be considered when calculating
849 Deletion of possible one hop neighbors registered on non main-addresses when
850 first registering MID info from a node removed. This can not occur due
851 to the fact that registering of neighbor nodes are done on main addresses
853 Option to not forward messages on wired links on which they arrived removed.
854 This is no longer usable to any degree when adding support for piggybacking
855 of forwarded messages is to be implemented.
859 Some unused parameters and commandline options were removed.
863 0.3.3 ---------------------------------------------------------------------
867 Added sending of empty TC messages if all MPR selectors are removed. Empty
868 TC messages are sent for a TC_HOLD_TIME period as described in section
873 Fixed HNA route calculations for IPv6. I forgot to upgrade this in 0.3.2
877 -hnaint and -midint command line optionas added to set the interval
878 of HNA and MID generation.
882 As an optimization messages have not been forwarded on the received interface
883 if this is registered as a non-WLAN interface. This causes problems for
884 people using Ethernet-to-WLAN adapters. This optimization is now turned
885 off by default. It can be activated using the -nofwlan option.
889 THERE ARE SOME NASTY BUGS IN 0.3.2!
890 Fixed a bug that caused 2 hop neighbors not to time out.
891 Fixed a bug that caused a 1 hop neighbor timeout not to recalculate
893 Fixed a small memleak in the MID set
894 Fixed some smaller bugs.
896 IPv6 functioning is not well tested in this release.
898 0.3.2 ---------------------------------------------------------------------
902 Updated HNA to be RFC compliant. This means that all received HNA tuples
903 are registered and only the subset of unique entries(net/netmask) with
904 the smallest hopcount is inserted into the routing table.
908 User can specify configfile name using the -f switch.
912 Fixed a link-sensing bug that caused problems when using MID nodes.
914 0.3.1 ---------------------------------------------------------------------
918 MPR calculation is now based on the willingness announced by nodes.
922 The neighbor set does not have timeouts on entries any more. Creation
923 and deletion of neighbor entries is done from the link-set as suggested
928 Gotten rid of a lot of code that became more or less obsolete due to
929 all the changes introduced in 0.3.0.
933 Fixed a nasty bug concerning the sequence numbering of TC packets.
934 Fixed some bugs regarding MPR calculation - and probably introduced
935 a whole new species when implementing the willingness-based calculation ;-)
938 0.3.0 ---------------------------------------------------------------------
940 Due to the extensive amount of updates this release is versioned 0.3.0
942 Duplicate table and forwarding
944 The duplicate table functionality is totally rewritten in 100% RFC
945 compliance. The forward algorithm specified in the RFC is implemented
946 this meant rewriting much of the packet processing code. The daemon
947 also forwards unknown packettypes now.
949 Link sensing and neighbor processing
951 Link sensing and neighbor processing was done in the same operation in the
952 old code. Link sensing is now a mechanism of its own which is 100% RFC
953 compliant. Neighbor processing and HELLO generation has been partly
954 rewritten to be RFC compliant. Neighbors are now registered as either
955 SYN or NOT_SYM. The NOT_NEIGH, SYM_NEIGH and MPR_NEIGH values are only
956 used when building HELLO messages. Links are in one of the following states:
957 UNSPEC_LINK, ASYM_LINK or SYM_LINK.
958 HELLO messages now advertise link status of neighbors on the interface
959 the message is transmitted.
963 A node now dynamically calculates willingness based on powersource and
964 possibly battery power. If the node is AC powered it announces a willingness
965 of 6. If batterypowered the willingness is calculated as:
967 Where P is percentage of power left.
971 The daemon now tries to read its configuration from the file /etc/uolsrd.conf
972 A "standard" configuration file is installed when doing 'make install'.
973 This file should be edited to fit your needs.
974 Command-line options can still be used to override the configuration form
975 the file(ore if no config file is present).
976 The -f switch can also be used to specify a configuration file.
980 If AdvancedPowerManagemant(APM) is supported on your system the willingness
981 of the node is dynamically calculated based upon the powerstatus of the node.
982 MPR calculation based upon willingness is not done as of yet.
986 A bugs in the TC processing fixed.
990 Some serious HNA bugs fixed. These bugs caused a node to always choos the
991 gateway with the larges hopcout :) More seriously - a bug caused looping
992 of HNA messages in certain scenarios.
994 Package sequence numbers
996 These were added. Not much use as of now - but they're there(as specified
1001 Users can now specify the broadcast address to use. Useful if one wishes to
1002 use the 255.255.255.255 broadcast.
1006 0.2.5 ---------------------------------------------------------------------
1010 Htime and Vtime processing and handling added. Holding times used to be
1011 a static value for all nodes. Now every node can signal its vlidity time
1013 To achieve this mantissa/exponent calculation functionality was added.
1014 Messages now include Vtime(and Htime in HELLO) values in mantissa/exponent
1015 format instead of just zero. These values are as stated above, used as holding
1017 the GUI should be upgraded as well...
1021 The use of jitter in message generation intervals vere fixed.
1024 0.2.4 ---------------------------------------------------------------------
1028 Some bugs concerning sequence numbers in HELLO and MID message handling
1029 was fixed. Newly registered nodes in the neighbor and MID sets were
1030 initialized with a seqno of 0. When using a "wraparound" sequencenumber
1031 check(as defined in olsr_protocol.h) this can produce errors if a new
1032 node joins a network where existing nodes has seqnos >0x00FF.
1036 Some checks and copying of node addresses where done using sizeof(u_olsr32_t)
1037 which is 32 bits. This caused only the 32 firs bits of IPv6 addresses to
1038 be copied and checked.