Project

General

Profile

Regression #13248

Updated by Marcos M almost 2 years ago

After installing @22.05.b.20220531.0600@, I noticed that the @System / Routing@ logs showed the following: 

 * @2001:db8:4407:41c:20c:29ff:feae:75dc@ is the lan (ixv0) IPv6 address assigned from the tracked interface. 
 * @fe80::20c:29ff:feae:75dc@ is the lan (ixv0) Link-Local address. 
 * lan (ixv0) shows DHCPv6 Server and RA disabled in the GUI. The interface has @Tracked Interface@ set. 
 * ixv2/3/4/6 have DHCPv6 Server and RA enabled. The interface has IPv6 static addresses. 

 <pre> 
 Jun 5 13:03:26  	 radvd  	 51368  	 RDNSS address 2001:db8:4407:41c:20c:29ff:feae:75dc received on ixv0 from fe80::20c:29ff:feae:75dc is not advertised by us 
 Jun 5 13:03:26  	 radvd  	 51368  	 RDNSS address 2001:db8:4407:41c:20c:29ff:feae:75dc received on ixv4 from fe80::20c:29ff:feae:75dc is not advertised by us 
 Jun 5 13:03:26  	 radvd  	 51368  	 RDNSS address 2001:db8:4407:41c:20c:29ff:feae:75dc received on ixv2 from fe80::20c:29ff:feae:75dc is not advertised by us 
 Jun 5 13:03:26  	 radvd  	 51368  	 RDNSS address 2001:db8:4407:41c:20c:29ff:feae:75dc received on ixv3 from fe80::20c:29ff:feae:75dc is not advertised by us 
 Jun 5 13:03:26  	 radvd  	 51368  	 RDNSS address 2001:db8:4407:41c:20c:29ff:feae:75dc received on ixv6 from fe80::20c:29ff:feae:75dc is not advertised by us  
 </pre> 

 I also noticed that some hosts behind the firewall were getting two additional IPv6 addresses assigned from lan (ixv0), a separate interface which was using @Track Interface@, on top of the correct IPv6 address addressed leased by the DHCPv6 Server. 

 I rebooted and the issue persisted. I then re-saved the DHCPv6 Server and Router Advertisements config for @ixv5@ (the LAN which has @Tracked Interface@ set), and the issue was resolved. I ran a diff on the @config.xml@ file before and after the issue was resolved, and noticed that the difference was that the file contained an entry under @dhcpdv6@ for @lan@ (@ixv5@) with @<ramode>disabled</ramode>@ included. When I was experiencing the issue, the file did not contain any entry for @lan@ under @dhcpdv6@.

Back