• amandahugginkis (unregistered) in reply to Cellar

    You do all know that you can use any range you feel like, you just need to route appropriately. The 10, 172, and 192 addresses that everyone knows and loves are reserved for private networks, but you don't have to use them.

    Mate of mine read an article that says it's better for corps to pick a random address range instead of one of the reserved ones - when corps merge, it makes the IT headaches a lot easier as it's much less likely to cause IP conflicts. And there's no real disadvantage to using a non-reserved range as long as you account for it in your routing.

  • (cs) in reply to Cellar
    Cellar:
    More disturbing is that 168.168/16 is not a private network. [...] Read RFC1918 to see what ranges they should've been using.

    I'd say it was a typo and they meant to use 192.168.2.40, which is why it is showing the IP as a "I can't connect to the host which tells me what to display".

    Edit: It took me a couple of looks to see that it was 168.168. instead of the 192.168 that I thought it was. It is Monday evening and I did go to Supanova on the weekend...

  • Salvador G. Jr. (unregistered)

    The real WTF is that the fitness machine has a handicapped person in the corner. Shouldn't it have someone working out o something?

  • (cs) in reply to My Name
    My Name:
    172.16.0.0 - 172.31.255.255 (/16)

    It's a /12, not /16.

    No, it's sixteen /16's.

  • NickNameNick (unregistered) in reply to amandahugginkis
    Mate of mine read an article that says it's better for corps to pick a random address range instead of one of the reserved ones - when corps merge, it makes the IT headaches a lot easier as it's much less likely to cause IP conflicts. And there's no real disadvantage to using a non-reserved range as long as you account for it in your routing.

    That's stupid, Public IP addresses need to be globally unique, no amount of clever routing rules or nat translation can save you from the fact that there is no way for the router to know that you want 168.168.0.40 the web-server on the far side of the planet, and not 168.168.0.40 the computer on your local network that has co-opted its name.

  • (cs) in reply to Mrrix32
    Mrrix32:
    Ok hands up, Who typed 168.168.2.40 into their browser?
    I did a whois lookup with the Network tool in Ubuntu and got the following results:

    OrgName: william M. Mercer OrgID: WMM-1 Address: 462 S. Fourth Avenue, Suite 1500 City: Louisville StateProv: KY PostalCode: 40202 Country: US

    NetRange: 168.168.0.0 - 168.168.255.255 CIDR: 168.168.0.0/16 NetName: MERCERNET NetHandle: NET-168-168-0-0-1 Parent: NET-168-0-0-0-0 NetType: Direct Assignment NameServer: AUTH01.US.WMMERCER.COM NameServer: AUTH02.NS.UU.NET Comment:
    RegDate: 1994-09-28 Updated: 2001-09-04

    RTechHandle: IW34-ARIN RTechName: William M. Mercer, Incorporated RTechPhone: +1-502-561-4500 RTechEmail: [email protected]

    ARIN WHOIS database, last updated 2008-04-07 19:10

    Enter ? for additional hints on searching ARIN's WHOIS database.

    Also, Traceroute ended with the IP address 12.118.144.30 .

  • Paul (unregistered)

    I led displays in that last picture and I can tell you one of two things about that picture: 1. The person taking the picture caught the display at the right time while it was booting up. 2. The display was stuck in boot mode.

  • Doug (dx9s) (unregistered)

    so THAT'S how IP packets are routed!?! Thing brings up a WHOLE new meaning to the terms "net lag" !!!

Leave a comment on “168.168.2.40 Now Boarding”

Log In or post as a guest

Replying to comment #:

Log Out

« Return to Article