Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Jim Reisert AD1C <jjreisert@alum.mit.edu>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] Comcast specific Cerowrt-3.10.26-7: another "too exciting for me" unrelease
Date: Sat, 25 Jan 2014 12:14:40 -0500	[thread overview]
Message-ID: <CAA93jw4kjv9BMFfP+mwSKyHzgTEjnXAym5RdjouW5jVmQz4s4w@mail.gmail.com> (raw)
In-Reply-To: <CAA93jw4R0od7W_WN-NVbOOUEcNcDOFg0wgJcadv0ie+5MoHVZA@mail.gmail.com>

On Sat, Jan 25, 2014 at 12:09 PM, Dave Taht <dave.taht@gmail.com> wrote:
> On Sat, Jan 25, 2014 at 11:57 AM, Jim Reisert AD1C
> <jjreisert@alum.mit.edu> wrote:
>> On Fri, Jan 24, 2014 at 10:06 AM, Dave Taht wrote:
>>
>>> I still recomend that everyone on comcast & not running this release do this.
>>
>> I'm up!
>
> And hopefully you'll stay up. :)

I just ping6'd you and you were up briefly and not now.

>
>> http://test-ipv6.comcast.net/
>>
>> Your IPv4 address on the public internet appears to be 76.25.42.131
>>
>> Your IPv6 address on the public internet appears to be
>> 2601:1:8a80:932:bc99:de2f:7f93:455f
>
> You will want to lock down some passwords, and restrict access
> to your own subnets. One thing not done is any form

of adding ipv6 to the xined daemon, by default it restricts
access to ipv4 natted hosts only. (so the router is very secure).

I wouldn't mind if you added a line to /etc/xinet.d/netserver
to let me try a rrul test from here:

only_from = 172.16.0.0/12 149.20.63.30 2001:4f8:3:203::c001

(this is the snapon test server)

Commonly insecure ports like windows filesharing are blocked on ipv6
and ipv4 from the public internet, already.

>
>> Congratulations! You appear to have both IPv4 and IPv6 internet
>> working. If a publisher publishes to IPv6, your browser will connect
>> using IPv6. Note: Your browser appears to prefer IPv4 over IPv6 when
>> given the choice. This may in the future affect the accuracy of sites
>> who guess at your location.
>
> Which browser is this?
>
>> Your DNS server (possibly run by your ISP) appears to have IPv6 internet access.
>
> Excellent. 4 down, several billion to go.
>
>
>> --
>> Jim Reisert AD1C, <jjreisert@alum.mit.edu>, http://www.ad1c.us
>
>
>
> --
> Dave Täht
>
> Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html



-- 
Dave Täht

Fixing bufferbloat with cerowrt: http://www.teklibre.com/cerowrt/subscribe.html

  reply	other threads:[~2014-01-25 17:14 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-21 20:59 Dave Taht
2014-01-24 17:06 ` Dave Taht
2014-01-24 22:08   ` Toke Høiland-Jørgensen
2014-01-24 22:27     ` Dave Taht
2014-01-24 23:14       ` Sebastian Moeller
2014-01-26  3:04       ` [Cerowrt-devel] side issue, related to the bigger picture surrounding Cerowrt and Bufferbloat dpreed
2014-01-25 16:57   ` [Cerowrt-devel] Comcast specific Cerowrt-3.10.26-7: another "too exciting for me" unrelease Jim Reisert AD1C
2014-01-25 17:09     ` Dave Taht
2014-01-25 17:14       ` Dave Taht [this message]
2014-01-25 20:26 Jim Reisert AD1C

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=CAA93jw4kjv9BMFfP+mwSKyHzgTEjnXAym5RdjouW5jVmQz4s4w@mail.gmail.com \
    --to=dave.taht@gmail.com \
    --cc=cerowrt-devel@lists.bufferbloat.net \
    --cc=jjreisert@alum.mit.edu \
    /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