Solaris

How about:

Code:

/etc/defaultrouter6

as in "router" with 'r' at the end.

Even so, try creating it and see what happens.
Can always remove it if it doesn't work.

---------- Post updated at 08:05 PM ---------- Previous update was at 08:02 PM ----------

And when you say that you can't ping your router, how are you doing that?

By ip address or by name? If by name, that would need successful resolution. Does the name appear in /etc/inet/hosts?

I have added /etc/defaultrouter6 and it does not do anything to get rid of my additional igb:2, igb:3 interfaces. However, this does not break anything. I am able still able to ping myself and the gateway. I am pinging the addresses via IP address.

---------- Post updated at 09:44 AM ---------- Previous update was at 08:22 AM ----------

I just realized this might help provide some more information. I am tyring to get this to work on a non global zone running solaris 10. My production server that "works" that I have been comparing against is a xen instance of Solaris 10 virutal machine running on a Oracle Linux server. Maybe my issue is something related to global and non global zones. At this time I do not have the global zone configured with IPv6 at all. I am going to configure it and report back.

Clarification - A /etc/hostname.<interface> file can contain an IP address instead of a hostname.

I've re-read the thread from the beginning and I think we need to ensure that the concepts are understood here to ensure that we're not missing the point(s).

To save me explaining (yes, I'm lazy) I'll provide a link:

Configuring a virtual interface in Solaris

Please post back any progress or lack of progress.

First an update. I have figured out that one of the additional interfaces was due to an additional subnet being configured on the cisco router. When that was removed I only got one additional virtual interface igb1:2 when I reconfigured the interface. However that shows up as NOLOCAL, and according to the ifconfig man page thats a on-link subnet.

What is that and what is it used for? I am assuming it is has something to do with the link local address but what and why? I dont see anywhere that states what the purpose of that NOLOCAL or on-link subnet serves. Below is my current ifconfig when restarting /network/physical.

Code:

ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
inet 127.0.0.1 netmask ff000000 
igb1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2
inet x.y.10.41 netmask ffffff00 broadcast x.y.10.255
ether 0:21:28:c0:ad:2b 
igb1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2
inet6 fe80::221:28ff:fec0:ad2b/10 
ether 0:21:28:c0:ad:2b 
igb1:1: flags=2000841<UP,RUNNING,MULTICAST,IPv6> mtu 1500 index 2
inet6 x:y:z:2302::41/64 
igb1:2: flags=20a0841<UP,RUNNING,MULTICAST,NOLOCAL,ADDRCONF,IPv6> mtu 1500 index 2
inet6 subnet x:y:z:2302::/64

My next discovery is that the servers are connected to different devices. The "working" production server is using a McAfee firewall as its default route and the "nonworking/extra interface" server is using a cisco router as its default route.

The cisco router is set to supress all autoconfiguration for ipv6 and I believe that my /etc/inet/ndpd.conf is setup correctly to stop ipv6 autoconfiguration. So with that being said why does the server act differently when connect to the McAfee firewall? I was told that nothing was done special on the firewall for a configuration.

It appears that in.ndpd by default creates an on-link prefix when it receives a Router Advertisement and it sees that StatelessAddrConf is set to false in ndpd.conf. The only way to prevent the on-link prefix from being created is to disable the network/ndp service.

So it is acting as intended.