From: Dave Taht <dave.taht@gmail.com>
To: "David P. Reed" <dpreed@deepplum.com>
Cc: Michael Richardson <mcr@sandelman.ca>,
cerowrt-devel <cerowrt-devel@lists.bufferbloat.net>
Subject: Re: [Cerowrt-devel] I got ipv6 on my cell tether this morning
Date: Tue, 28 Jan 2020 11:42:45 -0800 [thread overview]
Message-ID: <CAA93jw59n4Wa3W_Ck=oVLH_oGQ4__9SEznYicnNHD6JqEZQJEg@mail.gmail.com> (raw)
In-Reply-To: <1580238197.904526891@apps.rackspace.com>
On Tue, Jan 28, 2020 at 11:03 AM David P. Reed <dpreed@deepplum.com> wrote:
>
> Good grief, can't we kill off NAT? IPv4.01 isn't IPv6.
It's astonishing how little ipv4 traffic I'm generating...
> What does the other end think your IPv6 source address is?
It's the real thing, I can get back and forth via tcp, at least, to
port 22 or netperfs port. I was really surprised to see port 25 not
blocked. (course without reverse dns most mailers will fail)
I worry (not on this laptop, but others) about all the other ports I
might have exposed like 53 or smb...
>Can your tethered systems pass addressable endpoints to the other end, and expect them to work?
tcp tested. udp tested. rather depressing watching every keystroke in
gmail going back to big brother over udp, actually...
Somewhere around here I have udplite for netperf. It would be pretty
cool if other protocol
numbers just worked...
> Or will there be STUN6/TURN6 needed to do, say, WebRTC peering?
Haven't tried that yet! I sure hope not. Being MITM is kind of a
billable event for some folk though....
I guess my overall thought was that folk in the us check...
>
> On Tuesday, January 28, 2020 12:51pm, "Michael Richardson" <mcr@sandelman.ca> said:
>
> > Dave Taht <dave.taht@gmail.com> wrote:
> > > I got a new phone for christmas, and was surprised to see I finally had an
> > IPv6
> > > allocation on my tether. More surprising was seeing fc:: used... and
> > > while my laptop
> >
> > Sounds like your phone has decided to use NAT66, as fc:: is a ULA.
> >
> > --
> > ] Never tell me the odds! | ipv6 mesh networks [
> > ] Michael Richardson, Sandelman Software Works | IoT architect [
> > ] mcr@sandelman.ca http://www.sandelman.ca/ | ruby on rails [
> >
> > _______________________________________________
> > Cerowrt-devel mailing list
> > Cerowrt-devel@lists.bufferbloat.net
> > https://lists.bufferbloat.net/listinfo/cerowrt-devel
> >
>
>
--
Make Music, Not War
Dave Täht
CTO, TekLibre, LLC
http://www.teklibre.com
Tel: 1-831-435-0729
prev parent reply other threads:[~2020-01-28 19:42 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-28 15:51 Dave Taht
2020-01-28 17:51 ` Michael Richardson
2020-01-28 18:03 ` Dave Taht
2020-01-28 19:03 ` David P. Reed
2020-01-28 19:42 ` Dave Taht [this message]
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='CAA93jw59n4Wa3W_Ck=oVLH_oGQ4__9SEznYicnNHD6JqEZQJEg@mail.gmail.com' \
--to=dave.taht@gmail.com \
--cc=cerowrt-devel@lists.bufferbloat.net \
--cc=dpreed@deepplum.com \
--cc=mcr@sandelman.ca \
/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