Thursday, August 2, 2012

An idea for mobile phone application...

It just occurred to me that it would be good (well, at least for somebody) to have application that allows caller to define music/sound that will be played on a callee mobile phone. Basically, before you press Call button, you select a melody. This allows a lot of possibilities:
  • Suppose, I'm angry and I'm calling my support administrator because something isn't working. In that case I can select some pretty loud yelling of the sentence like Answer the phone you idiot! The server isn't working again. And this can be repeated as many times as necessary.
  • Or, if you are calling a wife because you've stayed with guys until late and you know she's currently mad. In that case you can select ringing tone something like: Hi Honey! I'm thinking on you and I'm calling you to appologize. with some appropriate background music.
  • Or, if you are trying to get to some chick, you can use something like: Hey beauty, XYZ is calling you.
  • Or, if you are calling your mother in law, you can use: Hey old bat! If you didn't drop dead answer the phone!
Well, you've got the point. The possibilities are endless. :)

arpwatch: too short requests error

Today, I got a lot of errors from arpwatch (actually arpwatch-NG) that look like this:
arpwatch: short (want 42)
There is no point in googling this, even though I tried. :) There is one post that mentions some Debian bug, or something like that.

Anyway, the problem is that something on the network has a bug, or is wrongly configured, and arpwatch doesn't log sending MAC address from frames in case it receives something erroneous that is supposed to be ARP. Of course it could be discussed as to how much this information would be useful, but, it would at least give some clue who's sending this.

In the end, the only thing that could be done in this case is to sniff network and wait for the error to repeat.

Update

I figured out what was causing this errors. It was nmap that I put to regularly scan the network! :)

Wednesday, August 1, 2012

Google Chrome yum repository...

Yesterday I noticed that yum repository on Google servers with packages for Chrome doesn't work. I see this in yum output when I run update process:
google-chrome                                            |  951 B     00:00 !!!
Note that three exclamation marks at the end! Also, once I received one  other error message, but I didnt' write it down, so I don't remember exactly what it was. Anyway, checking manually URL of the repository shows that it is not available:
# lftp http://dl.google.com/linux/chrome/rpm/stable/x86_64
cd: Access failed: 404 Not Found (/linux/chrome/rpm/stable/x86_64)
But, it turns out that there is no linux repository at all:
# lftp http://dl.google.com/linux/
cd: Access failed: 404 Not Found (/linux)
I did some Googling and what puzzles me is that there is nothing about this change. I found several posts in the past that the repository isn't available, but that was over a year ago, and in the mean time repository was restored. Also, there are some more recent posts, but again, those were solved!

I checked my update logs and found that the last update was on July, 27th, so is it possible that the URL will be restored as it was in the past?

About Me

scientist, consultant, security specialist, networking guy, system administrator, philosopher ;)

Blog Archive