• (cs)

    That IP address seems to belong to the HR consulting firm Mercer. I can understand why it might not be a popular destination.

  • (cs)

    Of course. Most people at an airport just want to go to 127.0.0.1.

  • (cs)

    $nmap 168.168.2.40

    Starting Nmap 4.20 ( http://insecure.org ) at 2008-04-03 14:18 CEST Note: Host seems down.

  • sweavo (unregistered) in reply to BlueKnot
    BlueKnot:
    Of course. Most people at an airport just want to go to 127.0.0.1.

    Well played, sir! (cricket applause)

  • (cs)

    I think I see the WTF: they used a PCIe card for just one serial port. Overkill. Just use a USB-to-serial adapter.

  • Mike Dimmick (unregistered)

    Yep, looks like yet another person getting the Class C private networks wrong.

    (192.168.0.0 - 192.168.255.255 with, by convention, a 255.255.255.0 subnet mask; 256 Class C networks.)

  • (cs)

    Clearly the person searching didn't realize that PCIe also stands for "Portable Chin Integrated Exfoliation." It's IEEE 22433x.b12.3

  • dave (unregistered) in reply to BlueKnot
    BlueKnot:
    Of course. Most people at an airport just want to go to 127.0.0.1.

    like i always say, localhost is where the heart is!

  • (cs)

    I have been to 168.168.2.40 It is, in fact, boring and vacant.

  • (cs) in reply to dave

    I am localhostless, you insensitive clod!

  • Sionnach (unregistered) in reply to BlueKnot
    BlueKnot:
    Of course. Most people at an airport just want to go to 127.0.0.1.

    Hehe excellent! :-)

  • (cs)

    "Reset" or "Fatal" are the choices?

    An error like that could really cripple a system...

    captcha: even if you smiled but didn't want to, you are a bad, bad person

  • Tones (unregistered)

    So people screw up error handling in apps written in LabView as much as in any other environment... How unsurprising...

  • dkf (unregistered)

    ERROR! Comment failed for the following reason: The reason is not clear.

  • (cs)

    So what's wrong with that? It's just another way of saying you ran out of pause time 42m43s ago?

  • s. (unregistered) in reply to brazzy

    Get yourself a e-tent: grab a RJ45 plug and wire pins 1 to 3 and 2 to 6, now wherever you plug it in, it's just like 127.0.0.1

  • (cs)

    The comment is not clear

  • Sam (unregistered)

    You have an unhandled error. Do you want to reset, or kill this kid in a wheelchair?

  • (cs)

    I showed this to a coworker who recalled another funny incident:

    They setup a videoconference for a group of ppl (across different countries), and sent them the IP address to connect to. One of them replied and asked if he needed to add the country code :)

  • Ryan (unregistered)

    I tried to sail a boat to 168.168.2.40 once, but all the ports I found were closed.

  • (cs)

    Haha, the first error is from Labview... N00bs!!!

  • (cs)

    If you fly to 127.0.0.1, is your flight attendant a localhostess?

  • (cs)

    Ok hands up, Who typed 168.168.2.40 into their browser?

  • (cs)

    Wow. Labview on a "fitness" machine.

    I think we've got a potential Feature Article WTF, here... can anyone get the story behind it?

  • (cs) in reply to Sam
    Sam:
    You have an unhandled error. Do you want to reset, or kill this kid in a wheelchair?

    Hmm... I wasn't going to bring it up... but I was wondering who would want to "measure up" against the kid anyway. I mean, doesn't he kind of seem like a first level boss? The kind that is tricky when you first play, but you know he's ultimately going to sit there and let you wail on him? Your first inclination would be to put it in extra hard mode, but you've never played before so he would run circles around you. All the kids around would point and laugh. Then you'd get that crazy look in your eye and start uppercutting all the 8 year olds within reach.

    I've never been to Ann Arbor, but I'm sure I'm not allowed.

    http://en.wikipedia.org/wiki/Ann_Arbor_Hands-On_Museum

    That does sound like a fun place to go to, though... dang.

    Addendum (2008-04-03 10:15): sigh Wale. Not wail. To mark with stripes... not lament. Okay... I'm not very good at "fitness" games.

  • Err (unregistered) in reply to brazzy

    WTF ?

    CAPTCHA: nibh

  • Err (unregistered)

    CAPTCHA: abbas

  • Anonymous (unregistered)

    The CAPTCHA is not clear.

  • test (unregistered) in reply to Anonymous
    Anonymous:
    The CAPTCHA is not clear.

    Yes, my CAPTCHA is not "clear", it is "unclear".

  • daniel c w (unregistered) in reply to Mrrix32
    Ok hands up, Who typed 168.168.2.40 into their browser?

    I copy and pasted it, sir.

  • Kuba (unregistered) in reply to North Bus
    North Bus:
    Wow. Labview on a "fitness" machine.

    I think we've got a potential Feature Article WTF, here... can anyone get the story behind it?

    It's understandable - they had some data processing going on (probably some DAQ board to control things). Although IMHO one of the main problems with LabView is that you really write using C primitives via a graphical interface. It's not very efficient that way, from a programmer's perspective. C is a pretty low-level thing, putting a graphical editor in front of those primitives doesn't make it so much better.

    Writing, say a Qt application accessing various DAQ functions via LabView-looking wrappers is way faster for me - heck, doing extensive changes is way faster too.

    Cheers!

  • Gunnar (unregistered) in reply to BlueKnot

    Unless, of course, you have a multihomed host behind 127.0.0.1. But i'm not sure if that's RFC-legal.

  • (cs) in reply to Mike Dimmick
    Mike Dimmick:
    Yep, looks like yet another person getting the Class C private networks wrong.

    (192.168.0.0 - 192.168.255.255 with, by convention, a 255.255.255.0 subnet mask; 256 Class C networks.)

    If the mask was /16, it could be valid for a huge range. They could also just mask down to /24 and put the router in the subnet with success. Check out http://en.wikipedia.org/wiki/Classful_network

    1. Network class terminology and allocation was dropped in 93 (that far back? wow).
    2. Private ranges: 10.0.0.0 - 10.255.255.255 (/8 (bit) mask) 172.16.0.0 - 172.31.255.255 (/16) 192.168.0.0 - 192.168.255.255 (ALSO /16 mask optionally masked to /24)

    Seriously, why would anyone in business bother with anything less than 10.../whatever suits you? Saves headaches later.

    I'm looking forward to the user-simplified IPv6 with bigger payloads -- which means we won't see it for another 10 years.

  • My Name (unregistered) in reply to Pecos Bill
    172.16.0.0 - 172.31.255.255 (/16)

    It's a /12, not /16.

  • (cs)

    168.168.2.40: Nice to see that they have unqualified idiots in IT over in Taipei as well.

  • sf (unregistered) in reply to operagost
    operagost:
    168.168.2.40: Nice to see that they have unqualified idiots in IT over in Taipei as well.
    那是苛刻的
  • (cs) in reply to Pecos Bill
    Pecos Bill:

    I'm looking forward to the user-simplified IPv6 with bigger payloads -- which means we won't see it for another 10 years.

    One of my college reports was on IPv6. "IPv6 would allow for 340 undecillion IP addresses... that's enough IPs for every proton on earth! Heeyuck!" (That's not true, by the way.) My how times don't change.

    Anyway, that was like 8 years ago. Do you think the conversion will ever completely happen?

  • Request timed out (unregistered)

    Pinging 168.168.2.40 with 32 bytes of data:

    Request timed out.

    As for that other person, you mean localhostess, not localhostless. But it's good that you're trying to avoid sexist language.

  • (cs) in reply to Sam
    Sam:
    You have an unhandled error. Do you want to reset, or kill this kid in a wheelchair?
    both
  • JB (unregistered)

    I see that coach Beilein has been moonlighting as a programmer.

  • (cs) in reply to Mike Dimmick
    Mike Dimmick:
    Yep, looks like yet another person getting the Class C private networks wrong.

    Perhaps they are using internet accessible displays... Or maybe it's showing the IP address of the hosts internet connection.

    Though since the range is owned by an HR company, it's more likely to be an idiot that can't remember 192.168.

  • Balony (unregistered) in reply to Pecos Bill
    Pecos Bill:
    Mike Dimmick:
    Yep, looks like yet another person getting the Class C private networks wrong.

    (192.168.0.0 - 192.168.255.255 with, by convention, a 255.255.255.0 subnet mask; 256 Class C networks.)

    If the mask was /16, it could be valid for a huge range. They could also just mask down to /24 and put the router in the subnet with success. Check out http://en.wikipedia.org/wiki/Classful_network

    1. Network class terminology and allocation was dropped in 93 (that far back? wow).
    2. Private ranges: 10.0.0.0 - 10.255.255.255 (/8 (bit) mask) 172.16.0.0 - 172.31.255.255 (/16) 192.168.0.0 - 192.168.255.255 (ALSO /16 mask optionally masked to /24)

    Seriously, why would anyone in business bother with anything less than 10.../whatever suits you? Saves headaches later.

    I'm looking forward to the user-simplified IPv6 with bigger payloads -- which means we won't see it for another 10 years.

    We'll need IPv6 so we can travel to the moon.

  • (cs) in reply to Mrrix32
    Mrrix32:
    Ok hands up, Who typed 168.168.2.40 into their browser?

    Well, I pinged it. But I do have a lot of computers on the 192.168.2.0/24 network... I think some are in the 30's.

    I'll have to put .40 on the new test server, being transient and all.

  • (cs) in reply to Pecos Bill
    Pecos Bill:
    Seriously, why would anyone in business bother with anything less than 10.../whatever suits you? Saves headaches later.
    You never had to set up VPN between two private networks, right?
  • 168 is a lucky number (unregistered)

    It sounds like "endless fortune" in Chinese language.

    IMHO, the destination boards don't need internets. They could even have DIP switches for IP addresses.

  • dignissim (unregistered)

    I bet the sign's tubes were clogged by all these people sending useless internets to each other. This is the reason why we need tiered internet trafic! All the tubes are backed up with the useless crap like the 100000's of "guy gets hit in balls" videos on youtube!

  • Jay (unregistered) in reply to Ryan
    Ryan:
    I tried to sail a boat to 168.168.2.40 once, but all the ports I found were closed.

    serial port: (n) place where they unload corn flakes from ships

  • pwa (unregistered) in reply to BlueKnot

    hehe

  • Hairy (unregistered) in reply to Mike Dimmick

    254 addresses.

  • Cellar (unregistered) in reply to Mike Dimmick

    Ha! Another developer with a really long beard. We've been off classes and on CIDR for quite a while now.

    More disturbing is that 168.168/16 is not a private network. It's public and registered to some HR outfit in KY, US. So, someone just picked a network outta their asses and went with it. Many people do (the asses that took'' 5/8 for their global vpn solution thingie do it publicly and claim it's alright because the block wasIANA - Reserved'' -- it might not be for much longer, ha ha) but that doesn't make it right.

    Read RFC1918 to see what ranges they should've been using.

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