similar to: [Bug 534] No option to use IPv6 connections by default

http://bugzilla.mindrot.org/show_bug.cgi?id=535 Summary: Wrong information in manual page about -6 option. Product: Portable OpenSSH Version: 3.5p1 Platform: ix86 OS/Version: Linux Status: NEW Severity: trivial Priority: P3 Component: ssh AssignedTo: openssh-unix-dev at mindrot.org

http://bugzilla.mindrot.org/show_bug.cgi?id=534 ------- Additional Comments From djm at mindrot.org 2003-05-16 10:50 ------- Created an attachment (id=303) --> (http://bugzilla.mindrot.org/attachment.cgi?id=303&action=view) Adds AddressFamily option to client ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee.

http://bugzilla.mindrot.org/show_bug.cgi?id=534 brent at graveland.net changed: What |Removed |Added ---------------------------------------------------------------------------- Status|RESOLVED |REOPENED Resolution|FIXED | ------- Additional Comments From brent at graveland.net 2003-06-23 09:29

http://bugzilla.mindrot.org/show_bug.cgi?id=451 Summary: new config-Option: IPv4or6 Product: Portable OpenSSH Version: 3.5p1 Platform: All URL: http://www.toppoint.de/~wklaebe/ipv4or6-config- 3.5p1.diff OS/Version: All Status: NEW Severity: enhancement Priority: P2

http://bugzilla.netfilter.org/show_bug.cgi?id=616 Summary: Duplicate rules for multi-homed hostnames. IPv4 and IPv6 inconsistent treatment. Product: iptables Version: unspecified Platform: i386 OS/Version: All Status: NEW Severity: minor Priority: P4 Component: iptables

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:06.ipv6 Security Advisory The FreeBSD Project Topic: setsockopt(2) IPv6 sockets input validation error Category: core Module: kernel

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-04:06.ipv6 Security Advisory The FreeBSD Project Topic: setsockopt(2) IPv6 sockets input validation error Category: core Module: kernel

On Saturday 11 December 2004 07:56, j@v2v.cc wrote: > right now icecast2 listens to 0.0.0.0 by default if bind-address is not > defined. it should rather listen to :: if ipv6 is available. > the change is rather small. i do not know how that works on systems that > do not support IPv6 yet. > so i added #ifdef AF_INET6, is that the right way to check for ipv6? > > attached is a

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:03.ipv6 Security Advisory The FreeBSD Project Topic: IPv6 Routing Header 0 is dangerous Category: core Module: ipv6 Announced:

right now icecast2 listens to 0.0.0.0 by default if bind-address is not defined. it should rather listen to :: if ipv6 is available. the change is rather small. i do not know how that works on systems that do not support IPv6 yet. so i added #ifdef AF_INET6, is that the right way to check for ipv6? attached is a patch against http://svn.xiph.org/icecast/trunk/net/ if it is ok like that it would

https://bugzilla.netfilter.org/show_bug.cgi?id=841 Summary: Specifying netmask option when creating ipv6 hash:ip is inconsistent Product: ipset Version: unspecified Platform: All OS/Version: All Status: NEW Severity: minor Priority: P5 Component: default AssignedTo:

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 ============================================================================= FreeBSD-SA-07:03.ipv6 Security Advisory The FreeBSD Project Topic: IPv6 Routing Header 0 is dangerous Category: core Module: ipv6 Announced:

https://bugzilla.samba.org/show_bug.cgi?id=4907 Summary: --disable-ipv6 disables -4 option Product: rsync Version: 2.6.9 Platform: Other OS/Version: Linux Status: NEW Severity: trivial Priority: P3 Component: core AssignedTo: wayned@samba.org ReportedBy: safari-samba-bugzilla-

http://bugzilla.netfilter.org/show_bug.cgi?id=588 Summary: make ipv6 optional in iptables Product: iptables Version: CVS (please indicate timestamp) Platform: All OS/Version: All Status: NEW Severity: enhancement Priority: P1 Component: ip6tables AssignedTo: laforge at netfilter.org

Hello, when I have this in /etc/sysconfig/network-scripts/ifcfg-eth0 TYPE=Ethernet NAME=eth0 NM_CONTROLLED=no ONBOOT=yes DEVICE=eth0 USERCTL=no ... IPV6INIT=yes IPV6ADDR=2001:DB8:DEAD:BEEF::10 IPV6ADDR_SECONDARIES="2001:DB8:DEAD:BEEF::20 2001:DB8:DEAD:BEEF::30 2001:DB8:DEAD:BEEF::40 2001:DB8:DEAD:BEEF::50" IPV6_AUTOCONF=no IPV6_DEFAULTGW=2001:DB8:DEAD:BEEF::1 IPV6_DEFAULTDEV=eth0 I

--- tests/Makefile.am | 4 +-- tests/{test-ipv4.sh => test-ip.sh} | 51 +++++++++++++++++++++++++++----------- tests/test-socket-activation.c | 2 +- 3 files changed, 40 insertions(+), 17 deletions(-) diff --git a/tests/Makefile.am b/tests/Makefile.am index 89ceb9d..9be57e6 100644 --- a/tests/Makefile.am +++ b/tests/Makefile.am @@ -50,7 +50,7 @@ EXTRA_DIST = \

http://bugzilla.mindrot.org/show_bug.cgi?id=401 ------- Additional Comments From yoshfuji at linux-ipv6.org 2003-01-06 12:20 ------- Created an attachment (id=194) --> (http://bugzilla.mindrot.org/attachment.cgi?id=194&action=view) patch to run openssh-3.5p1 on linux-2.2 & glibc-2.2(or later) This is modified patch for openssh-3.5p1. Patch is simplified. ------- You are

On Fri, Mar 04, 2016 at 12:16:37PM -0800, Dave Taht wrote: > I have been gradually moving more tinc servers over to ipv6 addresses > on the tinc 1.1 branch. > > Tinc is inserting a default route for ipv6 for some reason... > > default via 2600:3c01:e030:f2::1 dev tinc6 proto static metric 950 > pref medium > > In my case the default route supplied by ra is still

I have two installations of dovecot 2.18, apart from the necessary changes to allow them to replicate amongst themselves the configs are identical. Both are running Ubuntu 14.04 and are kept up to date. One is running 64bit and the other 32 bit (for historical reasons). Both have ipv4 and ipv6 addresses. The 64 bit installation allows access on port 143 and 993 on both ipv4 and ipv6. The 32

I have been gradually moving more tinc servers over to ipv6 addresses on the tinc 1.1 branch. Tinc is inserting a default route for ipv6 for some reason... default via 2600:3c01:e030:f2::1 dev tinc6 proto static metric 950 pref medium In my case the default route supplied by ra is still the correct thing, but I don't see where in the code tinc is inserting this route from.... which, as