My Oracle Support Banner

The Command "ifconfig -a" Still Shows Ipv6 Addressing On S11 When "Ipadm" Don't (Doc ID 2085084.1)

Last updated on FEBRUARY 03, 2019

Applies to:

Solaris Operating System - Version 11.2 and later
Information in this document applies to any platform.

Symptoms

Even after deleting the ipv6 address from the ipadm, its still reflects on the ifconfig output .

# ipadm
NAME CLASS/TYPE STATE UNDER ADDR
lo0 loopback ok -- --
  lo0/v4 static ok -- 127.0.0.1/8
  lo0/v6 static ok -- ::1/128
net0 ip ok -- --
  net0/v4 static ok -- X.Y.Z.81/24


# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
  inet 127.0.0.1 netmask ff000000
net0: flags=100001000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,PHYSRUNNING> mtu 1500 index 2
  inet X.Y.Z.81 netmask ffffff00 broadcast X.Y.Z.255
  ether a1:b1:c1:d1:e1:f1
lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
  inet6 ::1/128
net0: flags=120002000840<RUNNING,MULTICAST,IPv6,PHYSRUNNING> mtu 1500 index 2
  inet6 ::/0
  ether a1:b1:c1:d1:e1:f1


# ipadm delete-addr lo0/v6


# ipadm
NAME CLASS/TYPE STATE UNDER ADDR
lo0 loopback ok -- --
  lo0/v4 static ok -- 127.0.0.1/8
net0 ip ok -- --
  net0/v4 static ok -- X.Y.Z.81/24

   Ipadm DO NOT show any ipv6 addressing any more, event the loopback is gone.

# ifconfig -a
lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 index 1
  inet 127.0.0.1 netmask ff000000
net0: flags=100001000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4,PHYSRUNNING> mtu 1500 index 2
  inet X.Y.Z.81 netmask ffffff00 broadcast X.Y.Z.255
  ether a1:b1:c1:d1:e1:f1
lo0: flags=2002000848<LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu 8252 index 1
  inet6 ::/128
net0: flags=120002000840<RUNNING,MULTICAST,IPv6,PHYSRUNNING> mtu 1500 index 2
  inet6 ::/0
  ether a1:b1:c1:d1:e1:f1

  Ifconfig CONTINUE to show ipv6 addressing.

Changes

 

It used to be configurable in file /etc/default/inet_type in previous solaris 11 versions.

But that file has disappeared in solaris 11.2 (at least).

Cause

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Symptoms
Changes
Cause
Solution
References


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.