Bug 4546 - Build Farm does not support IPv6
Build Farm does not support IPv6
Status: RESOLVED FIXED
Product: BuildFarm
Classification: Unclassified
Component: scripts
unspecified
Other All
: P3 normal
: ---
Assigned To: Samba Bugzilla Account
Samba QA Contact
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-04-25 06:20 UTC by David Holder
Modified: 2011-07-12 20:59 UTC (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Holder 2007-04-25 06:20:57 UTC
Build farm does not support IPv6. Socket wrapper needs to be modified to support IPv6 not just IPv4.
I doubt if I can help much with this one, but I am willing to try. Let me know if you have any IPv6 questions and I'll try to answer them.
Comment 1 Stefan Metzmacher 2007-04-26 05:49:12 UTC
In samba4 we have merge heimdal's version of socket_wrapper with very simple
(non multi interface) support and we need to expand that to support multiple
interfaces.

I thought about using
FE80::5357:5FXX /* Link-Local */

where XX will be the interface id

we can also think about using ::7F00:00XX to be able to bind to ipv4 addresses 
via the ipv6 name.


Comment 2 David Holder 2007-04-26 10:01:45 UTC
(In reply to comment #1)
> In samba4 we have merge heimdal's version of socket_wrapper with very simple
> (non multi interface) support and we need to expand that to support multiple
> interfaces.
> I thought about using
> FE80::5357:5FXX /* Link-Local */
> where XX will be the interface id
This might work. This would allow link-local and global addresses to use an interface id (the last 64 bits) where socket wrapper uses the last 8 bits to specify the interface.
> we can also think about using ::7F00:00XX to be able to bind to ipv4 addresses 
> via the ipv6 name.
This sounds wrong. ::/96 addresses are deprecated and were for 6over4 use. If you want to map to IPv4 addresses you should use IPv4-mapped IPv6 addresses that have a prefix of ::ffff:0/96. The last 32 bits then map to the IPv4 address, so you wouldn't have anywhere to put the interface address. But this doesn't matter as you only need to specify the interface on link-local addresses. Also you can work out the IPv4 interface from the IPv4 address!
Comment 3 David Holder 2007-04-26 10:05:08 UTC
(In reply to comment #2)
> (In reply to comment #1)
> > In samba4 we have merge heimdal's version of socket_wrapper with very simple
> > (non multi interface) support and we need to expand that to support multiple
> > interfaces.
> > I thought about using
> > FE80::5357:5FXX /* Link-Local */
> > where XX will be the interface id
> This might work. This would allow link-local and global addresses to use an
> interface id (the last 64 bits) where socket wrapper uses the last 8 bits to
> specify the interface.
> > we can also think about using ::7F00:00XX to be able to bind to ipv4 addresses 
> > via the ipv6 name.
> This sounds wrong. ::/96 addresses are deprecated and were for 6over4 use. If
> you want to map to IPv4 addresses you should use IPv4-mapped IPv6 addresses
> that have a prefix of ::ffff:0/96. The last 32 bits then map to the IPv4
> address, so you wouldn't have anywhere to put the interface address. But this
> doesn't matter as you only need to specify the interface on link-local
> addresses. Also you can work out the IPv4 interface from the IPv4 address!

Thinking about it you might need to support 6over4 addresses as they are still there on a number of platforms. But this isn't a problem as the IPv4 address still tells you which (IPv4) interface you are using. I am of the view that it would be a bad idea to run SMB over 6over4. I will need to check if Windows does this.
Comment 4 Stefan Metzmacher 2011-07-12 20:59:25 UTC
Socket_wrapper uses FD00::5357:5FXX