Bug 159005
| Summary: | syntax error in /etc/radvd.conf, line 60: prefix | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Derek Poon <dpoon> | ||||
| Component: | radvd | Assignee: | Jason Vas Dias <jvdias> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Ben Levenson <benl> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | medium | ||||||
| Version: | 3 | CC: | pekkas | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | radvd-0.8-2 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2005-07-27 22:04:25 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
The radvd.conf EXAMPLE shipped with radvd-0.7.3 is shipped as %config(noreplace) , so if an /etc/radvd.conf existed previously, the new radvd.conf would be installed as /etc/radvd.conf.rpmnew . RPMs should never overwrite existing configuration files. Yes, the radvd.conf example for 0.7.2 will not work with 0.7.3 - copy /etc/radvd.conf.rpmnew to /etc/radvd.conf, and all should be OK - except you need to modify it to do something useful, not just provide examples of its syntax ! Let me know if you have any issues using the radvd.conf from 0.7.3 . That WAS the radvd.conf from 0.7.3-1_FC3, which I tried to use with radvd-0.7.3-1_FC3. # rm /etc/radvd.conf # rpm -Uvh --force radvd-0.7.3-1_FC3.i386.rpm # rpm -V radvd # service radvd restart was how I attained the error. Created attachment 114921 [details]
Default example radvd.conf file
I've attached the default EXAMPLE radvd.conf file.
NOTE: this is an EXAMPLE, which serves only to demonstrate the
syntax of radvd.conf, and is not meant to be used for a
real radvd configuration.
In future releases, I'll make /etc/radvd.conf an empty file with
the comment "# See /usr/share/doc/radvd*/radvd.conf.example", and
install the example radvd.conf as a %doc file .
Hi, I'm preparing for a new upstream radvd release. If you'd like to see some changes in the .spec file we ship, I'm open to suggestions (and/or patches :). FWIW, your idea about making radvd.conf basically empty seems OK, as there is not really such a thing as a working default radvd configuration.. Well, I did basically what you suggested in the just-released 0.8. This is now fixed in the current release of radvd : Rawhide: 0.8-2.FC5 FC4 : 0.8-2.FC4 FC3 : 0.8-2.FC3 |
From Bugzilla Helper: User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/412 (KHTML, like Gecko) Safari/412 Description of problem: As shipped, declarations in /etc/radvd.conf are in the wrong order. Out of the box configuration (excerpts): interface eth0 { # Example of a standard prefix prefix 3ffe:0302:0011:0002::/64 { ... }; # Example of a more specific route route 2001:db0:fff::/48 { ... }; # Example of a 6to4 prefix prefix 0:0:0:1234::/64 { ... }; }; Version-Release number of selected component (if applicable): radvd-0.7.3-1_FC3 How reproducible: Always Steps to Reproduce: With the out-of-the-box configuration (excerpts): interface eth0 { # Example of a standard prefix prefix 3ffe:0302:0011:0002::/64 { ... }; # Example of a more specific route route 2001:db0:fff::/48 { ... }; # Example of a 6to4 prefix prefix 0:0:0:1234::/64 { ... }; }; Run /sbin/service radvd start Actual Results: While trying to start radvd, the following errors appear in /var/log/messages: radvd[19980]: syntax error in /etc/radvd.conf, line 60: prefix radvd[19980]: syntax error in config file: /etc/radvd.conf radvd: radvd startup failed Expected Results: Simply rearranging the blocks lets it start up: interface eth0 { # Example of a standard prefix prefix 3ffe:0302:0011:0002::/64 { ... }; # Example of a 6to4 prefix prefix 0:0:0:1234::/64 { ... }; # Example of a more specific route route 2001:db0:fff::/48 { ... }; }; Additional info: