From: Dave Taht <dave.taht@gmail.com>
To: Michael Richardson <mcr@sandelman.ca>
Cc: cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] frequency of RAs from 6relayd
Date: Wed, 12 Jun 2013 11:34:50 -0700 [thread overview]
Message-ID: <CAA93jw6us1XX9U__UxWuGT1p6nzaMX8=9VguwsDRhHKitc47ug@mail.gmail.com> (raw)
In-Reply-To: <13946.1371057290@sandelman.ca>
[-- Attachment #1: Type: text/plain, Size: 3109 bytes --]
There is kind of a conflict on RA handling between dnsmasq and 6relayd
going on - back in january, dnsmasq was "winning", and the default. Since
then the 6relayd stuff has evolved something considerable, and I have not
looked into changing things around, nor how they should be changed around.
Try disabling dnsmasq's RA handling.
On Wed, Jun 12, 2013 at 10:14 AM, Michael Richardson <mcr@sandelman.ca>wrote:
>
> I am seeing a problem where the IPv6 default on a number of systems
> that use RA to get it is going away on a regular basis. CeroWrt 3.8 is
> the source of RA and IPv6 default routes everywhere. A /48 is delegated
> (manually) from my ISP, and configured for each subnet.
>
> There is no way that I can see to specify or find out what the lifetime
> / frequency of the RAs are in the UI. In /etc/config/6relayd, I see:
>
> config server 'default'
> option rd 'server'
> option compat_ula '1'
> option always_assume_default '1'
> option fallback_relay 'ndp'
> list network 'VoIP'
> list network 'gw00'
> list network 'gw01'
> list network 'gw10'
> list network 'gw11'
> list network 'se00'
> list network 'services'
> list network 'sw00'
> list network 'sw10'
> list network 'trusted'
>
> It is my understanding that 6relayd is responsible for sending out RAs.
>
> On my desktop:
>
> obiwan-[~] mcr 10187 %sudo rdisc6 eth0
> Soliciting ff02::2 (ff02::2) on eth0...
>
> Hop limit : undefined ( 0x00)
> Stateful address conf. : Yes
> Stateful other conf. : Yes
> Router preference : medium
> Router lifetime : 1800 (0x00000708) seconds
> Reachable time : unspecified (0x00000000)
> Retransmit time : unspecified (0x00000000)
> Source link-layer address: 76:44:01:76:5D:CC
> MTU : 1500 bytes (valid)
> from fe80::7444:1ff:fe76:5dcc
>
> (5dcc is indeed my CeroWRT)
>
> while the router lifetime given is 30 minutes, I am wondering if
> something else is up. I would have thought I'd see a prefix advertised
> here.
>
> As my MP3 streamer one of the machines affected, when it loses it's IP,
> it either falls off of NFS or the TCP stream breaks, and things go
> quiet.
>
> I've ssh'ed into my MP3 server (over v4), and I'm running:
> watch ip -6 route ls
> and sudo tcpdump -i eth0 -n -p ip6 and icmp6
> in two windows.
>
> --
> ] Never tell me the odds! | ipv6 mesh
> networks [
> ] Michael Richardson, Sandelman Software Works | network
> architect [
> ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails
> [
>
> _______________________________________________
> Cerowrt-devel mailing list
> Cerowrt-devel@lists.bufferbloat.net
> https://lists.bufferbloat.net/listinfo/cerowrt-devel
>
--
Dave Täht
Fixing bufferbloat with cerowrt:
http://www.teklibre.com/cerowrt/subscribe.html
[-- Attachment #2: Type: text/html, Size: 4029 bytes --]
next prev parent reply other threads:[~2013-06-12 18:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-12 17:14 Michael Richardson
2013-06-12 18:34 ` Dave Taht [this message]
2013-06-12 20:05 ` mcr
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://lists.bufferbloat.net/postorius/lists/cerowrt-devel.lists.bufferbloat.net/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAA93jw6us1XX9U__UxWuGT1p6nzaMX8=9VguwsDRhHKitc47ug@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=mcr@sandelman.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox