Project

General

Profile

Actions

Bug #3408

closed

IPV6 DHCP not disabling on initial setup

Added by Matthew Hoberg almost 11 years ago. Updated about 10 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
DHCP (IPv4)
Target version:
-
Start date:
01/22/2014
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:
amd64

Description

Installing fresh copy of v2.1 with 1 WAN and 1 LAN adapter. Install to hard drive and after rebooting during initial configuration change/setup static IPV4 & IPV6 on LAN. Choose option to disable DHCP for IPV4 & IPV6. DHCP is disabled for IPV4 but does not disable for IPV6.

Actions #1

Updated by Renato Botelho almost 11 years ago

  • Category set to DHCP (IPv4)

I could not reproduce it on a recent 2.1.1 snapshot. I'm wondering how could it put a range on dhcpv6 if you don't choose one? Could you share <dhcpdv6> block of your config.xml?

Actions #2

Updated by Matthew Hoberg almost 11 years ago

This is what was entered in the config on a fresh install of 2.1 not 2.1.1.
It seems to automatically enter the range into the config during the setup. This was done from the console and option #2 "Set interface(s) IP address" after a fresh install.

&lt;dhcpdv6&gt;
&lt;lan&gt;
&lt;ramode&gt;managed&lt;/ramode&gt;
&lt;rapriority&gt;low&lt;/rapriority&gt;
&lt;rainterface/&gt;
&lt;radomainsearchlist/&gt;
&lt;range&gt;
&lt;from&gt;2001:470:xxxx:1::1000&lt;/from&gt;
&lt;to&gt;2001:470:xxxx:1::2000&lt;/to&gt;
&lt;/range&gt;
&lt;prefixrange&gt;
&lt;from/&gt;
&lt;to/&gt;
&lt;prefixlength&gt;48&lt;/prefixlength&gt;
&lt;/prefixrange&gt;
&lt;defaultleasetime/&gt;
&lt;maxleasetime/&gt;
&lt;netmask/&gt;
&lt;domain/&gt;
&lt;domainsearchlist/&gt;
&lt;ddnsdomain/&gt;
&lt;tftp/&gt;
&lt;ldap/&gt;
&lt;nextserver/&gt;
&lt;filename/&gt;
&lt;rootpath/&gt;
&lt;dhcpv6leaseinlocaltime/&gt;
&lt;numberoptions/&gt;
&lt;/lan&gt;
&lt;/dhcpdv6&gt;
Actions #3

Updated by Chris Buechler about 10 years ago

  • Status changed from New to Closed

issue as described doesn't exist in 2.2

Actions

Also available in: Atom PDF