search for: ipv6s

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

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

Used steps on sysctl from?Centos7 FAQ (https://wiki.centos.org/FAQ/CentOS7)?and some gathered on internet # cat /etc/sysctl.d/90-disable_ipv6.conf? net.ipv6.conf.all.disable_ipv6=1 net.ipv6.conf.default.disable_ipv6=1 net.ipv6.conf.eth0.disable_ipv6=1 net.ipv6.conf.eth1.disable_ipv6=1 net.ipv6.conf.all.use_tempaddr=0 net.ipv6.conf.all.autoconf=0 net.ipv6.conf.all.accept_ra=0

Processing commands for control at bugs.debian.org: > ## dear clint. > ## > ## release goals are release goals and not release blockers. > ## please learn the difference and discuss this beforehand. > ## > ## thanks. > ## > > severity 382189 serious > ## > Bug #382189 [nbd-server] no IPv6 support > ## > Severity set to 'serious' from

Processing commands for control at bugs.debian.org: > severity 382189 serious Bug #382189 [nbd-server] no IPv6 support Severity set to 'serious' from 'important' > severity 384372 serious Bug #384372 [libadns1] libadns1: Cannot query IPv6 DNS servers Severity set to 'serious' from 'important' > severity 517299 serious Bug #517299 [klibido] klibido: needs

I have just moved a host from a network that supports static IPv4 and IPv6. The IPv4 addr is set in ifcfg-eth0, and the IPv6 via RA (I set the MAC so I get an IPv6 addr that I like). I just moved the host to a network that supports static IPv4, but only dymanic IPv6, so at this time (until I get static IPv6), I need to disable the global IPv6 addressing. So in the ifcfg-eth0 file I set:

Hi, I looked at CVS and this mailing list and didn't find anything regarding IPv6 support. I found old patches from KAME and one IPv6-only implementation (http://www.bugfactory.org/~gav/ipv6/icecast-1.3.11-ipv6.diff.gz) only. Therefore I decided to do this work again and as good as possible. I integrated IPv6 into configure script which allows to use te same code both for IPv4 and IPv6

On Fri, Mar 6, 2015 at 11:52 AM, Robert Moskowitz <rgm at htt-consult.com> wrote: > > > On 03/06/2015 11:00 AM, Robert Moskowitz wrote: > >> >> >> On 03/06/2015 10:55 AM, Barry Brimer wrote: >> >>> >>> >>> IPV6INIT="no" >>>> >>>> But I am still getting a global IPv6 (and of course local scope).

Sorry - that should be sysctl -w net.ipv6.conf.all.accept_ra=0 to disable that, not 1. Chris On Sun, Mar 8, 2015 at 11:14 PM, Chris Stone <axisml at gmail.com> wrote: > Try: > > sysctl -w net.ipv6.conf.all.accept_ra=1 > > to persist between boots, be sure to add this to your /etc/sysctl.conf > file. > > This should prevent the box from listening to any RA

On 03/06/2015 10:55 AM, Barry Brimer wrote: > > >> IPV6INIT="no" >> >> But I am still getting a global IPv6 (and of course local scope). >> >> What else do I need to do to disable the listening for RA announcements >> >> and setting an IPv6 global address? I do not want to reboot the box. > There are other modules, most notably bonding

I do not working with ipv6, I have disable, but I have the same error, I can read in internet that this ipv6 ip 2001:638:603:d06e::80:230: belong to url samba.org.... If I try to connect to this url using some navegator I connected perfect....but when I run git pull using command line I can not connect.. > Am 28.02.2015 um 15:37 schrieb sandy.napoles at eccmg.cupet.cu: >> Hello list,

On 21-03-17 20:51, Diaulas Castro wrote: > Used steps on sysctl from Centos7 FAQ (https://wiki.centos.org/FAQ/CentOS7) and some gathered on internet > > # cat /etc/sysctl.d/90-disable_ipv6.conf > net.ipv6.conf.all.disable_ipv6=1 > net.ipv6.conf.default.disable_ipv6=1 > net.ipv6.conf.eth0.disable_ipv6=1 > net.ipv6.conf.eth1.disable_ipv6=1 > net.ipv6.conf.all.use_tempaddr=0

http://www.realvnc.com/products/enterprise/4.1/ipv6.html IPv6 support in VNC Server E4.1.7/P4.1.2 VNC Server E4.1.7 & P4.1.2 are fully IPv6-aware, but is shipped with IPv6 support disabled by default, for security reasons. IPv6 can be enabled by setting "InTransports=IPv6,IPv4" (the default being IPv4 only), either on the command-line when starting vncserver under Unix Ok.

Hi Joachim, > Op 15 feb 2024 om 23:09 heeft Joachim Lindenberg via samba <samba at lists.samba.org> het volgende geschreven: > > ?Hi Rowland, > No, I don?t have so many devices yet. Rowland believes that one should not use IPv6 internally. Many disagree. > But I know some organizations that want to switch to IPv6 consistently and you can rephrase my question to whether

Hello, I have a nwfilter that I'm using to ensure that libvirt domains can't spoof IPv6 traffic. It looks like this: <filter name='no-ipv6-spoofing' chain='ipv6-ip' priority='-710'> <rule action='return' direction='out' priority='500'> <ipv6 srcipaddr='$IPV6' srcipmask='$IPV6MASK'/> </rule>

Dear Simon, every second IP-address is unwanted. We restarted? eno4: nmcli con down eno4; nmcli con up eno4 and the second address vanishes. Then after a few ours, the second ip address reappears. This is the config-file of eno2: # cat ifcfg-eno2 TYPE=Ethernet PROXY_METHOD=none BROWSER_ONLY=no BOOTPROTO=none DEFROUTE=yes IPV4_FAILURE_FATAL=yes IPV6INIT=no IPV6_AUTOCONF=yes IPV6_DEFROUTE=yes

Hello Samba Community, I've couple of questions regarding IPv6 link-local address support with Samba4. Is Samba4 suppose to listen on IPv6 link-local address? With following lines in smb.conf, smbd listens on IPv4 and IPv6 global address but not on IPv6 link-local address assigned on eth0. bind interfaces only = yes interfaces = lo eth0 On the same Linux box, Samba-3.5 used

Hello! I am having a strange issue with CentOS 5.4 that I cannot seem to solve. Every DNS lookup results in AAAA records being requested first before A records. As a result, this causes a large amount of unnecessary DNS traffic on the network. IPv6 has been completely disabled on these servers: /etc/modprobe.conf, ipv6 off and net-pf-10 off /etc/sysconfig/network, NETWORKING_IPV6=no lsmod |

After upgrading one of our servers from Fedora 7 to Fedora 9, from Samba 3.0 to 3.2.0-2.17.fc9 I noticed this strange phenomena: Windows 2003 and XP clients freeze when you type "\\server" in an explorer address bar where "server" is the name of the Samba 3.2 host. Windows 2000 clients don't freeze. 2003/XP clients don't freeze when you enter

I have setup a CentOS 6.3 VPS with ONLY IPv6 access simply for testing at this point. It browses the Internet with lynx fine on most major sites that are IPv6 enabled. Yum does not seem to work though. Always tries to connect to an IPv4 mirror and gives an error. Is there a way specify an IPv6 mirror to yum?