In article <[EMAIL PROTECTED]> (at Thu, 27 Jul 2000 16:28:48
-0500), "La Monte Henry Piggy Yarroll" <[EMAIL PROTECTED]> says:
> >> the v6 application could do this more simply by binding to the v4
> >> address (be it wildcard or not) in addition to any others.
> >
> >We cannot do this with Linux.
>
> I have not gotten into the v6 portions of the networking code, but
> what is the constraint?
Ipv6 tcp layer and ipv4 tcp layer are shared.
You cannot bind a ipv4 socket to a port already bound to ipv6 socket.
You cannot bind a ipv6 socket to a port already bound to ipv4 socket.
If you want to provide a service to ipv6 and ipv4 client through single
local port, you must create an ipv6 scoket and bind to that port;
ipv4 clients are serviced by ipv6 scoket through ipv4-mapped addresses.
We may be able to provide a new socket option that disables ipv4-mapped
feature, but I wonder application might abuse; create ipv6 socket, set
that sockopt and create ipv4 socket... then Linux cannot provide a service
to ipv4 clinets. please note this...
--
Hideaki YOSHIFUJI <[EMAIL PROTECTED]>
Web Page: http://www.ecei.tohoku.ac.jp/%7Eyoshfuji/
PGP5i FP: F731 6599 5EB2 BBA7 1515 1323 1806 A96F 5700 6B25
--------------------------------------------------------------------
IETF IPng Working Group Mailing List
IPng Home Page: http://playground.sun.com/ipng
FTP archive: ftp://playground.sun.com/pub/ipng
Direct all administrative requests to [EMAIL PROTECTED]
--------------------------------------------------------------------
