Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: "Richard E. Brown" <richb.hanover@gmail.com>
To: Fred Stratton <fredstratton@imap.cc>,
	cerowrt-devel@lists.bufferbloat.net
Subject: Re: [Cerowrt-devel] CeroWrt 3.10.18-1 Field Report
Date: Tue, 12 Nov 2013 12:24:29 -0500	[thread overview]
Message-ID: <4703EA71-6E03-426C-9420-278C292E87D9@gmail.com> (raw)
In-Reply-To: <5281F772.10504@imap.cc>

On Nov 12, 2013, at 4:40 AM, Fred Stratton <fredstratton@imap.cc> wrote:

> After your helpful writeup as an ADSL user, I am expanding on the previous remarks I made. SM is making his contribution as I write.
> 
> For several years, I have been with Telefonica O2 as an ISP. This network gave subscribers a dynamic ipv4 address which did not change unless the gateway WAN MAC changed. Sky bought the network to get the 400 000 subscribers and migrated everyone to their network, closing the O2 setup. I left, moving to TalkTalk, a network which gives out a different ipv4 address every time it retrains, two or three times a day at present, using their proprietary dynamic line management unchanged.
> 
> I threw away the supplied Trendchip box, and use a 1483-bridged TP-Link TD-W8970 to connect to the phone line.
> 
> Here, PPPoE always comes up using the 3.10.18-1 build. Henet is more problematic. I lose ipv6 connectivity every five or so retrains, and have to reboot the router.
> 
> The latest builds allow concurrent downloading or the use of torrents and video streaming 90 per cent of the time. tc-stab is apparently functional.
> 
> Changing ISP has been a very illuminating exercise from the point of view of 'bufferbloat'. O2 lost a lot of packets through their site screening mechanism. TalkTalk subcontracts its deep packet inspection to Huawei in China. This minimises packet loss.
> 
> Have set AQM to circa 70 percent of download sync and 95 per cent of upload sync, based on empirical incremental changes.

What other information could I collect if I find that PPPoE isn’t coming up reliably?

re: HEnet tunnels not coming up. There’s an easier way to reconnect the tunnel by going to a HTTPS link. It’s described in the IPv6 Tunnel page on the wiki: http://www.bufferbloat.net/projects/cerowrt/wiki/IPv6_Tunnel (Check out step 3, manually re-establishing the tunnel)

Rich

  reply	other threads:[~2013-11-12 17:25 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-11-12  5:47 Richard E. Brown
2013-11-12  9:11 ` Sebastian Moeller
     [not found]   ` <51BF9432-6FC2-4A14-B147-13F1E779CA93@gmail.com>
2013-11-12 17:26     ` Richard E. Brown
2013-11-12 21:17       ` Sebastian Moeller
2013-11-12 23:06         ` Sebastian Moeller
2013-11-12 23:11           ` Sebastian Moeller
2013-11-15 12:35             ` Sebastian Moeller
2013-11-13  4:21   ` Richard E. Brown
2013-11-13 13:56     ` Sebastian Moeller
2013-11-13 15:53       ` Richard E. Brown
2013-11-12  9:40 ` Fred Stratton
2013-11-12 17:24   ` Richard E. Brown [this message]
2013-11-15  1:56 ` Richard E. Brown
2013-11-15  2:27   ` David Personette

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=4703EA71-6E03-426C-9420-278C292E87D9@gmail.com \
    --to=richb.hanover@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=fredstratton@imap.cc \
    /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