Bug #5812
closed
RADVD starts at boot when it shouldn't
Added by Antonio Prado about 8 years ago. Updated about 8 years ago.
100%
Description
on a fresh installed box, IPv4 configured on LAN, IPv6
not configured, RADVD is active
Updated by Jim Thompson about 8 years ago
- Assignee set to Renato Botelho
assigned to Renato for eval
Updated by Renato Botelho about 8 years ago
Can you please share <interfaces> block of /cf/conf/config.xml?
Updated by Antonio Prado about 8 years ago
of course:
<interfaces>
<wan>
<enable/>
<if>lagg0</if>
<blockpriv/>
<blockbogons/>
<descr><![CDATA[WAN]]></descr>
<ipaddr>192.168.200.251</ipaddr>
<subnet>23</subnet>
<gateway>WANGW</gateway>
<spoofmac/>
</wan>
<lan>
<enable/>
<if>lagg1</if>
<ipaddr>172.31.150.251</ipaddr>
<subnet>24</subnet>
<ipaddrv6/>
<subnetv6/>
<media/>
<mediaopt/>
<track6-interface>wan</track6-interface>
<track6-prefix-id>0</track6-prefix-id>
<descr><![CDATA[LAN]]></descr>
<gateway/>
<gatewayv6/>
</lan>
</interfaces>
Updated by Renato Botelho about 8 years ago
Antonio Prado wrote:
of course:
<interfaces>
<wan>
<enable/>
<if>lagg0</if>
<blockpriv/>
<blockbogons/>
<descr><![CDATA[WAN]]></descr>
<ipaddr>192.168.200.251</ipaddr>
<subnet>23</subnet>
<gateway>WANGW</gateway>
<spoofmac/>
</wan>
<lan>
<enable/>
<if>lagg1</if>
<ipaddr>172.31.150.251</ipaddr>
<subnet>24</subnet>
<ipaddrv6/>
<subnetv6/>
<media/>
<mediaopt/>
<track6-interface>wan</track6-interface>
<track6-prefix-id>0</track6-prefix-id>
<descr><![CDATA[LAN]]></descr>
<gateway/>
<gatewayv6/>
</lan>
</interfaces>
For for evaluating, please change IPv6 configuration on LAN to 'none' and see if it goes away. I found 2 different possible bugs that are causing this, and will work on a fix
Updated by Antonio Prado about 8 years ago
Renato Botelho wrote:
For for evaluating, please change IPv6 configuration on LAN to 'none' and see if it goes away
double checked, with IPv6 configuration on LAN to 'none' does not change behavior: radvd continues advertising
Updated by Antonio Prado about 8 years ago
Renato Botelho wrote:
For for evaluating, please change IPv6 configuration on LAN to 'none' and see if it goes away
the only (weird) workaround is to uncheck Allow IPv6 under System: Advanced: Networking: IPv6 Options
Updated by Renato Botelho about 8 years ago
Antonio Prado wrote:
Renato Botelho wrote:
For for evaluating, please change IPv6 configuration on LAN to 'none' and see if it goes away
double checked, with IPv6 configuration on LAN to 'none' does not change behavior: radvd continues advertising
Can you please show me the content of radvd conf?
Updated by Antonio Prado about 8 years ago
Renato Botelho wrote:
Can you please show me the content of radvd conf?
here it is:
# Automatically Generated, do not edit
# Generated config for delegation from wan on lan
interface lagg1 {
AdvSendAdvert on;
MinRtrAdvInterval 3;
MaxRtrAdvInterval 10;
AdvLinkMTU 1500;
AdvOtherConfigFlag on;
prefix ::/64 {
AdvOnLink on;
AdvAutonomous on;
AdvRouterAddr on;
};
DNSSL example.net { };
};
Updated by Renato Botelho about 8 years ago
- Category set to Interfaces
- Status changed from New to Feedback
Your config looks wrong since you have <track6-interface> set but <ipaddrv6> is not track. I've pushed a better check to avoid this situation being culprit of starting radvd. Can you gitsync and try it please?
Updated by Antonio Prado about 8 years ago
Renato Botelho wrote:
Your config looks wrong
well, that's not my config actually. it's the default config.
Can you gitsync and try it please?
gitsync on a 2.2.6?
Updated by Renato Botelho about 8 years ago
- % Done changed from 0 to 100
Antonio Prado wrote:
Renato Botelho wrote:
Your config looks wrong
well, that's not my config actually. it's the default config.
Oh OK, thanks for the info. This fix will take care of it in this case.
Can you gitsync and try it please?
gitsync on a 2.2.6?
No, this fix was for 2.3.
I checked on a system with that config with and without the fix and it looks OK
Updated by Antonio Prado about 8 years ago
Renato Botelho wrote:
No, this fix was for 2.3.
my report was about 2.2.6
Updated by Chris Buechler about 8 years ago
- Status changed from Feedback to Resolved
- Affected Version set to All
Fixed.
Antonio Prado wrote:
my report was about 2.2.6
It's the same root issue, we're largely only fixing things in 2.3 at this stage. Just set your interface to IPv6 none if you don't want it to start, or the patch of the commit on here should be pretty easy to adapt to 2.2.6 if you want.