So here's the situation as it stands:
$ ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.0.1.98 netmask ff000000 broadcast 10.255.255.255
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu
8252 index 1
inet6 ::1/128
e1000g0: flags=2000840<RUNNING,MULTICAST,IPv6> mtu 1500 index 2
inet6 fe80::a00:27ff:fe90:fff2/10
$ svcs -l ndp
fmri svc:/network/routing/ndp:default
name in.ndpd IPv6 neighbour discovery daemon
enabled true (temporary)
state online
next_state none
state_time July 6, 2010 09:12:19 PM EDT
logfile /var/svc/log/network-routing-ndp:default.log
restarter svc:/system/svc/restarter:default
contract_id 65
dependency require_all/refresh svc:/network/routing-setup (online)
$ ls -l /etc/inet/ndpd.conf
ls: cannot access /etc/inet/ndpd.conf: No such file or directory
$ cat /etc/hostname6.e1000g0
opensolaris
In order to duplicate a situation I had believed I observed before, I
deleted /etc/hostname6.e1000g0 and rebooted.
After reboot:
$ ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.0.1.98 netmask ff000000 broadcast 10.255.255.255
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu
8252 index 1
inet6 ::1/128
Manually configuring:
$ pfexec ifconfig e1000g0 inet6 plumb
$ pfexec ifconfig e1000g0 inet6 up
Result (it works!):
$ ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
8232 index 1
inet 127.0.0.1 netmask ff000000
e1000g0: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet 10.0.1.98 netmask ff000000 broadcast 10.255.255.255
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu
8252 index 1
inet6 ::1/128
e1000g0: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2
inet6 fe80::a00:27ff:fe90:fff2/10
e1000g0:1: flags=2080841<UP,RUNNING,MULTICAST,ADDRCONF,IPv6> mtu 1500 index 2
inet6 2001:GHIJ:KLMN:OPQR:a00:27ff:fe90:fff2/64
So the question is, why does "manual" configuration work but not
configuration at boot time?
On Tue, Jul 6, 2010 at 12:11 PM, Patrick O'Sullivan
<ir...@insaneirish.com> wrote:
> Thanks all for the very helpful hints.
>
> I will try when I'm home this evening.
>
> On Jul 6, 2010, at 11:20, Vasumathi Sundaram <vasumathi.sunda...@oracle.com>
> wrote:
>
>> On 07/ 6/10 10:59 AM, Patrick O'Sullivan wrote:
>>> I have a b134 machine that I'd like to get participating in my IPv6 network
>>> using auto configuration.
>>>
>>> By creating /etc/hostname6.e1000g0 I've been able to get the interface to
>>> have a fe80::/10 address. However, I have a router on the subnet sending
>>> advertisements for a proper /64 and I'd like that to auto configure as well.
>>>
>>> Do I need to create another hostname6 file for a e1000g0:1 interface?
>>>
>>>
>>
>> If you have /etc/hostname6.e1000g0 and the router is sending out
>> advertisements, then you should automatically get the addresses
>> auto-configured as soon as the interface is up. You do not need to have a
>> separate hostname6 file for e1000g0:1.
>>
>> If you do not get any addresses auto-configured,
>> - check if the service svc:/network/routing/ndp:default is running
>> - check if you have the file /etc/inet/ndpd.conf. If you don't have the
>> file, it is ok. If the file is present, make sure that the parameter
>> "StatelessAddrConf" is not set to "false". For more information, refer to
>> man page for ndpd.conf(4).
>>
>>
>> Vasumathi
>>
>
_______________________________________________
networking-discuss mailing list
networking-discuss@opensolaris.org
