Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
From: Dave Taht <dave.taht@gmail.com>
To: Valdis Kletnieks <Valdis.Kletnieks@vt.edu>
Cc: "cerowrt-devel@lists.bufferbloat.net"
	<cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] cerowrt-3.10.32-9 released
Date: Sun, 16 Mar 2014 14:45:45 -0700	[thread overview]
Message-ID: <CAA93jw5d+Gs71T9xOQhWNNiLo6n29BxPc+jYj=Z-NkjhFLh_NQ@mail.gmail.com> (raw)
In-Reply-To: <145161.1395005271@turing-police.cc.vt.edu>

Valdis:

1) enable upnp and play some games?

2) what is the output of:

cat /sys/kernel/debug/mips/unaligned_instructions

3) It does look like miniupnpd IS correctly rejecting connection
attempts from the outside world, but I think I'd prefer to firewall it
off completely.

# logread

Sat Jan 17 03:30:04 1970 daemon.warn miniupnpd[21982]: HTTP peer
[::ffff:186.215.61.169]:41839 is not from a LAN, closing the
connection
Sat Jan 17 03:30:04 1970 daemon.warn miniupnpd[21982]: HTTP peer
[::ffff:59.90.193.38]:54571 is not from a LAN, closing the connection

And I'd love to improve the defensive sensor facility one day, to log
and forward external cracker attempts to something like a rbl blocklist.

Sat Jan 17 03:30:04 1970 daemon.crit xinetd[1416]: 1416
{process_sensor} Adding 103.26.122.210 to the global_no_access list
for 120 minutes

Still I sleep better knowing these limited protections are working.


On Sun, Mar 16, 2014 at 2:27 PM,  <Valdis.Kletnieks@vt.edu> wrote:
> On Sun, 16 Mar 2014 12:58:28 -0700, Dave Taht said:
>> Get it at:
>>
>> http://snapon.lab.bufferbloat.net/~cero2/cerowrt/wndr/3.10.32-9/
>
>> - untested with ipv6 as yet
>
> Running it on my 3800, IPv6 from my laptop to Google and work and
> other places seems to be working just fine in my corner of Comcast land.
> My laptop gets a DHCPv6 address, a SLAAC address, and generates itself
> a privacy address, and they all are reachable from the outside, and my
> Rasberry Pi is happily SLAAC'ing away as well.  As far as I can tell,
> my TV and my PS3 are IPv4-only, so that's as much as I can test.
>
> If I catch it misbehaving, or there's something in particular you want
> poked, yell...
>
>



-- 
Dave Täht

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

  reply	other threads:[~2014-03-16 21:45 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-03-16 19:58 Dave Taht
2014-03-16 21:27 ` Valdis.Kletnieks
2014-03-16 21:45   ` Dave Taht [this message]
2014-03-17  0:03     ` Toke Høiland-Jørgensen
2014-03-17  0:42     ` Valdis.Kletnieks
2014-03-17  0:54       ` Dave Taht
2014-03-17 12:20 ` Michael Richardson
2014-03-17 13:40   ` Dave Taht
2014-03-17 14:30     ` Toke Høiland-Jørgensen
2014-03-17 14:39       ` Toke Høiland-Jørgensen
2014-03-17 14:55       ` Dave Taht
2014-03-17 14:55     ` Michael Richardson
2014-03-17 15:18       ` Dave Taht
2014-03-18 10:00 ` Török Edwin
2014-03-18 12:12   ` Sebastian Moeller
2014-03-18 14:21     ` Dave Taht
2014-03-18 15:22       ` Török Edwin
2014-03-18 15:35         ` Dave Taht
2014-03-18 16:49           ` Török Edwin
2014-03-18 17:03             ` Dave Taht
2014-03-18 17:06           ` Valdis.Kletnieks

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='CAA93jw5d+Gs71T9xOQhWNNiLo6n29BxPc+jYj=Z-NkjhFLh_NQ@mail.gmail.com' \
    --to=dave.taht@gmail.com \
    --cc=Valdis.Kletnieks@vt.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