Skip to content

Commit 0812ec6

Browse files
tohojotohojo
committed
Add generated files from issue conversion.
1 parent a196f4f commit 0812ec6

File tree

389 files changed

+64635
-0
lines changed

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

389 files changed

+64635
-0
lines changed

‎content/bloat/issues/41.md‎

Lines changed: 39 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,39 @@
1+
2+
---
3+
title: "Bug #41: Battlemesh - Jim Gettys appearance "
4+
subject: "Battlemesh - Jim Gettys appearance "
5+
date: 2011-03-05T10:26:14
6+
updated: 2011-03-21T14:03:11
7+
type: issue
8+
author: Dave Täht
9+
id: 41
10+
issue_status: Closed
11+
priority: Normal
12+
assignee: Jim Gettys
13+
aliases:
14+
- /issues/41
15+
---
16+
17+
{{< issue_description >}}
18+
Jim Gettys will be giving two talks at the upcoming [Battlemesh
19+
conference](http://battlemesh.org/BattleMeshV4/Agenda) March 16-19, in\
20+
Sant Bartomeu del Grau (SBG for short), near Barcelona, Catalunia,
21+
Spain.
22+
23+
One will be a condensed version of the existing Bell Labs bufferbloat
24+
talk, the other will be about OLPC meltdowns.
25+
26+
There are also interesting talks scheduled about babel-z, the mesh
27+
potato, and other topics of interest to the mesh networking community.
28+
29+
Not to mention the battle of the mesh technologies! I have some hope
30+
that the best debloated router will win!
31+
32+
33+
{{< /issue_description >}}
34+
35+
## History
36+
{{< issue_journal date="2011-03-21T14:03:11" author="Dave Täht" >}}
37+
Appearance given...
38+
{{< /issue_journal >}}
39+

‎content/bloat/issues/index.md‎

Lines changed: 4 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,4 @@
1+
---
2+
type: issuesindex
3+
title: Bloat
4+
---

‎content/cerowrt/issues/110.md‎

Lines changed: 47 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,47 @@
1+
2+
---
3+
title: "Bug #110: dhcpd/named not restarted on network restart"
4+
subject: "dhcpd/named not restarted on network restart"
5+
date: 2011-05-03T16:40:51
6+
updated: 2014-06-24T20:03:25
7+
type: issue
8+
author: Evan Hunt
9+
id: 110
10+
issue_status: Closed
11+
priority: Normal
12+
assignee: Evan Hunt
13+
aliases:
14+
- /issues/110
15+
---
16+
17+
{{< issue_description >}}
18+
Restarting the network in iscwrt does not restart dhcpd; subsequent
19+
DHCPDISCOVERs are not answered.
20+
21+
Restarting named is less urgent but ought to be done anyway
22+
23+
24+
{{< /issue_description >}}
25+
26+
## History
27+
{{< issue_journal date="2011-05-07T21:47:56" author="Dave Täht" >}}
28+
Given what we now know about rndc and how slow named can be to restart,
29+
perhaps a kinder/gentler way than exists in files/hotplug.d/iface (rndc
30+
reload config?network?) can be used in named-latest, and regardless the
31+
method I put in place there, it needs to be tested.
32+
33+
Similar fix would be a good idea for dhcp, whatever works...
34+
{{< /issue_journal >}}
35+
{{< issue_journal date="2011-09-04T19:28:39" author="Dave Täht" >}}
36+
37+
{{< /issue_journal >}}
38+
{{< issue_journal date="2011-09-20T10:22:30" author="Jim Gettys" >}}
39+
40+
{{< /issue_journal >}}
41+
{{< issue_journal date="2012-04-21T12:42:04" author="Dave Täht" >}}
42+
43+
{{< /issue_journal >}}
44+
{{< issue_journal date="2014-06-24T20:03:25" author="Dave Täht" >}}
45+
46+
{{< /issue_journal >}}
47+

‎content/cerowrt/issues/118.md‎

Lines changed: 44 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,44 @@
1+
2+
---
3+
title: "Bug #118: SFB requires a new iproute2"
4+
subject: "SFB requires a new iproute2"
5+
date: 2011-05-07T21:33:42
6+
updated: 2013-03-27T23:32:04
7+
type: issue
8+
author: Dave Täht
9+
id: 118
10+
issue_status: Closed
11+
priority: Normal
12+
assignee: Jim Gettys
13+
aliases:
14+
- /issues/118
15+
---
16+
17+
{{< issue_description >}}
18+
While you can use SFB without a newer tc, it helps to control it better
19+
if you have a new tc.
20+
21+
The tc utility is heavily dependended on by other tools, so instead of
22+
using a separate feed for it, we need to patch openwt.
23+
24+
25+
{{< /issue_description >}}
26+
27+
## History
28+
{{< issue_journal date="2011-07-10T15:19:33" author="Dave Täht" >}}
29+
the new iproute2 is in cerowrt. Seems to work.
30+
31+
Needs to get pushed back into openwrt, after a few days of testing.
32+
{{< /issue_journal >}}
33+
{{< issue_journal date="2011-07-27T20:08:46" author="Dave Täht" >}}
34+
35+
{{< /issue_journal >}}
36+
{{< issue_journal date="2011-08-03T07:14:49" author="Dave Täht" >}}
37+
Needs to be thoroughly tested in the testplan.
38+
{{< /issue_journal >}}
39+
{{< issue_journal date="2013-03-27T23:32:04" author="夕 颜" >}}
40+
Best http://www.ahappydeal.com/notebook-umpc-c-95.html: top budget
41+
options - Get your hands on the best tablet ￡300 can get you - or just
42+
under two Nexus 7s. Buying advice fro.
43+
{{< /issue_journal >}}
44+

‎content/cerowrt/issues/122.md‎

Lines changed: 43 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,43 @@
1+
2+
---
3+
title: "Bug #122: DNSSec enabled and split dns enabled default setup"
4+
subject: "DNSSec enabled and split dns enabled default setup"
5+
date: 2011-05-07T23:13:31
6+
updated: 2012-04-21T12:42:07
7+
type: issue
8+
author: Dave Täht
9+
id: 122
10+
issue_status: Feedback
11+
priority: Normal
12+
assignee: Jim Gettys
13+
aliases:
14+
- /issues/122
15+
---
16+
17+
{{< issue_description >}}
18+
with a DNSSec enabled and split dns enabled default setup that "just
19+
worked" out of the box, bind could be an adaquate substitute and
20+
superset for dnsmasq in the name services case.
21+
22+
That said dnsmasq has a much tighter integration with dhcp than we do at
23+
present.
24+
25+
On the gripping hand, it would be a great proof of concept
26+
27+
28+
{{< /issue_description >}}
29+
30+
## History
31+
{{< issue_journal date="2011-07-10T15:06:02" author="Dave Täht" >}}
32+
out of the box dnssec configuration done in cerowrt.
33+
{{< /issue_journal >}}
34+
{{< issue_journal date="2011-09-01T17:51:42" author="Dave Täht" >}}
35+
we got as close as we could with this.
36+
{{< /issue_journal >}}
37+
{{< issue_journal date="2011-09-20T10:22:31" author="Jim Gettys" >}}
38+
39+
{{< /issue_journal >}}
40+
{{< issue_journal date="2012-04-21T12:42:07" author="Dave Täht" >}}
41+
42+
{{< /issue_journal >}}
43+

‎content/cerowrt/issues/123.md‎

Lines changed: 84 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,84 @@
1+
2+
---
3+
title: "Bug #123: dyndns and bind-latest integration scripts"
4+
subject: "dyndns and bind-latest integration scripts"
5+
date: 2011-05-07T23:16:03
6+
updated: 2014-06-24T20:03:27
7+
type: issue
8+
author: Dave Täht
9+
id: 123
10+
issue_status: Closed
11+
priority: Normal
12+
assignee: Evan Hunt
13+
aliases:
14+
- /issues/123
15+
---
16+
17+
{{< issue_description >}}
18+
I have put the last known version of the bind integration scripts into
19+
the ceropackage repository as an openwrt package.
20+
21+
https://github.com/dtaht/ceropackages/tree/master/net/bind-dhcp-hooks
22+
23+
Regrettably it depends on dhcp-latest and is out of sync with the work
24+
in progress.
25+
26+
27+
{{< /issue_description >}}
28+
29+
## History
30+
{{< issue_journal date="2011-08-03T07:50:03" author="Dave Täht" >}}
31+
The issues here are fairly large. Because isc-dhcp is targetted at large
32+
providers (100s of queries/sec), and not the home (20 queries/day), and
33+
the most current isc-dhcpv6 includes all of bind9, I ripped it out and
34+
at least temporarily replaced it with just using dnsmasq as a dhcp
35+
server, where it has full GUI support, and is quite smaller.
36+
37+
0\) There is no need for dhcpv6 inside the home. Stateless
38+
autoconfiguration + dhcpv4 leveraging the generated EUI-64, suffices for
39+
99% of all ipv6 capable devices.
40+
41+
1\) The dnsscripts that leveraged dhcpv4 addresses and turned them into
42+
stateless autoconfig ipv6 addresses, and inserted them into bind were
43+
dependent on evan's dual domain system, and not quite as view capable as
44+
they needed to be, where you would typically want to publish SOME
45+
addresses, but not all
46+
47+
2\) They didn't speak dnsmasq's syntax for it's plugin script, but
48+
isc-dhcp's.
49+
50+
3\) They didn't pick up on the dynamically assigned 6to4 or 6in4
51+
addresses generated by openwrt.
52+
53+
4\) In the shorter term, I'd like a dhcp server that ran out of xinetd.
54+
That would allow for locking out misbehaving, worm-ridden, devices from
55+
even getting on the network. I found one that looked pretty good.
56+
57+
http://inetdxtra.sourceforge.net/
58+
59+
5\) In the longer term, merging the functionality of AHCPD (the mesh
60+
network ip address distribution daemon) with dhcpv4 and dhcpv6 seems the
61+
right way to go, to get a common lease table and address distribution
62+
method that works both with conventional systems and mesh ones.
63+
64+
This work is already taking place elsewhere. I have no idea what
65+
schedule it is on.
66+
67+
AHCPD:
68+
69+
http://www.pps.jussieu.fr/~jch/software/ahcp/
70+
71+
As I don't think any of these issues can be fixed in the time remaining,
72+
I'm scheduling these for the next cerowrt release, and further
73+
discussion of approaches.
74+
{{< /issue_journal >}}
75+
{{< issue_journal date="2011-09-20T10:22:32" author="Jim Gettys" >}}
76+
77+
{{< /issue_journal >}}
78+
{{< issue_journal date="2012-04-21T12:42:08" author="Dave Täht" >}}
79+
80+
{{< /issue_journal >}}
81+
{{< issue_journal date="2014-06-24T20:03:27" author="Dave Täht" >}}
82+
83+
{{< /issue_journal >}}
84+

