September 2011 - Test - lists.nanog.org

Saudi Telecom sending route with invalid attributes 212.118.142.0/24
by Jonas Frey (Probe Networks) 20 Sep '11

20 Sep '11

Hello, anyone else getting a route for 212.118.142.0/24 with invalid attributes? Seems this is (again) causing problems with some (older) routers/software. Announcement bits (4): 0-KRT 3-KRT 5-Resolve tree 1 6-Resolve tree 2 AS path: 6453 39386 25019 I Unrecognized Attributes: 39 bytes AS path: Attr flags e0 code 80: 00 00 fd 88 40 01 01 02 40 02 04 02 01 5b a0 c0 11 04 02 01 fc da 80 04 04 00 00 00 01 40 05 04 00 00 00 64 Accepted Multipath -Jonas

11 15

Is yahoo seriously blocking emails with variants of the words "occupywallstreet"?
by Landon Stewart 19 Sep '11

19 Sep '11

Hi Guys, Is yahoo seriously blocking emails with variants of the words "occupywallstreet"? -- Landon Stewart <LStewart(a)SUPERB.NET> SuperbHosting.Net by Superb Internet Corp. Toll Free (US/Canada): 888-354-6128 x 4199 Direct: 206-438-5879 Web hosting and more "Ahead of the Rest": http://www.superbhosting.net

2 1

Re: How to begin making my own ISP?
by Valdis.Kletnieks＠vt.edu 19 Sep '11

19 Sep '11

On Fri, 16 Sep 2011 18:42:18 -0000, bmanning(a)vacation.karoshi.com said: > Configure Quagga w/ the obtained ASN and announce the IP prefix(es). > TaDa ... You are an ISP! Now all you need is a business plan that pays for the rack space. ;)

3 2

IPv6 side of www.charter.com has been down since Friday, September 16 5:12 am Central
by Frank Bulk 19 Sep '11

19 Sep '11

The IPv6 side of www.charter.com has been down since Friday, September 16 5:12 am Central. Emails to their NOC have gone unanswered. If anyone on list can nudge their ops group that would be appreciated. Frank nagios:/home/fbulk# wget -6 www.charter.com --2011-09-19 08:23:58-- http://www.charter.com/ Resolving www.charter.com... 2607:f428:3:1:80:80:80:1 Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:24:20-- (try: 2) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:24:43-- (try: 3) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:25:07-- (try: 4) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:25:32-- (try: 5) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:25:58-- (try: 6) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:26:25-- (try: 7) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:26:53-- (try: 8) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:27:22-- (try: 9) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:27:52-- (try:10) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:28:23-- (try:11) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:28:54-- (try:12) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:29:25-- (try:13) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:29:56-- (try:14) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:30:27-- (try:15) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:30:58-- (try:16) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:31:29-- (try:17) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:32:00-- (try:18) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:32:31-- (try:19) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:33:02-- (try:20) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Giving up. nagios:/home/fbulk#

3 4

RE: IPv6 side of www.charter.com has been down since Friday, September 16 5:12 am Central
by Nick Olsen 19 Sep '11

19 Sep '11

