Development issues regarding the cerowrt test router project
 help / color / mirror / Atom feed
* [Cerowrt-devel] dhcp-pd and source specific routing on debian
@ 2015-06-18 22:41 Dave Taht
  2015-06-19  1:35 ` Dave Taht
  0 siblings, 1 reply; 2+ messages in thread
From: Dave Taht @ 2015-06-18 22:41 UTC (permalink / raw)
  To: cerowrt-devel

after much flailing with dibbler, wide, and dhclient...

I have finally got dhcp-pd + source specific routing to work on
debian, using odhcp6c.


I have no idea what is going on with reverse dns here but:

d@nuc-client:~/git/sch_beatcake$ traceroute6 -s 2601:646:8301:c5f1::1
www.bufferbloat.net
traceroute to www.bufferbloat.net (2001:4f8:3:36::52) from
2601:646:8301:c5f1::1, 30 hops max, 24 byte packets
 1  www.googletagmanager.com (2601:646:8301:c500:225:90ff:fef4:a5c4)
0.275 ms  0.204 ms  0.161 ms
 2  * * *
 3  www.googletagmanager.com (2001:558:5027:51::1)  8.665 ms  8.699 ms
 10.112 ms
 4  www.googletagmanager.com (2001:558:82:2623::1)  9.385 ms  8.972 ms
 10.073 ms
 5  www.googletagmanager.com (2001:558:80:212::1)  9.309 ms  8.989 ms  9.548 ms
 6  * * *
 7  www.googletagmanager.com (2001:558:0:f5a9::2)  9.658 ms  10.876 ms  9.899 ms
 8  www.googletagmanager.com (2001:559::14e)  9.424 ms  11.18 ms  9.497 ms
 9  www.googletagmanager.com (2001:4f8:0:1::5:1)  11.067 ms  9.506 ms  11.616 ms
10  www.googletagmanager.com (2001:4f8:1b:1::8:2)  12.557 ms  12.153 ms  13.8 ms
11  www.googletagmanager.com (2001:4f8:3:36::52)  8.957 ms  8.76 ms  9.488 ms

d@nuc-client:~/git/sch_beatcake$ traceroute6 -s 2601:646:8300:2cba::1
www.bufferbloat.net
traceroute to www.bufferbloat.net (2001:4f8:3:36::52) from
2601:646:8300:2cba::1, 30 hops max, 24 byte packets
 1  www.googletagmanager.com (fe80::28c6:8eff:febb:9ff0)  0.443 ms
0.354 ms  0.28 ms
 2  * * *
 3  * * *
 4  www.googletagmanager.com (2601:646:8300:2cb0::1)  2.504 ms  2.282
ms  1.564 ms
 5  www.googletagmanager.com (2001:558:5027:51::1)  14.086 ms  15.424
ms  14.248 ms
 6  www.googletagmanager.com (2001:558:82:2623::1)  17.162 ms  10.897
ms  14.545 ms
 7  www.googletagmanager.com (2001:558:80:212::1)  18.25 ms  27.213 ms
 16.436 ms
 8  * * *
 9  www.googletagmanager.com (2001:558:0:f5a4::2)  13.617 ms  15.873
ms  14.308 ms
10  www.googletagmanager.com (2001:559::14e)  19.537 ms  15.939 ms  11.806 ms
11  www.googletagmanager.com (2001:4f8:0:1::5:1)  14.385 ms  14.925 ms
 18.257 ms
12  www.googletagmanager.com (2001:4f8:1b:1::8:2)  15.643 ms  15.596
ms  19.233 ms
13  www.googletagmanager.com (2001:4f8:3:36::52)  15.562 ms  11.155 ms
 11.737 ms

-- 
Dave Täht
worldwide bufferbloat report:
http://www.dslreports.com/speedtest/results/bufferbloat
And:
What will it take to vastly improve wifi for everyone?
https://plus.google.com/u/0/explore/makewififast

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: [Cerowrt-devel] dhcp-pd and source specific routing on debian
  2015-06-18 22:41 [Cerowrt-devel] dhcp-pd and source specific routing on debian Dave Taht
@ 2015-06-19  1:35 ` Dave Taht
  0 siblings, 0 replies; 2+ messages in thread
From: Dave Taht @ 2015-06-19  1:35 UTC (permalink / raw)
  To: cerowrt-devel

I retract that. The default scripts flush the existing addresses every
30 seconds.  That would be fine if I wasn't also getting a long
duration address from RA that also gets flushed. Feeding this into dns
every 30 seconds is not fun either...

The route stuff is fixible using a proto and a replace rather than
"add"... a replace does an add if not found, and otherwise updates the
lifetime.

(ideas borrowed from the hnetd code)

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2015-06-19  1:35 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2015-06-18 22:41 [Cerowrt-devel] dhcp-pd and source specific routing on debian Dave Taht
2015-06-19  1:35 ` Dave Taht

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox