similar to: ipv6 default route from somewhere

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

On Fri, Mar 04, 2016 at 09:43:44PM +0100, Guus Sliepen wrote: > - On Linux, add "echo 0 >/proc/sys/net/ipv6/conf/$INTERFACE/accept_ra" > to tinc-up before any ifconfig or ip commands. Ah, if it's only the default route you don't want, then it's: echo 0 >/proc/sys/net/ipv6/conf/$INTERFACE/accept_ra_defrtr -- Met vriendelijke groet / with kind regards,

Changing the subject line for good ... On Thu, Apr 7, 2011 at 8:58 AM, Lamar Owen <lowen at pari.edu> wrote: > On Thursday, April 07, 2011 11:23:51 AM Brunner, Brian T. wrote: >> AIUI: In previous releases, RH distributed source + patches. ?Starting >> 6.0 RH releases patched source. ?This makes backing out a patch, or >> backporting patches from future development in

Hello, Firstly THANK YOU for the IPv6 NAT support merged in 6.5. It has been almost impossible to get IPv6 into a VM on a laptop that switches between wifi and wired (dock) connections, because you can not add a wifi interface to a bridge. I know NAT is against the IPv6 end-to-end xen but it makes this "just work" for the vast majority of people like me who need to ssh/curl/talk to

I just got 50 Mbps symmetric fiber from AT&T and it includes a /56 of IPv6 addresses, replacing a much slower ADSL line. I never tried to get IPv6 working on the old connection. I'm using CentOS 7 as a gateway and it's worked great for several versions for IPv4. I'm not seeing any IPv6 default route on the WAN interface. I suspect I'm not getting route announcements. I

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,

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

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

Hi, Sorry for the delay. On Tue, 11 Aug 2020 23:52:46 -0400 Laine Stump <laine@redhat.com> wrote: > On 8/10/20 11:23 PM, Ian Wienand wrote: > > Hello, > > > > Firstly THANK YOU for the IPv6 NAT support merged in 6.5. It has been > > almost impossible to get IPv6 into a VM on a laptop that switches > > between wifi and wired (dock) connections, because

Hi ? I already stop the named and killall bind process. how can I clear the files under named/chroot/proc/ folder as those files are restricted me for tar backup? ? /var/named/chroot/proc/sys/net/ipv6/conf/lo/accept_ra_defrtr /var/named/chroot/proc/sys/net/ipv6/conf/lo/max_addresses /var/named/chroot/proc/sys/net/ipv6/conf/lo/max_desync_factor

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).

How about, in your /etc/sysconfig/network file adding or editing the line for IPV6 to be: NETWORKING_IPV6=no and then try a 'service network restart' and see what you get. Chris On Mon, Mar 9, 2015 at 11:52 AM, Robert Moskowitz <rgm at htt-consult.com> wrote: > No change after running this and trying both: > > system network restart > > ifdown eth0; ifup eth0

> On 03/09/2015 01:15 AM, Chris Stone wrote: >> >> sysctl -w net.ipv6.conf.all.accept_ra=0 On 03/10/2015 06:52 AM, Robert Moskowitz wrote: > No change after running this and trying both: > > system network restart it's: service network restart Try also setting these in sysctl: net.ipv6.conf.all.disable_ipv6=1 net.ipv6.conf.default.disable_ipv6=1

Two VPSs. Identical setups with the exception of the extension. Same version of everything, Asterisk 14.1, Ubuntu 16.10, same firewall rules and so on - box 2 was cloned from box 1. Both VPSs run in the same datacentre. Suddenly, after weeks of OK, I'm getting lots of this on ONE box only: [Nov 4 21:23:04] NOTICE[1468]: res_hep.c:466 hep_queue_cb: Unable to send packet: Address Family

Hi Sandy, Thanks! Curious. Do you have any other interfaces? ifconfig -a should show them all including loopback. What is puzzling me is that it should not even attempt to use IPv6 to reach a global address when it only has a link-local address. It should gracefully fall back to IPv4 (as per RFC 6724 or RFC 3484 depending on the kernel version). Since you have an IPv4 address and I assume an

On Sat, May 20, 2017 at 8:30 PM, Sarah Newman <srn at prgmr.com> wrote: > I experienced a bug that is likely the same as https://bugs.launchpad.net/ > ubuntu/+source/linux/+bug/1350373 . Commit > b7dd0e350e0bd4c0fddcc9b8958342700b00b168 , which is supposed to fix it, > doesn't appear in this kernel and doesn't apply cleanly either. > Is there any point in trying to

Hi, below is the output of the kernel just before it goes down and crashes. I have to use "xm destroy" to kill it. I have tried the enable/disable the "Optimize for Size" setting in the kernel. I hopes that it''s some kind of compiler bug because of the "invalid opcode" thing. But actually I don''t a clue what this might be caused by. Do you

Hello CentOS Xen Heroes, Yesterday, I have installed testing kernel 4.9.23-26.el6.x86_64 from virt-xen-testing repo. It crashed today morning. Hardware is a pretty ancient, testing machine (CO6 PV guests only), but had no problems yet. It was stable on 4.9*, including testing 4.9.15-22.el6.x86_64 Console output: [59826.069427] general protection fault: 0000 [#1] SMP [59826.069463] Modules

> Thanks for the heads-up. It's been running through XenServer's tests > as well as the XenProject's "osstest" -- I haven't heard of any > additional issues, but I'll ask. Looks like I can reproduce this pretty easily, this happened upon ssh'ing into the server while I had a VM migrating into it. The system goes completely unresponsive (can't even

And some more information ... Am 2014-10-13 12:04, schrieb Jonas Meurer: > Am 2014-08-19 12:26, schrieb Jonas Meurer: >> I encounter kernel crashes on an up-to-date Debian/Wheezy Xen domU >> with the >> stock kernel. The dom0 runs the same linux kernel and >> xen/4.1.4-3+deb7u1. > > the bug is still reproducible with the latest kernel and Xen packages >