Home
last modified time | relevance | path

Searched hist:"259 d2d54" (Results 1 – 4 of 4) sorted by relevance

/freebsd/sys/net/
H A Dif_bridge.c259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
H A Dif_ethersubr.c259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
H A Dif.c259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]
/freebsd/sys/conf/
H A Dfiles259d2d54 Thu Jun 11 10:26:38 GMT 2009 Bjoern A. Zeeb <bz@FreeBSD.org> carp(4) allows people to share a set of IP addresses and can only
use IPv4/v6 for inter-node communication (according to my reading).

Properly wrap the carp callouts in INET || INET6 and refelect this
in sys/conf/files as well. While in theory this should be ok,
it might be a bit optimistic to think that carp could build with
inet6 only[1].

Discussed with: mlaier [1]