Takes our HE tunnel to get out. Were also Native with Cogent (Not that it gets us anything..) No dice. [root@bench ~]# wget -6 www.charter.com --2011-09-19 13:53:17-- http://www.charter.com/ Resolving www.charter.com... 2607:f428:3:1:80:80:80:1 Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... Times Out [root@bench ~]# traceroute6 www.charter.com traceroute to www.charter.com (2607:f428:3:1:80:80:80:1), 30 hops max, 40 byte packets 1 (2606:2400:141::1) 1.169 ms 1.157 ms 1.145 ms 2 (2606:2400:222::d) 31.685 ms 36.812 ms 37.104 ms 3 (2606:2400:222::5) 37.387 ms 37.456 ms 37.477 ms 4 brevardwireless-1.tunnel.tserv7.ash1.ipv6.he.net (2001:470:1f0d:c5::1) 123.090 ms 123.371 ms 123.334 ms 5 v104.core1.ash1.he.net (2001:470:0:40::2) 122.542 ms 122.523 ms 122.516 ms 6 10gigabitethernet1-2.core1.atl1.he.net (2001:470:0:1b5::2) 142.508 ms 129.220 ms 131.762 ms 7 2001:470:0:115::2 (2001:470:0:115::2) 131.537 ms 131.696 ms 131.739 ms 8 bbr01sghlga-tge0-2-0-1.ga.sghl.charter.com (2001:506:100:326::1) 143.856 ms bbr01sghlga-tge0-0-0-0.ga.sghl.charter.com (2001:506:100:308::1) 140.164 ms 140.196 ms 9 bbr01blvlil-tge0-3-0-4.il.blvl.charter.com (2001:506:100:42::2) 151.880 ms 152.019 ms 151.955 ms 10 bbr01olvemo-tge0-1-0-6.mo.olve.charter.com (2001:506:100:8::1) 151.669 ms 151.681 ms 151.665 ms 11 bdr01tncomo-tge1-1.mo.tnco.charter.com (2001:506:100:23::2) 149.784 ms 149.851 ms 149.852 ms 12 2001:506:100:6c::2 (2001:506:100:6c::2) 147.953 ms 147.470 ms 147.479 ms 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * Nick Olsen Network Operations (855) FLSPEED x106 ---------------------------------------- From: "Frank Bulk" <frnkblk(a)iname.com> Sent: Monday, September 19, 2011 1:38 PM To: "PC" <paul4004(a)gmail.com> Subject: RE: IPv6 side of www.charter.com has been down since Friday, September 16 5:12 am Central I've been told by someone else offline that it's fine for them, too. Last hop according to tcptraceroute6 is Qwest. Anyone else going to www.charter.com (IPv6) through Qwest? nagios:/home/fbulk# tcptraceroute6 www.charter.com traceroute to www.charter.com (2607:f428:3:1:80:80:80:1) from 2607:fe28:0:1000::5, port 80, from port 43838, 30 hops max, 60 bytes packets 1 2607:fe28:0:1003::2 (2607:fe28:0:1003::2) 1.075 ms 1.258 ms 1.857 ms 2 router-core.mtcnet.net (2607:fe28:0:1000::1) 1.625 ms 2.271 ms 1.331 ms 3 sxct.sxcy.mtcnet.net (2607:fe28:11:1002::197) 2.581 ms 1.568 ms 1.215 ms 4 v6-siouxcenter.sxcy.137.netins.net (2001:5f8:7f06::5) 3.347 ms 3.007 ms 2.640 ms 5 v6-ins-db1-te-13-2-219.desm.netins.net (2001:5f8:1:1::1) 7.441 ms 7.121 ms 6.798 ms 6 v6-ins-dc1-et-8-2.desm.netins.net (2001:5f8::1:1) 8.682 ms 8.294 ms 7.910 ms 7 2001:428:3801:210:0:1:0:1 (2001:428:3801:210:0:1:0:1) 20.790 ms 20.447 ms 20.133 ms 8 * * * 9 * * * 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * 15 * * * 16 * * * 17 * * * 18 * * * 19 * * * 20 * * * 21 * * * 22 * * * 23 * * * 24 * * * 25 * * * 26 * * * 27 * * * 28 * * * 29 * * * 30 * * * nagios:/home/fbulk# Frank From: PC [mailto:paul4004@gmail.com] Sent: Monday, September 19, 2011 12:13 PM To: frnkblk(a)iname.com Cc: nanog(a)nanog.org Subject: Re: IPv6 side of www.charter.com has been down since Friday, September 16 5:12 am Central Works fine here. # wget -6 www.charter.com --2011-09-19 10:24:37-- http://www.charter.com/ Resolving www.charter.com... 2607:f428:3:1:80:80:80:1 Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... connected. HTTP request sent, awaiting response... 200 OK Length: unspecified [text/html] Saving to: `index.html' [ <=> ] 112,940 288K/s in 0.4s 2011-09-19 10:24:43 (288 KB/s) - `index.html' saved [112940] traceroute to www.charter.com (2607:f428:3:1:80:80:80:1), 30 hops max, 80 byte packets 1 2607:f2f8:xxxx::1 (2607:f2f8:xxxx::1) 18.721 ms 18.699 ms 18.689 ms 2 2001:504:13::1a (2001:504:13::1a) 1.256 ms 1.672 ms 1.428 ms 3 10gigabitethernet1-2.core1.den1.he.net (2001:470:0:15d::1) 26.498 ms 26.486 ms 26.466 ms 4 10gigabitethernet1-1.core1.chi1.he.net (2001:470:0:1af::1) 49.986 ms 49.529 ms 49.521 ms 5 2001:470:0:114::2 (2001:470:0:114::2) 50.105 ms 49.632 ms 49.626 ms 6 bbr02chcgil-tge0-1-0-0.il.chcg.charter.com (2001:506:100:313::1) 55.805 ms 54.254 ms bbr02chcgil-tge0-0-0-0.il.chcg.charter.com (2001:506:100:305::1) 55.880 ms 7 bbr01olvemo-tge0-4-0-4.mo.olve.charter.com (2001:506:100:55::1) 69.465 ms 63.351 ms 63.314 ms 8 bdr01tncomo-tge1-1.mo.tnco.charter.com (2001:506:100:23::2) 60.018 ms 59.597 ms 59.586 ms 9 2001:506:100:6c::2 (2001:506:100:6c::2) 60.251 ms 60.245 ms 60.236 ms 10 * * * 11 * * * 12 * * * 13 * * * 14 * * * On Mon, Sep 19, 2011 at 11:08 AM, Frank Bulk <frnkblk(a)iname.com> wrote: The IPv6 side of www.charter.com has been down since Friday, September 16 5:12 am Central. Emails to their NOC have gone unanswered. If anyone on list can nudge their ops group that would be appreciated. Frank nagios:/home/fbulk# wget -6 www.charter.com --2011-09-19 08:23:58-- http://www.charter.com/ Resolving www.charter.com... 2607:f428:3:1:80:80:80:1 Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:24:20-- (try: 2) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:24:43-- (try: 3) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:25:07-- (try: 4) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:25:32-- (try: 5) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:25:58-- (try: 6) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:26:25-- (try: 7) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:26:53-- (try: 8) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:27:22-- (try: 9) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:27:52-- (try:10) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:28:23-- (try:11) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:28:54-- (try:12) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:29:25-- (try:13) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:29:56-- (try:14) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:30:27-- (try:15) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:30:58-- (try:16) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:31:29-- (try:17) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:32:00-- (try:18) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:32:31-- (try:19) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Retrying. --2011-09-19 08:33:02-- (try:20) http://www.charter.com/ Connecting to www.charter.com|2607:f428:3:1:80:80:80:1|:80... failed: Connection timed out. Giving up. nagios:/home/fbulk#