‎content/cerowrt/issues/125.md‎

Lines changed: 54 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,54 @@
1+
2+
---
3+
title: "Bug #125: ECN blacklist iptables rules"
4+
subject: "ECN blacklist iptables rules"
5+
date: 2011-05-07T23:24:05
6+
updated: 2014-06-24T20:03:30
7+
type: issue
8+
author: Dave Täht
9+
id: 125
10+
issue_status: Closed
11+
priority: Normal
12+
assignee: Steven Bauer
13+
aliases:
14+
- /issues/125
15+
---
16+
17+
{{< issue_description >}}
18+
Much like we have email blacklists, a malfunctioning ECN server
19+
blacklist could be maintained, and used as a standard iptables rule, to
20+
prevent ECN negotiation to malfunctioning hosts.
21+
22+
It could use ipset to check for malfunctioning hosts on connect and
23+
rsync or wget to periodically update the file, much like how spam
24+
sources are tracked today. It would be awesome if it could check
25+
automagically and phone home with the data...
26+
27+
28+
{{< /issue_description >}}
29+
30+
## History
31+
{{< issue_journal date="2011-05-08T11:23:16" author="Steven Bauer" >}}
32+
Lets discuss... most ECN "problems" are caused by network elements of
33+
one sort or another (routers, switches, load balancers, etc).
34+
35+
So a ECN **server** blacklist perhaps isn't quite the right thing.
36+
Moreover, ECN problems can be introduced by a device very close to the
37+
client. For such a client, essentially the entire Internet would have to
38+
be blacklisted. (This in fact was exactly the case at my lab before it
39+
was fixed.)
40+
41+
Now, perhaps your point is there are servers that have topologically
42+
close problems and those could reasonably be put on a global list so
43+
everyone doesn't go negotiating an ECN connection that ends up broken.
44+
Could be fairly large list. But even here since ECN brokenness is a path
45+
issue, the blacklist might not be correct for some clients depending
46+
upon the network topology and the location of the problems.
47+
{{< /issue_journal >}}
48+
{{< issue_journal date="2011-07-27T20:08:23" author="Dave Täht" >}}
49+
50+
{{< /issue_journal >}}
51+
{{< issue_journal date="2014-06-24T20:03:30" author="Dave Täht" >}}
52+
53+
{{< /issue_journal >}}
54+

0 commit comments

Comments
 (0)