Open Radar

 
21-May-2008 01:41 PM Derek Morr:
Summary:

The ipconfig(8) command does not display IPv6 addresses when its getifaddr option is used. This occurs if the interface has both an IPv4 and and IPv6 address, or if the interface only has an IPv6 address.

Steps to reproduce:

1) Configure a routable IPv6 address on the interface

2) Run `ipconfig getifaddr <interface>`

Expected Results:

It should display the IPv6 address(es) configured on the interface:

E.g:

$ ipconfig getifaddr en0
128.118.27.75
2610:8:6800:1::408

Actual Results:

If the interface has an IPv4 address, only the IPv4 address is displayed:

$ ipconfig getifaddr en0
128.118.27.75

If the interface does not have an IPv4 address (e.g., it's on an IPv6-only network), ipconfig prints an error:

$ ipconfig getifaddr en1
get if addr en1 failed, (os/kern) failure

Regression:

N/A

Notes:

Here is sample ipconfig and ifconfig output from my machine, which has an IPv4 and and IPv6 address on en0:

$ ipconfig getifaddr en0
128.118.27.75

$ ifconfig en0
en0: flags=8863<UP,BROADCAST,SMART,RUNNING,SIMPLEX,MULTICAST> mtu 9000
	inet6 fe80::21d:4fff:fe49:36bc%en0 prefixlen 64 scopeid 0x4 
	inet6 2610:8:6800:1::408 prefixlen 64 
	inet 128.118.27.75 netmask 0xffffff80 broadcast 128.118.27.127
	ether 00:1d:4f:49:36:bc 
	media: autoselect (1000baseT <full-duplex,flow-control>) status: active
	supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control>

Here is sample output using interface en1, which only has IPv6 configured:

$ ipconfig getifaddr en1
get if addr en1 failed, (os/kern) failure

$ ifconfig en1
en1: flags=8963<UP,BROADCAST,SMART,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
	inet6 fe80::21d:4fff:fe49:36bd%en1 prefixlen 64 scopeid 0x5 
	inet6 2610:8:6800:4::507 prefixlen 64 
	ether 00:1d:4f:49:36:bd 
	media: 1000baseT <full-duplex> status: active
	supported media: autoselect 10baseT/UTP <half-duplex> 10baseT/UTP <full-duplex> 10baseT/UTP <full-duplex,hw-loopback> 10baseT/UTP <full-duplex,flow-control> 100baseTX <half-duplex> 100baseTX <full-duplex> 100baseTX <full-duplex,hw-loopback> 100baseTX <full-duplex,flow-control> 1000baseT <full-duplex> 1000baseT <full-duplex,hw-loopback> 1000baseT <full-duplex,flow-control>

21-May-2008 04:17 PM Vanaja Pasumarthi:
Engineering has determined that this issue behaves as intended based on the following information:
 
Yes, ipconfig is for IPv4 only right now.

21-May-2008 05:02 PM Derek Morr:
This isn't an acceptable response to my bug report. It's effectively dismissing the bug report.

At a minimum, the man page for ipconfig(8) should be updated to inform users that it's IPv4-only. Is there an open RFE for adding IPv6 support to ipconfig(8)?