Linux Advanced Routing and Traffic Control list
 help / color / mirror / Atom feed
From: Tomasz Orzechowski <tmo@apk.net>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] 150.150. addresses
Date: Thu, 21 Jun 2001 02:27:38 +0000	[thread overview]
Message-ID: <marc-lartc-99309055921602@msgid-missing> (raw)
In-Reply-To: <marc-lartc-99309192123806@msgid-missing>

adelphia wrote on Wed, Jun 20, 2001 at 10:24:18PM -0400:
> Are 150.150.*.* adresses private or reserve addresses?
> My friend has a one, and I tried doing an nslookup, ping, and traceroute
> with no luck.

$ whois -h whois.arin.net 150.150.1.1 
LG-EDS Systems Inc. (NET-LGEDS-NET)
   555 Hogae-Dong,Dongan-Gu
   AnYang-Si KyungKi-Do 430-080
   KR

   Netname: LGEDS-NET
   Netblock: 150.150.0.0 - 150.150.255.255

gw5#sh ip bgp 150.150.1.1
BGP routing table entry for 150.150.0.0/16, version 1869114
Paths: (2 available, best #2, table Default-IP-Routing-Table)
  Not advertised to any peer
  701 2828 3786 6068
    157.130.96.149 from 157.130.96.149 (137.39.2.106)
      Origin IGP, localpref 100, valid, external
  2548 3786 6068
    209.49.240.185 (metric 20) from 209.221.31.9 (209.221.31.9)
      Origin IGP, metric 720501, localpref 100, valid, internal, best

why ask here? :-)
-- 
Tomasz Orzechowski                                           tmo@apk.net
APK.net systems administration team                                TO630


_______________________________________________
LARTC mailing list / LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/mailman/listinfo/lartc HOWTO: http://ds9a.nl/2.4Routing/

  reply	other threads:[~2001-06-21  2:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-06-21  2:24 [LARTC] 150.150. addresses adelphia
2001-06-21  2:27 ` Tomasz Orzechowski [this message]
2001-06-21  6:42 ` Fredrik Björk

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=marc-lartc-99309055921602@msgid-missing \
    --to=tmo@apk.net \
    --cc=lartc@vger.kernel.org \
    /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