Problem with dhcpd6 configuration

Simon Hobson dhcp1 at thehobsons.co.uk
Mon Oct 3 21:32:37 UTC 2011


scott_stone at trendmicro.com wrote:

>Here's the interface configuration (the 'fffa' and 'fffb' addresses 
>were added by us, the 'scope link' and 'scope global dynamic' seem 
>to be getting auto-set).
>
>6: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast qlen 1000
>     link/ether 00:26:9e:58:48:30 brd ff:ff:ff:ff:ff:ff
>     inet 10.31.55.241/24 brd 10.31.55.255 scope global eth4
>     inet 10.31.55.244/24 brd 10.31.55.255 scope global secondary eth4:0
>     inet6 2620:101:4037:3b05:226:9eff:fe58:4830/64 scope global dynamic
>        valid_lft 2591861sec preferred_lft 604661sec
>     inet6 2620:101:4037:3b05:fffa::1/64 scope global
>        valid_lft forever preferred_lft forever
>     inet6 2620:101:4037:3b05:fffb::1/64 scope global
>        valid_lft forever preferred_lft forever
>     inet6 fe80::226:9eff:fe58:4830/64 scope link
>        valid_lft forever preferred_lft forever

At a rough guess, you've a router advertising routes and the server 
is self-configuring an interface - which is normal. 
226:9eff:fe58:4830 is a self assigned local part derived from the MAC 
address 00:26:9e:58:48:30 with a bit flipped and ff:fe stuck in the 
middle - you see the same with the link-local address (fe80:: prefix) 
which is always created on IPv6 interface.

Can't help with the rest of the problem though - you are starting the 
daemon with the "use IPv6" option aren't you ?

-- 
Simon Hobson

Visit http://www.magpiesnestpublishing.co.uk/ for books by acclaimed
author Gladys Hobson. Novels - poetry - short stories - ideal as
Christmas stocking fillers. Some available as e-books.



More information about the dhcp-users mailing list