Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug
report.
http://bugzilla.quagga.net/show_bug.cgi?id=442
Summary: ripd packet debug option refuses daemon to start
Product: Quagga
Version: 0.99.9
Platform: All
OS/Version: All
Status: NEW
Severity: major
Priority: Very High
Component: ripd
AssignedTo: maintainers@quagga.net
ReportedBy: ch@debian.org
As reported by Andreas Unterkircher <unki@netshadow.at> to the Debian bug
reporting system (http://bugs.debian.org/469346).
bye,
-christian-
------------------------ original report follows --------------
Quagga's ripd provides the possibility to turn on debugging which will
show up and explain received and sent RIP packets. To enable this kind
of debugging, you have to enter the following two lines into ripd's
configuration:
myrouter# conf t
myrouter(config)# debug rip packet recv detail
myrouter(config)# debug rip packet send detail
myrouter(config)# exit
myrouter#
If you now show the current config with "show running-config", only one
additional line appears in the config which says:
myrouter# show running-conig
...
debug rip packet detail
...
Note that "recv" and "send" are gone (looks like some aggregation).
Anyway, if you store now running-config with "write" into the
config-file "/etc/quagga/ripd.conf" and afterwards restart ripd,
it will spit out the following error message:
myrouter:~# /etc/init.d/quagga restart ripd
Stopping Quagga daemons (prio:0): (ripd).
Removing all routes made by zebra.
Nothing to flush.
Loading capability module if not yet done.
Starting Quagga daemons (prio:10): ripdThere is no such command.
Error occured during reading below line.
debug rip packet detail
To get around this bug, you have to open ripd.conf with an editor and
manually remove the line. Afterwards ripd will start up smoothly.
A nasty bug, if you forgot to disable debugging, stored the config
and reboot your machine - if you really depend on ripd, then the machine
will not fully come back on the network, because ripd fails.
At the end of this post [1] it was noted, but not answered later.
[1]
http://lists.quagga.net/pipermail/quagga-users/2005-September/005406.html
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
Quagga-bugs mailing list
Quagga-bugs@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-bugs
comments should be made in the comments box of this bug
report.
http://bugzilla.quagga.net/show_bug.cgi?id=442
Summary: ripd packet debug option refuses daemon to start
Product: Quagga
Version: 0.99.9
Platform: All
OS/Version: All
Status: NEW
Severity: major
Priority: Very High
Component: ripd
AssignedTo: maintainers@quagga.net
ReportedBy: ch@debian.org
As reported by Andreas Unterkircher <unki@netshadow.at> to the Debian bug
reporting system (http://bugs.debian.org/469346).
bye,
-christian-
------------------------ original report follows --------------
Quagga's ripd provides the possibility to turn on debugging which will
show up and explain received and sent RIP packets. To enable this kind
of debugging, you have to enter the following two lines into ripd's
configuration:
myrouter# conf t
myrouter(config)# debug rip packet recv detail
myrouter(config)# debug rip packet send detail
myrouter(config)# exit
myrouter#
If you now show the current config with "show running-config", only one
additional line appears in the config which says:
myrouter# show running-conig
...
debug rip packet detail
...
Note that "recv" and "send" are gone (looks like some aggregation).
Anyway, if you store now running-config with "write" into the
config-file "/etc/quagga/ripd.conf" and afterwards restart ripd,
it will spit out the following error message:
myrouter:~# /etc/init.d/quagga restart ripd
Stopping Quagga daemons (prio:0): (ripd).
Removing all routes made by zebra.
Nothing to flush.
Loading capability module if not yet done.
Starting Quagga daemons (prio:10): ripdThere is no such command.
Error occured during reading below line.
debug rip packet detail
To get around this bug, you have to open ripd.conf with an editor and
manually remove the line. Afterwards ripd will start up smoothly.
A nasty bug, if you forgot to disable debugging, stored the config
and reboot your machine - if you really depend on ripd, then the machine
will not fully come back on the network, because ripd fails.
At the end of this post [1] it was noted, but not answered later.
[1]
http://lists.quagga.net/pipermail/quagga-users/2005-September/005406.html
------- You are receiving this mail because: -------
You are on the CC list for the bug, or are watching someone who is.
_______________________________________________
Quagga-bugs mailing list
Quagga-bugs@lists.quagga.net
http://lists.quagga.net/mailman/listinfo/quagga-bugs