5 4

ouch..
by Martin Hepworth 18 Sep '11

18 Sep '11

http://www.overpromisesunderdelivers.net/ -- Martin Hepworth Oxford, UK

28 33

Traceroute losses through NYC1.gblx.net?
by Steve Bohrer 17 Sep '11

17 Sep '11

My general question is "what meaning do I give to lossy traceroutes, even when pings show no problem." Can I expect that backbone routers should never give me timeouts on a traceroute through them, so, lots of asterisks from these systems indicate a packet loss problem that needs to be fixed? Or, are these traceroute asterisks essentially meaningless, and should be expected on any busy link? More specifically, is anyone else getting lots of *s for NYC1.gblx.net for traceroutes through them? If I do three traceroutes through there, at least one will show losses at or beyond the NYC1 hops (and, the *s beyond NYC1 might be getting lost in NYC1, rather than indicating a different error). But, Global Crossing's on-line tools don't show any loss. I am at simons-rock.edu, in Western Mass, and we connect via Boston. A few days ago, our users of a database that's hosted at our parent campus, bard.edu, started complaining of many frequent (but intermittent) delays. Bard is in the Hudson Valley, and connects via Poughkeepsie. Both of our local providers connect to Global Crossing. Once before, we saw similar database symptoms, and that time, Bard had a problem dropping packets at their gateway. So I think these symptoms mean packet loss is happening somewhere. However, this time, pings from Simon's Rock to Bard, and vice-versa, show essentially no errors, typically 1000 pings will get through 100%. Still, despite the good pings, traceroutes from either end show lots of asterisks at or after Global Crossing's NYC1.gblx.net links. I have opened a ticket with our provider, who has opened one with Global Crossing; and Bard has done the same with their end, but no significant response so far. (Bard's Graduate campus, located in New York City, is having similar poor database performance, so I'm pretty sure it is not just my end. Staff at the main Bard campus have no troubles, so it seems a network problem, not a server problem.) As I understand it, an asterisk in traceroute means that the sending machine did not get any reply to a given packet. Since the traceroute packets have small TTL values, it expects to get a reply when the TTL is decremented to zero. But, I don't know if big routers are just lazy about sending such responses, or if these asterisks really indicate packets getting lost. (As far as I remember in the past, when things work well, I never see *s at the central links, but, I have not really done any baseline testing of the link from here to Bard when the database was working.) So, another question is why pings work so well when traceroutes work so poorly. (By experiment, I believe our database application performs more like traceroute than like ping.) Is it packet size? Different handling for different sorts of traffic? Magic? Here are some sample traceroutes each way: Simon's Rock to Bard: 2h189:bin skbohrer$ traceroute -q5 -S bip.bard.edu traceroute to bip.bard.edu (192.246.228.16), 64 hops max, 40 byte packets 1 10.30.2.1 (10.30.2.1) 1.514 ms 1.791 ms 0.684 ms 0.761 ms 0.712 ms (0% loss) 2 michael.simons-rock.edu (208.81.88.1) 2.509 ms 1.882 ms 0.899 ms 1.345 ms 2.057 ms (0% loss) 3 64.213.79.249 (64.213.79.249) 104.294 ms 10.605 ms 17.106 ms 18.987 ms 38.740 ms (0% loss) 4 pos2-0-155M.cr2.BOS1.gblx.net (67.17.70.166) 21.962 ms 20.411 ms 8.394 ms 23.308 ms 10.192 ms (0% loss) 5 so1-2-0-2488M.scr2.NYC1.gblx.net (67.17.94.158) 15.738 ms 14.582 ms 17.306 ms 24.444 ms 15.466 ms (0% loss) 6 ae3-30g.scr3.NYC1.gblx.net (67.17.104.189) 15.586 ms 13.358 ms ae0-30G.scr4.NYC1.gblx.net (67.16.139.2) 13.875 ms 13.495 ms 12.780 ms (0% loss) 7 e5-1-30G.ar9.NYC1.gblx.net (67.16.142.54) 75.184 ms lag1.ar9.NYC1.gblx.net (67.16.142.50) 15.766 ms 11.947 ms * e5-1-30G.ar9.NYC1.gblx.net (67.16.142.54) 25.916 ms (20% loss) 8 * * wbs-connect.gigabitethernet1-0-2.asr1.jfk1.gblx.net (64.211.195.6) 55.909 ms 73.803 ms * (60% loss) 9 * pghknyshj42-xe-0-3-0.lightower.net (72.22.160.150) 16.521 ms 21.817 ms 23.715 ms 17.236 ms (20% loss) 10 pghknyshj91-ae0-66.lightower.net (72.22.160.165) 76.257 ms 27.712 ms 20.372 ms 18.923 ms 55.355 ms (0% loss) 11 kgtnnykgj91-ae3.66.lightower.net (72.22.160.107) 18.088 ms 51.631 ms 19.052 ms 20.876 ms 22.942 ms (0% loss) 12 BardCollege-cust.customer.hvdata.net (64.72.66.234) 51.243 ms 47.800 ms 32.835 ms 19.040 ms 55.661 ms (0% loss) 13 *^C Bard to SR (their version of traceroute doen't have the handy -S option): SRDB/users/usrsr/finrep: traceroute mail.simons-rock.edu trying to get source for mail.simons-rock.edu source should be 10.20.11.23 traceroute to hedwig.simons-rock.edu (208.81.88.14) from 10.20.11.23 (10.20.11.23), 30 hops max outgoing MTU = 1500 1 hcrcgw (10.20.11.1) 1 ms 0 ms 0 ms 2 hyphen (192.246.235.1) 1 ms 1 ms 1 ms 3 BardCollege-hvdn.customer.hvdata.net (64.72.66.233) 1 ms 1 ms 1 ms 4 pghknyshj91-xe-5-2-0.lightower.net (72.22.160.106) 2 ms 2 ms 2 ms 5 pghknyshj42-ae0-66.lightower.net (72.22.160.159) 27 ms 2 ms 2 ms 6 nycmnyzrj42-xe-0-3-0.lightower.net (72.22.160.151) 4 ms 4 ms 4 ms 7 ve463.ar9.NYC1.gblx.net (64.211.195.5) 4 ms 4 ms 4 ms 8 * ae0-40G.scr1.NYC1.gblx.net (67.16.138.253) 4 ms 4 ms 9 pos5-0-2488M.cr1.BOS1.gblx.net (67.17.94.57) 9 ms pos9-0-2488M.cr2.BOS1.gblx.net (67.17.94.157) 9 ms 11 ms 10 pos1-0-0-155M.ar1.BOS1.gblx.net (67.17.70.165) 14 ms 10 ms 9 ms 11 64.213.79.250 (64.213.79.250) 15 ms 15 ms 18 ms ^C For more automated testing, I used -m10 to set the max hops so that the traces stop within the backbone network, as this avoids any issue of the boxes at the ends not really responding to traceroutes. That way, I could assume any * was a real time out. I also used -q4 for 4 queries to each host. With a few hundred traceroutes each direction, more than 75% from SR to Bard, and more than 94% from Bard to SR, showed an asterisk at or past the NYC1 hops. There were zero asterisks on the links before NYC1 from either side. Thanks for any insights. Steve Bohrer Network Administrator ITS, Bard College at Simon's Rock 413-528-7645

