Brian Leonard wrote:
> e1000g0: flags=2004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500 index 2
> inet6 fe80::21c:7eff:fec3:41bc/10
> e1000g0:1: flags=2080841<UP,RUNNING,MULTICAST,ADDRCONF,IPv6> mtu 1500 index 2
> inet6 2002:47eb:2fa8:0:21c:7eff:fec3:41bc/64
That second address came from ADDRCONF (stateless address
autoconfiguration), which means that you either have a router on your
network advertising that network (it's a 6to4 prefix for 71.235.47.168,
if that helps) or you've got an /etc/inet/ndpd.conf entry that tells the
system to create this network.
You can learn more about stateless address autoconfiguration in the
ndpd.conf and in.ndpd man pages.
Note also that you've got DHCP set on the main interface (the one
without the ":" in the name). That means that either your local IPv6
router is telling you to run DHCPv6 (but you don't seem to be getting
addresses or prefixes to use from that service) or your local router was
down when this interface came up. It might be normal behavior,
depending on your situation, or if you were expecting more, it might be
something to look into.
> Notice the last entry, e1000g0:1, appears to be a logical IPv6 interface.
> It's not associated with a zone. However, I'm not able to manage it. For
> example, if I try to bring it down I get the following:
>
> bleon...@opensolaris:~$ pfexec ifconfig e1000g0:1 down
> ifconfig: setifflags: SIOCGLIFFLAGS: e1000g0:1: no such interface
If you want to manipulate an IPv6 interface, you'll have to tell
ifconfig that this is what you intend to do. Like this:
pfexec ifconfig e1000g0:1 inet6 down
IPv4 and IPv6 interfaces are distinct to the system; you can have
"e1000g0:1" for each address type, and they have nothing to do with each
other beyond sharing underlying hardware.
Note that you probably want "unplumb" rather than "down", but I guess
that's your choice.
_______________________________________________
networking-discuss mailing list
[email protected]
