 | IAPrefix into radvd.conf and interface configuration I'm working on my Debian router and I'm trying to figure out the best way to get an IAPrefix published by a DHCPv6 server into the interface configuration and radvd.conf. The best solution I can figure out is to write a script to parse the dhcp logs and insert the prefix into the LAN interface and radvd.conf file. While this approach would work, I feel it's a bit hacky. Any way to use the configuration of radvd or the interface settings to accomplish this for me? |
|

2 recommendations | Have you tried setting the prefix in radvd.conf to ::/64 ?
said by radvd.conf(5) : Prefix definitions are of the form:
prefix prefix/length { list of prefix specific options };
Prefix can be network prefix or the address of the inferface. The address of interface should be used when using Mobile IPv6 extensions.
Special prefix "::/64" is also supported on systems that implement getifaddrs() (on other systems, configuration activation fails and radvd exits). When configured, radvd picks all non-link-local prefix assigned to the interface and starts advertising it. This may be applicable in non-6to4 scenarios where the upstream prefix might change. This option is incompatible with Base6to4Interface option. AdvRouterAddr option is always enabled when this configuration is used. /M |
|
|
|
 | Thanks! That works beautifully for radvd. Still having trouble with the interface portion though. |
|
 1 edit | What DHCPv6 client are you using? I'm using WIDE-DHCPv6 and it Just Works without anything special.
My dhcp6c.conf for requesting 2 /64's from Comcast:
interface vlan100 {
send ia-pd 1;
send ia-pd 2;
send ia-na 3;
send rapid-commit;
request domain-name-servers;
script "/usr/local/sbin/w-dhcp6c-state";
};
id-assoc pd 1 {
prefix-interface vlan70 {
sla-id 1;
sla-len 0;
};
};
id-assoc pd 2 {
prefix-interface vlan9 {
sla-id 2;
sla-len 0;
};
};
id-assoc na 3 { };
Launched with: /usr/local/sbin/dhcp6c -d -D -c /usr/local/etc/dhcp6c.conf vlan100
/usr/local/sbin/w-dhcp6c-state just logs some stuff:
#!/bin/sh
echo $* >/tmp/w-dhcpc-out
env >>/tmp/w-dhcpc-out
$ cat /tmp/w-dhcpc-out
REASON=NBI
PWD=/
new_domain_name_servers=2001:558:feed::2 2001:558:feed::1
SHLVL=1
_=/bin/env
/M |
|
 | For simplicity reason, I'm avoiding WIDE-DHCPv6 D:
I'm currently just using the dhcp client and config that comes with Debian. |
|
 | After many, many hours of fighting the ISC client, recompiling, patching, trying different versions, etc I gave up and installed WIDE. It was quick and painless to install from source compared to the hell I went through fighting that other one.
/M |
|
 | Sounds good. I'll give it a try and let you know how it goes. Thanks again. |
|
 NetDogPremium,VIP join:2002-03-04 Parker, CO kudos:49 Reviews:
·Comcast
| reply to mackey
said by mackey:What DHCPv6 client are you using? I'm using WIDE-DHCPv6 and it Just Works without anything special.
My dhcp6c.conf for requesting 2 /64's from Comcast:
You shouldn't be requesting 2 /64's but one /63 or /60.. -- Comcaster.. Network Engineer with NETO |
|
 | Yeah but requesting a /60 didn't work but requesting 2 /64's did, and as it works I never bothered to go back and check to see if requesting a /60 actually works yet. Even if it does, who knows when another problem will pop up and get it shut back off again.
/M |
|
 NetDogPremium,VIP join:2002-03-04 Parker, CO kudos:49 Reviews:
·Comcast
| said by mackey:Yeah but requesting a /60 didn't work but requesting 2 /64's did, and as it works I never bothered to go back and check to see if requesting a /60 actually works yet. Even if it does, who knows when another problem will pop up and get it shut back off again.
/M
PM Me your CM-MAC I will take a look and see if it is supported in your area yet. We do have 2 areas not supported.. -- Comcaster.. Network Engineer with NETO |
|