From: "Török Edwin" <edwin+ml-cerowrt@etorok.net>
To: cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] cerowrt_stability?
Date: Sat, 07 Jun 2014 15:38:22 +0300 [thread overview]
Message-ID: <539307BE.9070509@etorok.net> (raw)
In-Reply-To: <CAA93jw7tv72mUC594kGvuWSFaaYYxoLZchWzmWpcAjc1RiDVeA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 2450 bytes --]
On 06/06/2014 05:46 PM, Dave Taht wrote:
> 1)how many are encountering bug 442 regularly?
>
> Getting it to occur is hard for me. I've only seen in once in the last
> several weeks, jg can have it happen inside of two days. It mostly
> seems to occur in conditions of poor signal strength, near as I can tell.
>
> 2) aside from that, how are things?
I am quite happy with 3.10.40-5, although I might try -6 soon as apparently that has a new dnsmasq.
I don't use wireless that often these days anymore, so I can't say about that bug.
I didn't have troubles with DNSSEC with the default config.
IPv6 works reliably too, in fact it is too reliable :) It happened once that I DHCP/IPv4 was broken, but IPv6 still worked.
There are just 2 strange things that weren't reproducible [1], sorry that I can't give you more than anecdotal evidence:
1. I booted the router, the interface went up, I read my email, tried to search on startpage.com, but it was down (or so I thought),
so I searched google, but then none of the links in google work ... ah there is no IPV4 address ...
Running DHCP didn't give me anything, and manually setting an IP address on eth0 didn't help either as I wasn't able to ping / ssh the router on IPv4
(and apparently ssh doesn't work on IPv6, might be my fault though)
I was able to open the web interface on IPv6, tried restarting dnsmasq but that didn't fix things, so I just rebooted the router and then it worked.
2. At some point my internet speed and latency become very bad. I don't know if this was due to the fault of my ISP or not, but a reboot fixed it.
A ping looked like this (over an ethernet connection):
PING www.google.com (173.194.44.52) 56(84) bytes of data.
64 bytes from muc03s08-in-f20.1e100.net (173.194.44.52): icmp_seq=1 ttl=55 time=2467 ms
64 bytes from muc03s08-in-f20.1e100.net (173.194.44.52): icmp_seq=2 ttl=55 time=2502 ms
64 bytes from muc03s08-in-f20.1e100.net (173.194.44.52): icmp_seq=3 ttl=55 time=2349 ms
The good news is that I had a VoIP call running at the time, and I could still understand everyone, in fact I only noticed
something was wrong when I finished the call and people told me I was very lagged with my replies.
I think thats a success for cerowrt's SQM, that voip was still able to work even on a very lagged and slow line :)
P.S. I use a variation of the attached script to configure my router, which is based on the script from the wiki.
Best regards,
--Edwin
[-- Attachment #2: script.sh --]
[-- Type: application/x-shellscript, Size: 7001 bytes --]
next prev parent reply other threads:[~2014-06-07 12:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-06 14:46 Dave Taht
2014-06-07 12:38 ` Török Edwin [this message]
2014-06-07 17:55 ` Dave Taht
2014-06-07 3:28 R.
2014-06-10 0:01 ` R.
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=539307BE.9070509@etorok.net \
--to=edwin+ml-cerowrt@etorok.net \
--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