[arin-tech-discuss] arin-tech-discuss Jennifer marshall

Andy Newton andy at arin.net
Tue Jun 14 13:31:51 EDT 2011


Jennifer,

RFC 1918 defines all addresses within 192.168.xxx.xxx as private IP space. This address is most likely being supplied to your computer from your cable or wireless router. Your router translates and aggregates requests from these addresses into a single, publicly routable IP address given to your router from your ISP. To find the publicly routable IP address your router is using, go to http://www.arin.net and look at the very top where it says "Your IP address is".

Andy Newton
Chief Engineer, ARIN

On Jun 14, 2011, at 1:14 PM, Jen wrote:

> could someone tell me what my iP address is my Internet provider keeps telling me it starts with 184. but when I use the utilities on my Mac it says I am redirected to 192.168.78.  2. I am not a computer savy person at all. but why am I getting redirected  does that mean something?? any help would be appreciated. also I printed out something that looks strange it appears that 64.4.61.212 through port 1863 has been trying to connect to me
> 
> 
> 
> On Jun 14, 2011, at 11:00 AM, arin-tech-discuss-request at arin.net wrote:
> 
>> Send arin-tech-discuss mailing list submissions to
>>   arin-tech-discuss at arin.net
>> 
>> To subscribe or unsubscribe via the World Wide Web, visit
>>   http://lists.arin.net/mailman/listinfo/arin-tech-discuss
>> or, via email, send a message with subject or body 'help' to
>>   arin-tech-discuss-request at arin.net
>> 
>> You can reach the person managing the list at
>>   arin-tech-discuss-owner at arin.net
>> 
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of arin-tech-discuss digest..."
>> 
>> 
>> Today's Topics:
>> 
>>  1. Re: arin-tech-discuss Digest, Vol 7, Issue 3 (Zhao, Sean)
>> 
>> 
>> ----------------------------------------------------------------------
>> 
>> Message: 1
>> Date: Mon, 13 Jun 2011 14:37:33 -0600
>> From: "Zhao, Sean" <Sean.Zhao at qwest.com>
>> To: "'Tim Christensen'" <timc at arin.net>, "Grimes, Ronald"
>>   <Ron.Grimes at qwest.com>, "'arin-tech-discuss at arin.net'"
>>   <arin-tech-discuss at arin.net>
>> Cc: "Ravibalan Pillai, Mithun" <Mithun.RavibalanPillai at qwest.com>
>> Subject: Re: [arin-tech-discuss] arin-tech-discuss Digest, Vol 7,
>>   Issue 3
>> Message-ID:
>>   <6369CD337F4CEE47A9FE64D907B2DBAF19E6BB272A at qtdenexmbm20.AD.QINTRA.COM>
>> 
>> Content-Type: text/plain; charset="iso-8859-1"
>> 
>> Ron,
>>       That is cool. I modify my research code. It does return an error xml after throw me an exception 400. I closed the connection right after I got an exception. The error xml is like this
>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?><error xmlns="http://www.arin.net/regrws/core/v1"><additionalInfo/><code>E_BAD_REQUEST</code><components><component><message>Please specify only one, either orgHandle or customerHandle.</message><name>customerHandle/orgHandle</name></component></components><message>This method requires certain parameters.  Please see the documentation for details.</message></error>
>> 
>> Tim, thanks for your info. Very, very helpful.
>> 
>> 
>> Thanks,
>> 
>> Sean Zhao
>> Sean.Zhao at CenturyLink.com
>> 
>> 
>> -----Original Message-----
>> From: Tim Christensen [mailto:timc at arin.net]
>> Sent: Thursday, June 09, 2011 6:53 PM
>> To: Grimes, Ronald; 'arin-tech-discuss at arin.net'
>> Cc: Zhao, Sean; Ravibalan Pillai, Mithun
>> Subject: Re: arin-tech-discuss Digest, Vol 7, Issue 3
>> 
>> Hello Ron,
>> 
>> On 6/9/11 4:28 PM, "Grimes, Ronald" <Ron.Grimes at qwest.com> said:
>> 
>>> Hi Tim,
>>> 
>>> Could you please look at the below.  We do not seem to be receiving the
>>> "Codes" for errors below?  Could you help us out with this concern?
>>> 
>> 
>>> I sent an xml with an empty <orgHandle>
>>> I got an exception instead of error message. Here is the xml I sent
>>> 
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <net xmlns="http://www.arin.net/regrws/core/v1">
>>>       <version>4</version>
>>>       <orgHandle></orgHandle>
>>>       <parentNetHandle>NET-208-44-0-0-1</parentNetHandle>
>>>       <netName>Q0609-208-44-99-48</netName>
>>>       <netBlocks>
>>>               <netBlock xmlns="">
>>>                       <type>S</type>
>>>                       <startAddress>208.44.99.48</startAddress>
>>>                       <cidrLength>29</cidrLength>
>>>               </netBlock>
>>>       </netBlocks>
>>> <originASes>
>>>       <originAS xmlns="">209</originAS>
>>> </originASes>
>>> </net>
>>> 
>>> But instead of getting an xml error message, I got this, "Server returned HTTP
>>> response code: 400 for URL:
>>> https://www.arin.net/rest/net/NET-208-44-0-0-1/reassign?apikey=MyAPIKey"
>> 
>> Along with this HTTP 400 response, you would have received an Error Payload
>> in the body of the response. (I just ran your transaction, and got the Error
>> Payload below).  It is possible that the client you are using may not be
>> providing these Error Payloads if the HTTP response is not in the 200 group;
>> if that is so, you will need to use a REST client that properly provides
>> Error Payloads on all HTTP responses.  Check the BODY to see if it was
>> returned.
>> 
>> This Error Payload would have contained the following content:
>> 
>> <error xmlns="http://www.arin.net/regrws/core/v1">
>>   <additionalInfo>
>>       <message>element "netBlock" not allowed in this context</message>
>>       <message>element "originAS" not allowed in this context</message>
>>   </additionalInfo>
>>   <code>E_SCHEMA_VALIDATION</code>
>>   <components/>
>>   <message>The XML payload did not validate against the defined
>>       schema. Please see the documentation for details.</message>
>> </error>
>> 
>> Note that the error indicates that the XML payload you sent did not validate
>> against the schema definition, and refers you to the documentation.
>> 
>> In examining this particular issue, refer to the Methods document, page 10
>> and following regarding the "Reassign" method (specifically, the Detailed
>> Reassignment), which indicate that the orgHandle is required, and other
>> rules applicable to a Detailed Reassignment (middle of page 11).
>> 
>> As an aside, the reason that the message does not come back with "orgHandle
>> is not provided" or something like that, is because many different things
>> (different methods, containing different payload elements) are serviced by
>> any given XML schema.  The software is making its best guess at what might
>> be wrong in the "additionalInfo" collection (e.g., netBlock and originAS not
>> allowed), under the assumption that what you provided was accurate. In this
>> case, though, following the referral to the documentation and ensuring
>> conformance to the Methods, Payloads, and XML Schemas is your best bet
>> (which is what Sean did next, by providing the required orgHandle.)
>> Continuing...
>> 
>>> 
>>> Second time I sent an xml with orgHandle,
>>> 
>>> <?xml version="1.0" encoding="UTF-8"?>
>>> <net xmlns="http://www.arin.net/regrws/core/v1">
>>>       <version>4</version>
>>>       <orgHandle>BNO</orgHandle>
>>>       <parentNetHandle>NET-63-144-0-0-1</parentNetHandle>
>>>       <netName>Q0609-63-146-48-0</netName>
>>>       <netBlocks>
>>>               <netBlock xmlns="">
>>>                       <type>S</type>
>>>                       <startAddress>63.146.48.0</startAddress>
>>>                       <cidrLength>29</cidrLength>
>>>               </netBlock>
>>>       </netBlocks>
>>>       <originASes>
>>>               <originAS xmlns="">209</originAS>
>>>       </originASes>
>>> </net>
>>> 
>>> I got a good an xml returned, like following,
>>> <?xml version="1.0" encoding="UTF-8" standalone="yes"?>
>>> <ticketedRequest xmlns="http://www.arin.net/regrws/core/v1">
>>>       <net>
>>>               <pocLinks/>
>>>               <netBlocks>
>>>                       <netBlock>
>>>                               <cidrLength>29</cidrLength>
>>>                               <description>Reassigned</description>
>>>                               <endAddress>063.146.048.007</endAddress>
>>>                               <startAddress>063.146.048.000</startAddress>
>>>                               <type>S</type>
>>>                       </netBlock>
>>>               </netBlocks>
>>>               <handle>NET-63-146-48-0-1</handle>
>>>               <netName>Q0609-63-146-48-0</netName>
>>>               <orgHandle>BNO</orgHandle>
>>>               <originASes>
>>>                       <originAS>AS209</originAS>
>>>               </originASes>
>>>               <parentNetHandle>NET-63-144-0-0-1</parentNetHandle>
>>> 
>>> <registrationDate>2011-06-09T16:11:13.059-04:00</registrationDate>
>>>               <version>4</version>
>>>       </net>
>>> </ticketedRequest>
>> 
>> This indicates that your client IS returning payloads when the HTTP status
>> is in the 200 group.  As I mentioned earlier, your client may not be
>> supporting payloads in the body when the HTTP status is in the 400 or 500
>> class (client error, server error). You'll have to use one that properly
>> supports response bodies under all HTTP status codes.
>> 
>> For testing one-off REST submissions, you may want to consider using a
>> client that is known to provide the proper responses.  Among those that we
>> use internally at ARIN are RESTClient from WizTools and the Simple Rest
>> Client for Chrome.
>> 
>> Best regards,
>> Tim Christensen
>> ARIN Engineering
>> 
>> 
>> This communication is the property of Qwest and may contain confidential or
>> privileged information. Unauthorized use of this communication is strictly
>> prohibited and may be unlawful.  If you have received this communication
>> in error, please immediately notify the sender by reply e-mail and destroy
>> all copies of the communication and any attachments.
>> 
>> 
>> ------------------------------
>> 
>> _______________________________________________
>> arin-tech-discuss mailing list
>> arin-tech-discuss at arin.net
>> http://lists.arin.net/mailman/listinfo/arin-tech-discuss
>> 
>> 
>> End of arin-tech-discuss Digest, Vol 7, Issue 5
>> ***********************************************
> _______________________________________________
> arin-tech-discuss mailing list
> arin-tech-discuss at arin.net
> http://lists.arin.net/mailman/listinfo/arin-tech-discuss




More information about the arin-tech-discuss mailing list