Displaying 11 results from an estimated 11 matches for "bindv6on".
Did you mean:
bindv6only
2011 Jun 06
2
Using Icecast over IPv6
Hi,
Thanks for the quick answer!
On Mon, 6 Jun 2011, Thomas.Rucker at tieto.com wrote:
> To your problem there are two approaches:
> - bind explicitly to :: and to 0.0.0.0 (so an ipv4 and a separate ipv6 bind)
> - change your sysctl.conf to contain: "net.ipv6.bindv6only = 0"
hmmm. OK but this implies (does it not) that
/proc/sys/net/ipv6/bindv6only should now contain something other than 0.
It doesn't (i.e. it does contain 0).
> If you opt for the latter don't forget to reload sysctl settings or
> change that option using the 'sysctl...
2011 Jun 06
0
Using Icecast over IPv6
...Icecast] Using Icecast over IPv6
>On Mon, 6 Jun 2011, Thomas.Rucker at tieto.com wrote:
>
>> To your problem there are two approaches:
>> - bind explicitly to :: and to 0.0.0.0 (so an ipv4 and a separate ipv6
>bind)
>> - change your sysctl.conf to contain: "net.ipv6.bindv6only = 0"
>
>hmmm. OK but this implies (does it not) that
>/proc/sys/net/ipv6/bindv6only should now contain something other than 0.
>It doesn't (i.e. it does contain 0).
Huh? Then we might be onto something different.
It's been ages since we sat down and fixed icecast to bin...
2011 Jun 06
3
Using Icecast over IPv6
Hi,
I realise this might be a Debian-specific question.
I've got access to two hosts which have IPv6 connectivity, both of which
are running Icecast 2.3.2. One is still running Debian Lenny and can be
reached via IPv6 just fine, but the other is running Debian Squeeze and
cannot. In addition, my local server which does not have IPv6 conectivity
to the Internet but which can be reached
2010 Aug 20
1
smbd version 3.5.4-62.fc13 can NOT bind to IPv4 endpoint( 0.0.0.0:445 ), but it bind to IPv6 endpoint ( :::445 )
....0.0.
Error = Address already in use
smbd_open_once_socket: open_socket_in: Address already in use
bind failed on port 139 socket_addr = 0.0.0.0.
Error = Address already in use
smbd_open_once_socket: open_socket_in: Address already in use
waiting for connections
^C
but I found after I turn on the bindv6only kernel var, then I can bind both
IPv4 and IPv6 port. like this:
# echo 1 > /proc/sys/net/ipv6/bindv6only
then It works as follows:
# smbd -Fi -d 2
smbd version 3.5.4-62.fc13 started.
Copyright Andrew Tridgell and the Samba Team 1992-2010
uid=0 gid=0 euid=0 egid=0
rlimit_max: rlimit_max (1024...
2017 Jul 28
4
firewalld and LISTEN
On CentOS7 I have following firewalld setting.
external (active)
target: default
icmp-block-inversion: no
interfaces: eth0
sources:
services: dns ftp http https imaps pop3s smtp ssh
ports: 110/tcp 21/tcp 20000/tcp 106/tcp 53/tcp 990/tcp 5432/tcp 8447/tcp
113/tcp 143/tcp 3306/tcp 5224/tcp 22/tcp 465/tcp 995/tcp 25/tcp 10000/tcp
8443/tcp 993/tcp 443/tcp 8880/tcp 587/tcp 20/tcp 53/udp
2017 Jul 28
0
firewalld and LISTEN
...0 128 :::443 :::*
By default, Linux processes that listen on an IPv6 port will also listen
on the IPv4 port (when no specific address is specified):
http://man7.org/linux/man-pages/man7/ipv6.7.html
You could change that behavior by modifying
/proc/sys/net/ipv6/bindv6only, but your system is working normally now.
2013 Mar 21
4
Asterisk 1.8 and dual stack support
Hi folks,
Following an upgrade to Debian wheezy, I'm now running Asterisk 1.8.13.1.
As opposed to Asterisk 1.6.2.9 that I ran with squeeze, this version can
support IPv6. However, it seems that I can't get it to support both IPv4
and IPv6 at the same time. For example, if in sip.conf I set the bindaddr
variable to '::' it will only listen on IPv6 and none of my IPv4-only
2009 Sep 13
6
[Bug 1648] New: Fix IPV6_V6ONLY for -L with -g
....0-OpenSSH_5.2
Using Fedora 11 kernel with its (+AFAIK upstream) defaults:
# cat /proc/version
Linux version 2.6.30.5-43.fc11.x86_64
(mockbuild at xenbuilder4.fedora.phx.redhat.com) (gcc version 4.4.1
20090725 (Red Hat 4.4.1-2) (GCC) ) #1 SMP Thu Aug 27 21:39:52 EDT 2009
# cat /proc/sys/net/ipv6/bindv6only
0
In the current case one cannot access IPv6 because the IPv4 socket was
created first. If IPv6 would be created first it would work.
The copy-pasted code could be probably moved to some unified function.
This is out of scope of this patch.
Similiar problem+resolution was in Bug 164, Bug 130...
2010 Jan 16
0
Processed: tag ipv6 related packages
Processing commands for control at bugs.debian.org:
> # Tagging bugs related to IPv6 support according to bug title (and checked for false positive)
> # Maintainer, sorry if you consider the tag as not relevant
> tag 561835 +ipv6
Bug #561835 [openjdk-6-jdk] josm: net.ipv6.bindv6only=1 breaks OSM access
Added tag(s) ipv6.
> tag 560837 +ipv6
Bug #560837 {Done: Krzysztof Krzy??aniak (eloy) <eloy at debian.org>} [lighttpd] lighttpd listened on ipv6 only after upgrade
Added tag(s) ipv6.
> tag 553584 +ipv6
Bug #553584 [snort] CVE-2009-3641: DoS while printing specially...
2010 Jan 16
0
Processed: tag ipv6 related packages
Processing commands for control at bugs.debian.org:
> # Tagging bugs related to IPv6 support according to bug title (and checked for false positive)
> # Maintainer, sorry if you consider the tag as not relevant
> tag 561835 +ipv6
Bug #561835 [openjdk-6-jdk] josm: net.ipv6.bindv6only=1 breaks OSM access
Added tag(s) ipv6.
> tag 560837 +ipv6
Bug #560837 {Done: Krzysztof Krzy??aniak (eloy) <eloy at debian.org>} [lighttpd] lighttpd listened on ipv6 only after upgrade
Added tag(s) ipv6.
> tag 553584 +ipv6
Bug #553584 [snort] CVE-2009-3641: DoS while printing specially...
2017 Jul 30
2
firewalld and LISTEN
...:::*
>>
>
>
> By default, Linux processes that listen on an IPv6 port will also listen
> on the IPv4 port (when no specific address is specified):
>
> http://man7.org/linux/man-pages/man7/ipv6.7.html
>
> You could change that behavior by modifying /proc/sys/net/ipv6/bindv6only,
> but your system is working normally now.
>
> _______________________________________________
> CentOS mailing list
> CentOS at centos.org
> https://lists.centos.org/mailman/listinfo/centos
>