From: Jim Reisert AD1C <jjreisert@alum.mit.edu>
To: cerowrt-devel@lists.bufferbloat.net
Subject: [Cerowrt-devel] Strangeness in log files
Date: Mon, 1 Jul 2013 08:21:34 -0600 [thread overview]
Message-ID: <CAK-n8j5m=hZQ6Wv+pL0YcproR3HWuz2-E+GQ6E-G52C57rBaSA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1461 bytes --]
I'm running 3.8.13 on a WNDR3800 router. Should I be concerned about these
messages. I am not configured for IPv6 (Comcast), unless someone knows of
a way to do so.
system log:
Jul 1 14:19:06 cerowrt daemon.err miniupnpd[2738]: Can't find in which sub
network the client is
Jul 1 14:19:06 cerowrt daemon.err miniupnpd[2738]: Can't find in which sub
network the client is
Jul 1 14:19:06 cerowrt daemon.err miniupnpd[2738]: Can't find in which sub
network the client is
Jul 1 14:19:13 cerowrt daemon.warn dnsmasq-dhcp[3583]: no address range
available for DHCPv6 request via se00
Jul 1 14:19:20 cerowrt daemon.warn dnsmasq-dhcp[3583]: no address range
available for DHCPv6 request via se00
Jul 1 14:19:45 cerowrt daemon.warn dnsmasq-dhcp[3583]: no address range
available for DHCPv6 request via se00
Jul 1 14:19:52 cerowrt daemon.warn dnsmasq-dhcp[3583]: no address range
available for DHCPv6 request via se00
kernel log:
[33272.566406] IPv6: Neighbour table overflow
[33272.570312] IPv6: Neighbour table overflow
[33272.574218] IPv6: Neighbour table overflow
[33272.578125] IPv6: Neighbour table overflow
[33272.585937] IPv6: Neighbour table overflow
[33272.589843] IPv6: Neighbour table overflow
[33272.593750] IPv6: Neighbour table overflow
[33272.597656] IPv6: Neighbour table overflow
[33272.601562] IPv6: Neighbour table overflow
[33272.605468] IPv6: Neighbour table overflow
--
Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
[-- Attachment #2: Type: text/html, Size: 1784 bytes --]
reply other threads:[~2013-07-01 14:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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='CAK-n8j5m=hZQ6Wv+pL0YcproR3HWuz2-E+GQ6E-G52C57rBaSA@mail.gmail.com' \
--to=jjreisert@alum.mit.edu \
--cc=cerowrt-devel@lists.bufferbloat.net \
/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