4 3

Disappointing ARIN - A great advertisement for the USA ?
by Always Learning 17 Sep '11

17 Sep '11

Hallo North Americans, I am from Europe. A contributor on the Centos (the largest Red Hat clone) list suggested I reposted my ARIN item on your list. I have a BASH script called .w It contains #! /bin/bash whois $1 host $1 When I type .w 51.51.51.51 I receive a normal and conventional display of data because that IP address is not 'organised' by ARIN. When I type:- .w 64.64.64.64 I receive a one line summary of possible matches, which always includes ARIN, but omits the details we used to receive before ARIN implemented its much criticised "improved" service. My second script .wa is more useful for North American IP enquiries:- #! /bin/bash whois -h whois.arin.net n + $1 host $1 On some occasions I get a normal display of Northern American data. The 'n' and '+' are not part of WHOIS. They are ARIN's own parameters. This example produces a 'near-as-possible-because-it-is-ARIN' display:- .wa 65.65.65.65 However when ARIN automatically forwards the query to a North American RWHOIS the query is apparently malformed and nothing useful is displayed. For example:- .wa 66.66.66.66 The Internet was created in North America. Many people around the world would appreciate your help in getting ARIN to revert to normal WHOIS displays. ARIN wants enquirers to click on web page after web page to try and find the information previously displayed in a single response. Frankly that weird attitude is stark raving bonkers! -- With best regards, Paul. England, EU.

19 39

Re: ouch..
by Scott Weeks 17 Sep '11

17 Sep '11

--- brandon.galbraith(a)gmail.com wrote: From: Brandon Galbraith <brandon.galbraith(a)gmail.com> Juniper: Who needs to waste time with pathetic marketing videos when you're gear just works. --------------------------------------------------- Unless it's the ERX series. Blech, it puts a bad taste in my mouth just writing the acronym ERX. Thank $deity that I don't have to work on those anymore... scott

9 10

IPV6 over a PPTP Link
by Meftah Tayeb 17 Sep '11

17 Sep '11

Hello, can i ofer ipv6 addresses through a PPTP connection using cisco ? if yes, how please ? Thank you Meftah Tayeb IT Consulting http://www.tmvoip.com/ phone: +21321656139 Mobile: +213660347746 __________ Information provenant d'ESET NOD32 Antivirus, version de la base des signatures de virus 6465 (20110915) __________ Le message a été vérifié par ESET NOD32 Antivirus. http://www.eset.com

4 7