From astro at spaceboyz.net Sun Aug 1 02:16:49 2010 From: astro at spaceboyz.net (Astro) Date: Sun, 1 Aug 2010 02:16:49 +0200 Subject: [dn42] DN42 Dns Frontend In-Reply-To: <4C5456EC.6040506@cyb0rg.org> References: <4C5456EC.6040506@cyb0rg.org> Message-ID: <20100801001649.GO2271@chronos.sin> Crest wrote: > The scripts should offer an interface like this: > res dns add --domain crest.dn42 \ > --nserver ns1.crest.dn42 172.22.228.6 \ > --nserver ns2.crest.dn42 172.22.180.46 \ > --status connect \ > --admin-c CREST-DN42 \ > --tech-c CREST-DN42 > > res commit && res sync +1 I like that. From admin at crystalnet.eu Sun Aug 1 15:54:58 2010 From: admin at crystalnet.eu (Lukas Wingerberg) Date: Sun, 1 Aug 2010 15:54:58 +0200 Subject: [dn42] DN42 Dns Frontend In-Reply-To: <4C544FC6.4020706@cyb0rg.org> References: <4C501A91.2080603@cyb0rg.org> <4C544FC6.4020706@cyb0rg.org> Message-ID: well, planned atm is as stated on the wiki page: have the webinterface work directly with the registry so when ppl are done editing all theyre stuff on the webinterfac e's local registry copy they click on "safe" / "push changes" so theyre changes will get pushed into the monotone server after theyre done editing On Sat, Jul 31, 2010 at 6:31 PM, Crest wrote: > SRN schrieb: > > crest at cyb0rg.org (Crest) writes: > > > >> SRN schrieb: > >>> admin at crystalnet.eu (Cronix) writes: > >>> > >>>> Im currently collecting ideas / feature requests etc for the > webinterface > >>>> i write to use with the current registry, if u have any particular > >>>> features or anything else in mind, please let me know and write it > down at > >>>> the wiki page i created for this purpose: > >>>> http://dn42.net/trac/wiki/dnsWebinterface > >>> Hi cronix, > >>> > >>> I notice you haven't yet implemented the part that manages the actual > >>> records. I'd like to take this opportunity to suggest a format, and if > >>> it sounds good, I can then implement the script to autogenerate > datafiles > >>> for crazydns nameservice to power domains managed by your webinterface. > >>> My suggestion is to place the contents of the zone directly in the > >>> data/dns/.dn42 file, as records named "dnsrecord." Here's what > >>> data/dns/crazydns.dn42 might look like, with my current proposal: > >>> domain: crazydns.dn42 > >>> nserver: somerandomcrap.ns.crazydns.dn42 172.22.53.55 > >>> nserver: someothercrap.ns.crazydns.dn42 172.22.53.56 > >>> status: connect > >>> admin-c: SRN-DN42 > >>> tech-c: SRN-DN42 > >>> dnsrecord: A:www.crazydns.dn42:172.22.53.80 > >>> dnsrecord: A:a.rootns.crazydns.dn42:172.22.53.50 > >>> dnsrecord: A:a.dn42ns.crazydns.dn42:172.22.53.51 > >>> dnsrecord: A:a.rdns.crazydns.dn42:172.22.53.52 > >>> dnsrecord: A:a.dnscache.crazydns.dn42:172.22.53.53 > >>> dnsrecord: A:a.smallblockrdns.crazydns.dn42:172.22.53.54 > >>> > >>> What do you think of my current proposal? I see some strengths and > some > >>> weaknesses, but I don't see any way to improve it off-hand. Do you? > >>> Does anybody else? > > > >> How about the bind zonefile format? I would use one $INCLUDE per zone. > > > > The fundamental problem with the bind zonefile format is that it's harder > > to parse. I was actually going to propose the tinydns datafile format > > (which is even easier to parse), but I decided to stick with something > > that's easier for humans to read/write too given that the cost to achieve > > it is minimal. > > > >> e.g. "master/dn42": > >> $ORIGIN . > >> $TTL 24h > >> dn42 IN SOA nic.dn42. root.nic.dn42. ( > >> 2010072800 ; serial > >> 4h ; refresh > >> 1h ; retry > >> 2w ; expire > >> 2d ; minimum > >> ) > >> ... > >> $INCLUDE master/dn42_include/crest > >> ... > > > >> and "master/dn42_include/crest": > >> crest.dn42. NS ns1.crest.dn42. > >> crest.dn42. NS ns2.crest.dn42. > >> ns1.crest.dn42 A 172.22.228.6 > >> ns2.crest.dn42 A 172.22.228.46 > > > > You want to do all this in separate files, rather than in the > > data/dns/crest.dn42 file? > > I would reject anything that implies manual duplication. I would > replace it. > > >> The format is reasonably simple to write for your Webinterface and > >> directly usable by BIND. > > > > ...and essentially unusable by anything else that may have to parse it > > (including the webinterface itself) :-( > > Not as long as you can rely on the webinterface to generate a subset of > that what's readable by BIND. > > > My proposed format is usable by BIND, tinydns, or anything else, with > > a simple one-line script in nearly any language. It's also trivial > > to validate. The only downside is that if you have a TXT record > > with a colon in the record data, parsing rules become ambiguous. > > And (newlines or 0 character etc.). Your're right we should be able to > transport any valid value. Base64 to the rescue? > > > If you want to address that type of issue, my suggestion is to make a > > data/dns/crazydns.dn42.d/rr/ directory: > > $ cat data/dns/crazydns.dn42.d/rr/www.crazydns.dn42/0 > > name: www.crazydns.dn42 > > type: A > > data: 172.22.53.80 > > > > This scheme is nowhere near perfect, because of an "ancient" > > assumption that all "dns" data would fit in a flat name:value table. > > If we were starting from scratch, I'd rename data/dns/crazydns.dn42 to > > data/dns/crazydns.dn42/whois. > > > >> IMO the internal format is more or less unimportant as long as it's > >> exported into the monotone repo in whoisd's format. > > > > My proposal is not to have any separate "internal" format, but rather > > to use the repo directly. It simplifies implementation, and provides > > reliability for free. > > Sry i didn't meant to replace the current format with BIND's insane > formats. I tought the webfrontend should also generate ID-10-T > compatible zonefiles. > > >> e.g. "data/dns/crest.dn42" > >> domain: crest.dn42 > >> nserver: ns1.crest.dn42 172.22.228.6 > >> nserver: ns2.crest.dn42 172.22.180.46 > >> status: connect-webif > >> admin-c: CREST-DN42 > >> tech-c: CREST-DN42 > > > > Interesting, so you're (ab)using the status field instead of (ab)using > > the tech-c field. Why do you think that's better? (Before you ask, > > I'm not sure why I think tech-c is better, except that it comes closer > > to agreeing with (my perception of) reality.) > > Neither status nor tech-c are meant to be for this. I think tech-c with > an extra handle is the cleaner approach as it doesn't create subformats. > > _______________________________________________ > dn42 mailing list > dn42 at lists.spaceboyz.net > http://lists.spaceboyz.net/mailman/listinfo/dn42 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From nick at srn.dn42 Tue Aug 3 20:36:28 2010 From: nick at srn.dn42 (SRN) Date: Tue, 3 Aug 2010 18:36:28 +0000 (UTC) Subject: [dn42] DN42 Dns Frontend References: <4C5456EC.6040506@cyb0rg.org> <20100801001649.GO2271@chronos.sin> Message-ID: astro at spaceboyz.net (Astro) writes: >Crest wrote: >> The scripts should offer an interface like this: >> res dns add --domain crest.dn42 \ >> --nserver ns1.crest.dn42 172.22.228.6 \ >> --nserver ns2.crest.dn42 172.22.180.46 \ >> --status connect \ >> --admin-c CREST-DN42 \ >> --tech-c CREST-DN42 >> >> res commit && res sync >+1 I like that. TBPH, I'm not quite sure what's wrong with the ancient copy-and-modify approach, but I guess the nice thing about your approach is that nobody is required to use it, so you obviously have a +1 from me if it makes dn42 easier for _someone_ to use. (Based on the posts I'm replying to, there are at least two.) -- Their mad rush in getting us out of the country is the greatest proof to me that I have served the cause of humanity, that I have never wavered or compromised. -- Emma Goldman From nick at srn.dn42 Tue Aug 3 21:14:51 2010 From: nick at srn.dn42 (SRN) Date: Tue, 3 Aug 2010 19:14:51 +0000 (UTC) Subject: [dn42] DN42 Dns Frontend References: <4C501A91.2080603@cyb0rg.org> <4C544FC6.4020706@cyb0rg.org> Message-ID: crest at cyb0rg.org (Crest) writes: >SRN schrieb: >> crest at cyb0rg.org (Crest) writes: >> >>> SRN schrieb: >>>> admin at crystalnet.eu (Cronix) writes: >>>> >>>>> Im currently collecting ideas / feature requests etc for the webinterface >>>>> i write to use with the current registry, if u have any particular >>>>> features or anything else in mind, please let me know and write it down at >>>>> the wiki page i created for this purpose: >>>>> http://dn42.net/trac/wiki/dnsWebinterface >>>> Hi cronix, >>>> >>>> I notice you haven't yet implemented the part that manages the actual >>>> records. I'd like to take this opportunity to suggest a format, and if >>>> it sounds good, I can then implement the script to autogenerate datafiles >>>> for crazydns nameservice to power domains managed by your webinterface. >>>> My suggestion is to place the contents of the zone directly in the >>>> data/dns/.dn42 file, as records named "dnsrecord." Here's what >>>> data/dns/crazydns.dn42 might look like, with my current proposal: >>>> domain: crazydns.dn42 >>>> nserver: somerandomcrap.ns.crazydns.dn42 172.22.53.55 >>>> nserver: someothercrap.ns.crazydns.dn42 172.22.53.56 >>>> status: connect >>>> admin-c: SRN-DN42 >>>> tech-c: SRN-DN42 >>>> dnsrecord: A:www.crazydns.dn42:172.22.53.80 >>>> dnsrecord: A:a.rootns.crazydns.dn42:172.22.53.50 >>>> dnsrecord: A:a.dn42ns.crazydns.dn42:172.22.53.51 >>>> dnsrecord: A:a.rdns.crazydns.dn42:172.22.53.52 >>>> dnsrecord: A:a.dnscache.crazydns.dn42:172.22.53.53 >>>> dnsrecord: A:a.smallblockrdns.crazydns.dn42:172.22.53.54 >>>> >>>> What do you think of my current proposal? I see some strengths and some >>>> weaknesses, but I don't see any way to improve it off-hand. Do you? >>>> Does anybody else? >> >>> How about the bind zonefile format? I would use one $INCLUDE per zone. >> >> The fundamental problem with the bind zonefile format is that it's harder >> to parse. I was actually going to propose the tinydns datafile format >> (which is even easier to parse), but I decided to stick with something >> that's easier for humans to read/write too given that the cost to achieve >> it is minimal. >> >>> e.g. "master/dn42": >>> $ORIGIN . >>> $TTL 24h >>> dn42 IN SOA nic.dn42. root.nic.dn42. ( >>> 2010072800 ; serial >>> 4h ; refresh >>> 1h ; retry >>> 2w ; expire >>> 2d ; minimum >>> ) >>> ... >>> $INCLUDE master/dn42_include/crest >>> ... >> >>> and "master/dn42_include/crest": >>> crest.dn42. NS ns1.crest.dn42. >>> crest.dn42. NS ns2.crest.dn42. >>> ns1.crest.dn42 A 172.22.228.6 >>> ns2.crest.dn42 A 172.22.228.46 >> >> You want to do all this in separate files, rather than in the >> data/dns/crest.dn42 file? >I would reject anything that implies manual duplication. I would >replace it. How would the data/dns/ directory look, then? >>> The format is reasonably simple to write for your Webinterface and >>> directly usable by BIND. >> >> ...and essentially unusable by anything else that may have to parse it >> (including the webinterface itself) :-( >Not as long as you can rely on the webinterface to generate a subset of >that what's readable by BIND. The tinydns datafile format can actually represent a non-trivial superset of what's readable by bind within the IN class. >> My proposed format is usable by BIND, tinydns, or anything else, with >> a simple one-line script in nearly any language. It's also trivial >> to validate. The only downside is that if you have a TXT record >> with a colon in the record data, parsing rules become ambiguous. >And (newlines or 0 character etc.). Your're right we should be able to >transport any valid value. Base64 to the rescue? If you're serious about representing arbitrary bytestrings, my suggestion is to use the input format of cdbmake (http://cr.yp.to/cdb/cdbmake.html) for each file rather than the WHOIS format currently used, and to represent values with multiple parts (like the nserver values in data/dns/whatever.dn42 files) as concatenations of netstrings. This way, we remain 100% readable by normal humans, while being able to represent arbitrary bytestrings reliably. The only downside is that now it becomes a bit of a pain to hand-write these files, so I guess we'll probably see more guys creating scripts similar to the one you were talking about in a separate thread. >> If you want to address that type of issue, my suggestion is to make a >> data/dns/crazydns.dn42.d/rr/ directory: >> $ cat data/dns/crazydns.dn42.d/rr/www.crazydns.dn42/0 >> name: www.crazydns.dn42 >> type: A >> data: 172.22.53.80 >> >> This scheme is nowhere near perfect, because of an "ancient" >> assumption that all "dns" data would fit in a flat name:value table. >> If we were starting from scratch, I'd rename data/dns/crazydns.dn42 to >> data/dns/crazydns.dn42/whois. >> >>> IMO the internal format is more or less unimportant as long as it's >>> exported into the monotone repo in whoisd's format. >> >> My proposal is not to have any separate "internal" format, but rather >> to use the repo directly. It simplifies implementation, and provides >> reliability for free. >Sry i didn't meant to replace the current format with BIND's insane >formats. I tought the webfrontend should also generate ID-10-T >compatible zonefiles. The webfrontend, IMHO, should simply load data into the registry. It's the responsibility of nameserver operators to export the DNS data in any format they want (presumably, using some zonegen-type scripts). >>> e.g. "data/dns/crest.dn42" >>> domain: crest.dn42 >>> nserver: ns1.crest.dn42 172.22.228.6 >>> nserver: ns2.crest.dn42 172.22.180.46 >>> status: connect-webif >>> admin-c: CREST-DN42 >>> tech-c: CREST-DN42 >> >> Interesting, so you're (ab)using the status field instead of (ab)using >> the tech-c field. Why do you think that's better? (Before you ask, >> I'm not sure why I think tech-c is better, except that it comes closer >> to agreeing with (my perception of) reality.) >Neither status nor tech-c are meant to be for this. I think tech-c with >an extra handle is the cleaner approach as it doesn't create subformats. with an extra handle? -- Their mad rush in getting us out of the country is the greatest proof to me that I have served the cause of humanity, that I have never wavered or compromised. -- Emma Goldman From nick at srn.dn42 Tue Aug 3 22:10:04 2010 From: nick at srn.dn42 (SRN) Date: Tue, 3 Aug 2010 20:10:04 +0000 (UTC) Subject: [dn42] DN42 Dns Frontend References: <4C5456EC.6040506@cyb0rg.org> Message-ID: crest at cyb0rg.org (Crest) writes: >I'm working on some scripts to make the repo more user and script friendly. >The scripts should offer an interface like this: > res dns add --domain crest.dn42 \ > --nserver ns1.crest.dn42 172.22.228.6 \ > --nserver ns2.crest.dn42 172.22.180.46 \ > --status connect \ > --admin-c CREST-DN42 \ > --tech-c CREST-DN42 > > res commit && res sync >Their is an other problem to discuss. How do we want do store arbitrary >binary data in the current format? Hex? Base64? My suggestion is to use netstrings instead of base64 or hex, for two important reasons: 1) Hex and base64 require substantial expansion of the payload. 2) Hex and base64 are difficult for humans and greps to read. -- Their mad rush in getting us out of the country is the greatest proof to me that I have served the cause of humanity, that I have never wavered or compromised. -- Emma Goldman From h0arry at h0arry.de Wed Aug 25 22:50:02 2010 From: h0arry at h0arry.de (Harald-Alfred Wurpts) Date: Wed, 25 Aug 2010 22:50:02 +0200 Subject: [dn42] Looking for Tunnel/BGP Peer Message-ID: <4C7581FA.4050506@h0arry.de> Hi everbody, i?m new to dn42. And look for a IPv4 Tunnel / Peer. AS64781 172.22.181.0/24 Hardware : 1und1 V-Server openvpn / quagga -- Harry From dn42-net at bauani.org Thu Aug 26 10:53:28 2010 From: dn42-net at bauani.org (Ahamed Bauani) Date: Thu, 26 Aug 2010 14:53:28 +0600 (BDT) Subject: [dn42] Looking for Tunnel/BGP Peer Message-ID: <20100826085333.17C262668032@smtp.dhaka-wireless.net> Hi Harry I am also new in Dn42 and your email catch my eyes. Now please confirm me if you are looking for BGP for Ipv4 or IPv6 Traffic or Anoucing your /24 IPv4 prefix. Or you are looking for a BGP peer to collect BGP data around the world or you need a connectivity to IPv6 Internet from your IPv4 network. Please let me know details. Ahamed Bauani My Technology Blog >On Thu, Aug 26, 2010 at 2:50 AM, Harald-Alfred Wurpts wrote: > Hi everbody, >i?m new to dn42. And look for a IPv4 Tunnel / Peer. >AS64781 >172.22.181.0/24 >Hardware : 1und1 V-Server >openvpn / quagga >-- >Harry >_______________________________________________ >dn42 mailing list >dn42 at lists.spaceboyz.net >http://lists.spaceboyz.net/mailman/listinfo/dn42 From tobias at linuxdingsda.de Thu Aug 26 11:20:22 2010 From: tobias at linuxdingsda.de (Tobias Winter) Date: Thu, 26 Aug 2010 11:20:22 +0200 Subject: [dn42] Looking for Tunnel/BGP Peer In-Reply-To: <4C7581FA.4050506@h0arry.de> References: <4C7581FA.4050506@h0arry.de> Message-ID: <4C7631D6.40404@linuxdingsda.de> Am 25.08.2010 22:50, schrieb Harald-Alfred Wurpts: > Hi everbody, > > i?m new to dn42. And look for a IPv4 Tunnel / Peer. > > AS64781 > 172.22.181.0/24 > > Hardware : 1und1 V-Server > openvpn / quagga > feel free to hit me in jabber. wintix at jabber.ccc.de From nobody at nowhere.ws Thu Aug 26 12:48:23 2010 From: nobody at nowhere.ws (nobody) Date: Thu, 26 Aug 2010 12:48:23 +0200 Subject: [dn42] MUA-Settings (Was: Looking for Tunnel/BGP Peer) In-Reply-To: <20100826085333.17C262668032@smtp.dhaka-wireless.net> References: <20100826085333.17C262668032@smtp.dhaka-wireless.net> Message-ID: <20100826104823.GA5245@ts2server.com> Hi, could you please fix your MUA to add an "In-Reply-To" or "References" header when you reply to mails? Thanks. -nobody From mail at simonzoellner.de Thu Aug 26 20:27:42 2010 From: mail at simonzoellner.de (=?UTF-8?Q?Simon_Z=C3=B6llner?=) Date: Thu, 26 Aug 2010 20:27:42 +0200 Subject: [dn42] Looking for Tunnel/BGP Peer In-Reply-To: <4C7581FA.4050506@h0arry.de> References: <4C7581FA.4050506@h0arry.de> Message-ID: <3c12379688ac9f8c15b18aa3129ec868@simon-zoellner.de> Hi Harry, for peering partners best join the IRC channel. There's usualy somebody in it, also at night. If you ask there, you'll have success. If you want to peer with me, contact Bonix in IRC Channel! BUT REMEMBER: Always register your net on the http://dn42.net/trac/wiki/IPv4Topologie Page! Simon On Wed, 25 Aug 2010 22:50:02 +0200, Harald-Alfred Wurpts wrote: > Hi everbody, > > i?m new to dn42. And look for a IPv4 Tunnel / Peer. > > AS64781 > 172.22.181.0/24 > > Hardware : 1und1 V-Server > openvpn / quagga From frapzzt at ccc.de Sun Aug 29 19:53:14 2010 From: frapzzt at ccc.de (frapzzt) Date: Sun, 29 Aug 2010 19:53:14 +0200 Subject: [dn42] mrmcd anyone Message-ID: <4C7A9E8A.1050402@ccc.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hi, dn42 at mrmcd? we are using as13020 - 94.45.224.0/19 - 2001:41b8:201::/48 https://mrmcd1001b.metarheinmain.de/ anyone there who brings a node and wants to peer? cheers --frapzzt -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) iEYEARECAAYFAkx6nooACgkQ39rh4kgD6O84QwCbBg/tiXR9Q3cLjg122htOVAGi LvoAn3qk/P5kjS8CKkVg1WZLExrqjiHf =QMos -----END PGP SIGNATURE----- From tobias.fiebig at wouldyoubuythis.net Sun Aug 29 22:25:21 2010 From: tobias.fiebig at wouldyoubuythis.net (Tobias Fiebig) Date: Sun, 29 Aug 2010 22:25:21 +0200 Subject: [dn42] mrmcd anyone In-Reply-To: <4C7A9E8A.1050402@ccc.de> References: <4C7A9E8A.1050402@ccc.de> Message-ID: <30270a5a6a603b5f6278df389a450568@mail.wouldyoubuythis.net> Moin, > dn42 at mrmcd? > we are using as13020 - 94.45.224.0/19 - 2001:41b8:201::/48 > https://mrmcd1001b.metarheinmain.de/ > anyone there who brings a node and wants to peer? wuerds wieder von as64677 ausm albinokontor announcen. schreib dich da die tage mal an. Mit freundlichen Grueszen, Tobias From dn42-net at bauani.org Sun Aug 29 22:55:57 2010 From: dn42-net at bauani.org (Ahamed Bauani [http://bd-servers.net]) Date: Mon, 30 Aug 2010 02:55:57 +0600 Subject: [dn42] mrmcd anyone In-Reply-To: <4C7A9E8A.1050402@ccc.de> References: <4C7A9E8A.1050402@ccc.de> Message-ID: Hello, I am from Bangladesh and ready to peer with anyone. My ASN is: AS55364 IPv4 Prefix 175.158.96.0/22 IPv6 Prefix: 2403:1200::/32 Let me know how can I help you and the volume of traffic you want to transit through me. Best Regards Ahamed Bauani On Sun, Aug 29, 2010 at 11:53 PM, frapzzt wrote: > -----BEGIN PGP SIGNED MESSAGE----- > Hash: SHA1 > > hi, > dn42 at mrmcd? > we are using as13020 - 94.45.224.0/19 - 2001:41b8:201::/48 > https://mrmcd1001b.metarheinmain.de/ > anyone there who brings a node and wants to peer? > cheers > --frapzzt > -----BEGIN PGP SIGNATURE----- > Version: GnuPG/MacGPG2 v2.0.14 (Darwin) > > iEYEARECAAYFAkx6nooACgkQ39rh4kgD6O84QwCbBg/tiXR9Q3cLjg122htOVAGi > LvoAn3qk/P5kjS8CKkVg1WZLExrqjiHf > =QMos > -----END PGP SIGNATURE----- > > _______________________________________________ > dn42 mailing list > dn42 at lists.spaceboyz.net > http://lists.spaceboyz.net/mailman/listinfo/dn42 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From frapzzt at ccc.de Sun Aug 29 23:46:36 2010 From: frapzzt at ccc.de (frapzzt) Date: Sun, 29 Aug 2010 23:46:36 +0200 Subject: [dn42] mrmcd anyone In-Reply-To: <30270a5a6a603b5f6278df389a450568@mail.wouldyoubuythis.net> References: <4C7A9E8A.1050402@ccc.de> <30270a5a6a603b5f6278df389a450568@mail.wouldyoubuythis.net> Message-ID: <4C7AD53C.7000208@ccc.de> -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 hab dieses mal nur equipment vor ort. kein vpn was in berlin terminiert wird. ich werd mit leon mal nen peering ?ber gre probieren falls keiner vor ort ist von euch. cheers --frapzzt Tobias Fiebig wrote: > Moin, >> dn42 at mrmcd? >> we are using as13020 - 94.45.224.0/19 - 2001:41b8:201::/48 >> https://mrmcd1001b.metarheinmain.de/ >> anyone there who brings a node and wants to peer? > > wuerds wieder von as64677 ausm albinokontor announcen. schreib dich da die > tage mal an. > > Mit freundlichen Grueszen, > Tobias > > _______________________________________________ > dn42 mailing list > dn42 at lists.spaceboyz.net > http://lists.spaceboyz.net/mailman/listinfo/dn42 -----BEGIN PGP SIGNATURE----- Version: GnuPG/MacGPG2 v2.0.14 (Darwin) iEYEARECAAYFAkx61TwACgkQ39rh4kgD6O/nXwCbBDGgCbqt4Ls966yZaEYzSYmn bmQAnRsIgpP6NugbXjm94zpjDjhztnMN =sHSk -----END PGP SIGNATURE----- From docsteel at docsteel.de Sun Aug 29 23:53:46 2010 From: docsteel at docsteel.de (Docsteel) Date: Sun, 29 Aug 2010 23:53:46 +0200 Subject: [dn42] mrmcd anyone In-Reply-To: <4C7AD53C.7000208@ccc.de> References: <4C7A9E8A.1050402@ccc.de> <30270a5a6a603b5f6278df389a450568@mail.wouldyoubuythis.net> <4C7AD53C.7000208@ccc.de> Message-ID: <4C7AD6EA.40008@docsteel.de> Am 08/29/2010 11:46 PM, schrieb frapzzt: > hab dieses mal nur equipment vor ort. kein vpn was in berlin terminiert wird. > > ich werd mit leon mal nen peering ?ber gre probieren falls keiner vor ort ist von euch. Hallo Ich bin, da ich ja in der Uni arbeite, auch vor Ort und kann Hardware und Peering anbieten. Gru? Doc From dn42-net at bauani.org Mon Aug 30 09:37:55 2010 From: dn42-net at bauani.org (Ahamed Bauani [http://bd-servers.net]) Date: Mon, 30 Aug 2010 13:37:55 +0600 Subject: [dn42] mrmcd anyone In-Reply-To: <4C7AD6EA.40008@docsteel.de> References: <4C7A9E8A.1050402@ccc.de> <30270a5a6a603b5f6278df389a450568@mail.wouldyoubuythis.net> <4C7AD53C.7000208@ccc.de> <4C7AD6EA.40008@docsteel.de> Message-ID: Hay Hay Hay, Man, English Please. Thanks Ahamed Bauani 2010/8/30 Docsteel > Am 08/29/2010 11:46 PM, schrieb frapzzt: > > hab dieses mal nur equipment vor ort. kein vpn was in berlin terminiert > wird. > > > > ich werd mit leon mal nen peering ?ber gre probieren falls keiner vor ort > ist von euch. > > Hallo > > Ich bin, da ich ja in der Uni arbeite, auch vor Ort und kann Hardware > und Peering anbieten. > > Gru? > Doc > > _______________________________________________ > dn42 mailing list > dn42 at lists.spaceboyz.net > http://lists.spaceboyz.net/mailman/listinfo/dn42 > -------------- next part -------------- An HTML attachment was scrubbed... URL: From equinox at diac24.net Mon Aug 30 14:34:15 2010 From: equinox at diac24.net (David Lamparter) Date: Mon, 30 Aug 2010 14:34:15 +0200 Subject: [dn42] Peering (was: mrmcd anyone) In-Reply-To: References: <4C7A9E8A.1050402@ccc.de> Message-ID: <20100830123415.GB2170790@jupiter.n2.diac24.net> On Mon, Aug 30, 2010 at 02:55:57AM +0600, Ahamed Bauani [http://bd-servers.net] wrote: > AS55364 > > IPv4 Prefix 175.158.96.0/22 > IPv6 Prefix: 2403:1200::/32 You're trying to peer with public ASN and IPv4. While this can be done, it is not generally recommended. Please be aware that dn42 is a virtual network, so to speak an isolated insula in the internet. dn42 peerings are not "peerings" in the internet BGP sense, and the only networks/people you can reach are other dn42 participants. You cannot reach any other regular internet user through dn42. dn42 is NOT an internet exchange point! -equinox -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 198 bytes Desc: not available URL: From dn42-net at bauani.org Mon Aug 30 21:11:34 2010 From: dn42-net at bauani.org (Ahamed Bauani [http://bd-servers.net]) Date: Tue, 31 Aug 2010 01:11:34 +0600 Subject: [dn42] Peering (was: mrmcd anyone) In-Reply-To: <20100830123415.GB2170790@jupiter.n2.diac24.net> References: <4C7A9E8A.1050402@ccc.de> <20100830123415.GB2170790@jupiter.n2.diac24.net> Message-ID: Hello equinox Thanks for your writing. I was know that this is a virtual community. But I don't know how to apply for a /24 IP address from DN42.Net. I know how to create or the system of ASN Number Assignment from DN42, but can't don't know how to apply for IP address. I am Technology Advisor of an ISP here in Dhaka, Bangladesh. My plan is to give access to my user in both DN42 Network and Public Internet. Few of my customer want to access DNS42 from their home. So, If I can create a gateway, which have DN42 Peering Information (BGP Info) then I can redirect my users request to their destination. I will be glad if you inform me how I can get DN42 IPv4 address , if possible IPv6 also. Best Regards Ahamed Bauani On Mon, Aug 30, 2010 at 6:34 PM, David Lamparter wrote: > On Mon, Aug 30, 2010 at 02:55:57AM +0600, Ahamed Bauani [ > http://bd-servers.net] wrote: > > AS55364 > > > > IPv4 Prefix 175.158.96.0/22 > > IPv6 Prefix: 2403:1200::/32 > > You're trying to peer with public ASN and IPv4. While this can be done, > it is not generally recommended. > > Please be aware that dn42 is a virtual network, so to speak an isolated > insula in the internet. dn42 peerings are not "peerings" in the internet > BGP sense, and the only networks/people you can reach are other dn42 > participants. > > You cannot reach any other regular internet user through dn42. > > dn42 is NOT an internet exchange point! > > > -equinox > > -------------- next part -------------- An HTML attachment was scrubbed... URL: From crest at cyb0rg.org Mon Aug 30 22:12:41 2010 From: crest at cyb0rg.org (Crest) Date: Mon, 30 Aug 2010 22:12:41 +0200 Subject: [dn42] Peering In-Reply-To: References: <4C7A9E8A.1050402@ccc.de> <20100830123415.GB2170790@jupiter.n2.diac24.net> Message-ID: <4C7C10B9.9090806@cyb0rg.org> Ahamed Bauani [http://bd-servers.net] schrieb: > Thanks for your writing. I was know that this is a virtual community. But I > don't know how to apply for a /24 IP address from DN42.Net. I know how to > create or the system of ASN Number Assignment from DN42, but can't don't > know how to apply for IP address. The dn42 (than called diac24) started as a small project by a few geeks. Resources where "managed" my claiming them and documenting this claim in a wiki. This scaled further than expected. Since the wiki isn't well scriptable and a single point of failure we setup a Monotone repository to document resource allocation. We claim 172.22.0.0/15 and AS64600 - AS65111. The IPv4 range 172.22.0.0/15 is defined as private by RFC1918. It shoudn't appear on the public internet. The same applies for AS64600 - AS5111. The dn42 has no ruling body of any kind. Discussions take place on the mailing list and #dn42 in the hackint IRC network. Because of this I can't speak for the rest of the dn42 members, but imo the dn42 is an infrastructure made by nerds for nerds to experiment with routing protocols creating something more or less usable by accident. To answer your question: read the how to peer page [1] documenting one individuals view on how a peering might be established. Join the #dn42 IRC channel in the hackint [2] IRC network. Btw most of us live in the CEST timezone so expect some phase shift. Ask the remaining questions in the IRC channel and document the result somewhere if you want to (dn42.net wiki, this mailing list). > I am Technology Advisor of an ISP here in Dhaka, Bangladesh. My plan is to > give access to my user in both DN42 Network and Public Internet. Few of my > customer want to access DNS42 from their home. Their are few services in the dn42. Even fewer which i expect to be of interest to an average ISP customer. The most important goal of the dn42 is to enable it's participants to learn about routing protocols in the wild. Offering access to the dn42 via their default route to your customers you would take this from opportunity to learn from them. > So, If I can create a gateway, which have DN42 Peering Information (BGP > Info) then I can redirect my users request to their destination. Than you have taken them the opportunity to learn who to get access themself. That said please don't bring the Eternal September [3] over us. > I will be glad if you inform me how I can get DN42 IPv4 address , if > possible IPv6 also. The most common setup is an OpenVPN tunnel in p2p mode link and BGP over this tunnel. Find peers (via IRC) and peer with them if they want (given your usecase). Feel free to peer for yourself, but please neither force your customers on use nor us on your customers. [1] : https://dn42.net/trac/wiki/HowToPeer [2] : http://hackint.eu [3] : http://en.wikipedia.org/wiki/Eternal_September From dn42-net at bauani.org Tue Aug 31 12:05:04 2010 From: dn42-net at bauani.org (Ahamed Bauani [http://bd-servers.net]) Date: Tue, 31 Aug 2010 16:05:04 +0600 Subject: [dn42] Peering In-Reply-To: <4C7C10B9.9090806@cyb0rg.org> References: <4C7A9E8A.1050402@ccc.de> <20100830123415.GB2170790@jupiter.n2.diac24.net> <4C7C10B9.9090806@cyb0rg.org> Message-ID: Thanks for your email reply with details of information. On Tue, Aug 31, 2010 at 2:12 AM, Crest wrote: > Ahamed Bauani [http://bd-servers.net] schrieb: > > Thanks for your writing. I was know that this is a virtual community. But > I > > don't know how to apply for a /24 IP address from DN42.Net. I know how to > > create or the system of ASN Number Assignment from DN42, but can't don't > > know how to apply for IP address. > > The dn42 (than called diac24) started as a small project by a few geeks. > Resources where "managed" my claiming them and documenting this claim in > a wiki. This scaled further than expected. Since the wiki isn't well > scriptable and a single point of failure we setup a Monotone repository > to document resource allocation. We claim 172.22.0.0/15 and AS64600 - > AS65111. The IPv4 range 172.22.0.0/15 is defined as private by RFC1918. > It shoudn't appear on the public internet. The same applies for AS64600 > - AS5111. > > I must read the article / documentation you provided. > The dn42 has no ruling body of any kind. Discussions take place on the > mailing list and #dn42 in the hackint IRC network. Because of this I > can't speak for the rest of the dn42 members, but imo the dn42 is an > infrastructure made by nerds for nerds to experiment with routing > protocols creating something more or less usable by accident. > > To answer your question: read the how to peer page [1] documenting one > individuals view on how a peering might be established. Join the #dn42 > IRC channel in the hackint [2] IRC network. Btw most of us live in the > CEST timezone so expect some phase shift. Ask the remaining questions in > the IRC channel and document the result somewhere if you want to > (dn42.net wiki, this mailing list). > > As most of us are too lazy or too busy, don't care to read the documentation. Like nobody (I think 99.1% ) tech public don't ready RFC like documents. This is a natural process of human being to read plan text with 3 or 4 page . > > I am Technology Advisor of an ISP here in Dhaka, Bangladesh. My plan is > to > > give access to my user in both DN42 Network and Public Internet. Few of > my > > customer want to access DNS42 from their home. > > Their are few services in the dn42. Even fewer which i expect to be of > interest to an average ISP customer. The most important goal of the dn42 > is to enable it's participants to learn about routing protocols in the > wild. Offering access to the dn42 via their default route to your > customers you would take this from opportunity to learn from them. > > Sure, I will guide them, if possible take a class of 1 or 2 hour in week so that they can understand the process and by joining with DN42, they can use it as a LAB, hand to hand practice. > So, If I can create a gateway, which have DN42 Peering Information (BGP > > Info) then I can redirect my users request to their destination. > > Than you have taken them the opportunity to learn who to get access > themself. That said please don't bring the Eternal September [3] over us. > > I am not forcing any traffic to DN42, Actually the the people ask me to give access to your private network. Other thing, the subscriber who ask for access to DN42 is not average user, Most of them is student and my low level network operating center's staff, who want to learn real world experience of BGP and Internet Routing both for IPv4 & 6. > > I will be glad if you inform me how I can get DN42 IPv4 address , if > > possible IPv6 also. > > > The most common setup is an OpenVPN tunnel in p2p mode link and BGP over > this tunnel. Find peers (via IRC) and peer with them if they want (given > your usecase). Feel free to peer for yourself, but please neither force > your customers on use nor us on your customers. > > [1] : https://dn42.net/trac/wiki/HowToPeer > [2] : http://hackint.eu > [3] : http://en.wikipedia.org/wiki/Eternal_September > Last, I am very glad to be member of DIAC24 Community. Hope to utilize this opportunity to reach to Goal of this project. By the way, I like to work voleenteering job. My current project is ' http://www.bd-servers.net/ ' & Deployment of IPv6 in our Country. Our Government has no Headache to deploy or get preparation to adapt IPv6 as soon as possible. Last of all, Thank you for your friendly discussion, due to the Time Zone factor it might not possible for join with you guys on IRC, but everything has exception. Right. Hope to be in IRC one day. -- Regards Ahamed Bauani http://www.bauani.org/ -------------- next part -------------- An HTML attachment was scrubbed... URL: