Age | Commit message (Collapse) | Author |
|
address of a interface could be used. Now it is possible to specify a
interface more than once if multiple networks are configured. An alternative
network can be specified via e.g. interface em0:10.0.5.1. The old interface
syntax without the IP still works and uses the main/first configured IP
address.
ospfd now needs to include the IP header on outgoing messages as it is not
possible to specifiy the source address in sendto(2). Additionally all
multicast joins and leaves have to be tracked.
OK norby@
|
|
This allows construct like these:
area 0.0.0.1 {
interface lo0
interface em1 { passive }
}
From Pierre-Yves Ritschard
|
|
From Pierre-Yves Ritschard
|
|
possible integer truncation because of the use of u_longs and u_int32_t in
the code. Initial diff by Pierre-Yves Ritschard but slightly modified version
commited.
|
|
range will match this "rule". This should be it, now it is time to write
some documentation.
|
|
routes via "no redistribute rtlabel admin". Redistribute rules are parsed
in order and the first match is used. Only exception is "redistribute default"
Which is independent of the other rules and can't be negated.
|
|
|
|
define which routes should be redistributed via OSPF. So now you can
define the export list on a fine graded basis. More to come... OK norby@
|
|
other things work. ok henning
|
|
global and per area defaults. With this it is now possible to define one
set of auth-md keys and use them in every defined interface. OK norby@
|
|
auth-type et al. to the main and area blocks. OK norby@
|
|
if iface is set and so the check is superfluous. OK norby@
|
|
c string with a lenght <= 8 with a buffer of size 8. Now in some cases
there can be trailing garbage after the c-string and so the bcmp() fails.
Found by Sergey Matveychuk who provided a similar patch.
OK norby@
|
|
|
|
|
|
not be used to connect to a OSPF cloud and forced to be passive. With this
ospfd will only announce the carp interface route if the interface is master.
So you can connect a LAN in a redundant way to your ospf backbone. OK norby@
|
|
Finaly implement clear_config(). OK norby@
|
|
|
|
ok claudio@
|
|
|
|
- remove rtr_id from struct iface we don't need to keep a copy of this value
per interface
- replace all references to iface->rtr_id.s_addr with calls to ospfe_rtr_id()
ok claudio@ norby@
|
|
Default to id 1 and mention it in the man page.
From a discussion with msf@ OK norby@
|
|
a {} block. Only drawback is that it is no longer possible to do
"interface em0\n{ ...".
OK henning@ norby@ some time ago
|
|
This makes it possible to have ospfd(8) parse a configuration file and
display the parsed result.
ok claudio@
|
|
ok claudio@
|
|
With "redistribute (static|connected|default|none)" it is possible to
tell ospfd which external routes should be announced.
Connected routes will be announced only if there is no corresponding
interface configured, in that case the prefix is not external.
Adding and removing of announced prefixes are done automaticaly.
OK norby@
|
|
Reworked by me.
ok claudio@
|
|
ok and input claudio@
|
|
From Jason Ackley (thanks).
ok claudio@
|
|
ok claudio@
|
|
ok henning@
|
|
ok henning@
|
|
by using the kif/kroute info while allocating interfaces.
|
|
Calculate Shortest Path Tree for each area known in the link state
database.
The Shortest Path Tree is used as input for route table calculation.
Route tabled is calculated and the result is inserted into the kernel
route table.
ok claudio@
|
|
ok claudio@ henning@
|
|
ok claudio@ henning@
|
|
do with this software, just happend to be my only valid email address at
the time.
|
|
started by Esben Norby some time ago by using the imsg/three process framework
of bgpd. He implemented the basic concept plus the ospf finite state machines.
Later I joined and helped him cleanup, debug and extend his work.
Right now it is not particularly useful, major parts are still missing but is
imported to allow more people to work on it.
status:
The basic protocol works for broadcast networks and the LS database is
synchronized and updated. It is not possible to be DR or BDR on a network
and other interface types like point-to-point are not yet supported.
The shortest path tree is not calculated and so no routing information is
exchanged with the kernel FIB.
Not yet connected to the builds.
OK henning@
|