BBC News is carrying the story of a massive protest in downtown London. Thousands, perhaps as many as 100,000 people, descended on Westminster and 10 Downing Street. According to what I've been seeing and reading, the vast majority sided with Hezbollah. All were screaming for an end to the fighting, and most made it sound as if this were all Israel's fault. One can find fault with many things that Israel does, but, folks, this ain't one of 'em.
Remember, Israel left Lebanon. They pulled out of Lebanon. First Hamas then Hezbollah conducted raids into Israel, killing several soldiers and taking a total of three hostage. Both Hamas and Hezbollah rant and rave about how Israel is killing Lebanese. Er, um, yeah, they are. Only because they are firing back at the people firing at them. And the people firing at them, whether Hamas, Hezbollah, or Walter-the-paper-hanger, are using the Lebanese as human shields. The Hezbollah / Hamas / whatever want as many casualties as possible. The more, the merrier. Don't know if this has to do with they want as many people as possible to find their 72 virgins (or strum their golden harp because, according to the press, many casualties are Christians). What I do know is that, the more innocent people in Lebanon die, the better for Hamas.
But the story doesn't stop there. Israel very quickly began circulating the story that Iran was behind this. At first, to me, the unitiated, that seemed plausible, but strange. I thought Israel might be trying to shun responsibility. Now, it not only seems plausible or possible, it seems probable. As the Marines say, let me break it down shotgun style.
First, Iran re-started their nuclear program. The world is concerned because Iran now wants the bomb. You don't believe that? Consider this item: Iranian's President , when speaking about the United States, said,
"How do you justify this logic of having a full arsenal of nuclear weapons, but when it comes to nations such as ours, you do not even allow research?"
Ah, so now he's no longer saying that the nuclear program is for peaceful purposes, it's for research. Ahhhh! I see. Research for... what? Frankly, you have an elected President stating outright that he wishes for the demise of another country. That country, of course, is Israel.
Second, just when the European community and the US are about to come breathing down Iran's neck over its nuclear "research" program, Hamas and Hezbollah attack Israel. Coincidence? Perhaps. But I find it interesting that they attack almost the exact same day that the Western World gathered to discuss what to do with Iran.
Third, there are now protests in downtown Baghdad against the US, against Israel, and in support of Hezbollah.
It's a triple whammy.
Yet, that's not enough. Now the milquetoast liberals come out of the woodwork in London to rally against Israel and "for" the people of Lebanon. "Ceasefire now", many placards say. "Stop the fighting!", they scream. Except the "they" the protesters want to stop are the Israelis. The Hezbollah can kill as many as they want.
Saturday, August 05, 2006
Sunday, June 04, 2006
Getting to the Internet through Comcast
Do you have a Comcast high-speed connection to the Internet? If so, are you having difficulties getting to the Internet? (Obviously, if you are, you're not on the computer from which you're having the difficulty. Either that, or you went through a particular connection and you went back to the old connection.)
Here's the typical scenario: You were connected using a particular computer, but you decided to add another system. So, you popped over to Best Buy and bought a router, such as are sold by Linksys or D-Link. Now, you can't get anywhere.
Here's why. First, some background. Every single ethernet connection is required to have a MAC (MAC = media access control) address. The MAC address, typically just called "the MAC", is essentially a serial number for each device. It uniquely defines that particular device. For example, you most likely have an Ethernet connection on your computer. It could either be a NIC (network interface connection) card or a connection that is direct on your motherboard. Either way, this connection has its own MAC address. If you are using a NIC card, such as made by D-Link or any of the others, it will have a MAC address. You can have two of the exact same make & model NIC cards, but they will each have a different MAC address. As I said, each device will have its own, unique MAC address.
The same goes for routers, wireless access points, on and on and on. Each will have its own MAC address.
What does this have to do with you not being able to connect to the Internet through Comcast? Simple. Let's say that your old connection was a PC connected directly to your cable modem. What happened was this: Comcast registered your connecting by using the MAC address of your computer. It's a form of security. If someone else tried to take over your connection, they wouldn't know your MAC address. (Yes, for those technical people out there, it's possible to spoof it. But that requires more work. Hackers tend to be, among other things, lazy.) Remember I said that every device has a different MAC address? Well, when you got that shiny, new router, it also had a MAC address. And it was different than that of your computer. When you plugged it into the cable modem, Comcast did not recognize that new MAC address. Therefore, it essentially locked you out. No Internet for you! (Note: That last sentence was said in the same voice as the "Soup Nazi" from "Seinfeld".)
But fear not! There is hope. You have two options. The first is to clone the MAC address of your old connection to your new router. The other option is to get Comcast to recognize the MAC address of your new router (or whatever new thing is connecting to the cable modem.)
To go with Option #1, use whatever method is necessary to configure your router (or whatever) and look for an option to clone the MAC address. On my Linksys router, for example, I open my Internet browser, open the web-based configuration page (by typing "http://192.168.1.1" into the address bar), then enter the administrator password. From the main "Setup" page, there's an option called "MAC Address Clone". On that page, I select "Enable" next to "MAC Clone Service". At that point, the "Clone" button is no longer greyed out. I press that button and it clones the MAC address of my computer. (NOTE: I don't know how it knows which MAC address to clone if there are multiple items connected to the router. It could be that it simply clones the MAC address of whatever computer is being used to set the configuration settings. Again, I don't know this for sure.) Finally, click the button at the bottom that says, "Save Settings".
From there, you should be able to connect to the Internet.
Option #2 is to simply disconnect your cable modem from the cable connection. You will need to leave it down for at least 12 hours. (Note: I've not tried this. I'm simply quoting what some others have reported.) At that time, Comcast will release your IP address. When you connect back to the Internet, it will allow you to re-register with a new MAC address.
Best of luck to you!
Gajimmy
Here's the typical scenario: You were connected using a particular computer, but you decided to add another system. So, you popped over to Best Buy and bought a router, such as are sold by Linksys or D-Link. Now, you can't get anywhere.
Here's why. First, some background. Every single ethernet connection is required to have a MAC (MAC = media access control) address. The MAC address, typically just called "the MAC", is essentially a serial number for each device. It uniquely defines that particular device. For example, you most likely have an Ethernet connection on your computer. It could either be a NIC (network interface connection) card or a connection that is direct on your motherboard. Either way, this connection has its own MAC address. If you are using a NIC card, such as made by D-Link or any of the others, it will have a MAC address. You can have two of the exact same make & model NIC cards, but they will each have a different MAC address. As I said, each device will have its own, unique MAC address.
The same goes for routers, wireless access points, on and on and on. Each will have its own MAC address.
What does this have to do with you not being able to connect to the Internet through Comcast? Simple. Let's say that your old connection was a PC connected directly to your cable modem. What happened was this: Comcast registered your connecting by using the MAC address of your computer. It's a form of security. If someone else tried to take over your connection, they wouldn't know your MAC address. (Yes, for those technical people out there, it's possible to spoof it. But that requires more work. Hackers tend to be, among other things, lazy.) Remember I said that every device has a different MAC address? Well, when you got that shiny, new router, it also had a MAC address. And it was different than that of your computer. When you plugged it into the cable modem, Comcast did not recognize that new MAC address. Therefore, it essentially locked you out. No Internet for you! (Note: That last sentence was said in the same voice as the "Soup Nazi" from "Seinfeld".)
But fear not! There is hope. You have two options. The first is to clone the MAC address of your old connection to your new router. The other option is to get Comcast to recognize the MAC address of your new router (or whatever new thing is connecting to the cable modem.)
To go with Option #1, use whatever method is necessary to configure your router (or whatever) and look for an option to clone the MAC address. On my Linksys router, for example, I open my Internet browser, open the web-based configuration page (by typing "http://192.168.1.1" into the address bar), then enter the administrator password. From the main "Setup" page, there's an option called "MAC Address Clone". On that page, I select "Enable" next to "MAC Clone Service". At that point, the "Clone" button is no longer greyed out. I press that button and it clones the MAC address of my computer. (NOTE: I don't know how it knows which MAC address to clone if there are multiple items connected to the router. It could be that it simply clones the MAC address of whatever computer is being used to set the configuration settings. Again, I don't know this for sure.) Finally, click the button at the bottom that says, "Save Settings".
From there, you should be able to connect to the Internet.
Option #2 is to simply disconnect your cable modem from the cable connection. You will need to leave it down for at least 12 hours. (Note: I've not tried this. I'm simply quoting what some others have reported.) At that time, Comcast will release your IP address. When you connect back to the Internet, it will allow you to re-register with a new MAC address.
Best of luck to you!
Gajimmy
Sunday, May 14, 2006
Dixie Chicks: The Victims of Intolerance?
The poor Dixie Chicks. Hard to not feel sorry for them. After their slamming the President and the war in Iraq, the Dixie Chicks tucked their tails between their legs and headed home. They were threatened, yelled at, had every epithet in the world thrown at them. All for merely speaking their mind. They told a London audience that they were ashamed that President Bush came from their home state of Texas.
After that, they were slammed in public and even threatened in private.
Now they are back on tour with a new album. It includes a new song, "Not Ready to Make Nice". This is a song they claim has to do with how they feel about the whole episode. After that incident, they put out some apologies, but no one seemed interested. Their reaction was, "We're being muzzled. We should be allowed to speak our minds."
Yup, that's absolutely right. But when other people, you know, us common folk, express our minds, don't act surprised. What were you expecting? Okay, here's another question: Why didn't you say this in Texas? Why did you have to fly 3600+ miles away from your "home" in Texas to speak your mind?
I know, I know, you were so muzzled in Texas. They're nothing but a bunch of hicks. Such simpletons. Only the English would understand.
Mind you, I don't like the guy who threatened you. I think that idiot should be put in a nice, 6 x 9 cell with his roommate, Rufus T. Buttlove.
But those people who merely expressed anger and outrage at your antics and expressed it by NOT buying your albums, calling the local radio stations to request that they NOT play your music, well, you had that one coming.
After that, they were slammed in public and even threatened in private.
Now they are back on tour with a new album. It includes a new song, "Not Ready to Make Nice". This is a song they claim has to do with how they feel about the whole episode. After that incident, they put out some apologies, but no one seemed interested. Their reaction was, "We're being muzzled. We should be allowed to speak our minds."
Yup, that's absolutely right. But when other people, you know, us common folk, express our minds, don't act surprised. What were you expecting? Okay, here's another question: Why didn't you say this in Texas? Why did you have to fly 3600+ miles away from your "home" in Texas to speak your mind?
I know, I know, you were so muzzled in Texas. They're nothing but a bunch of hicks. Such simpletons. Only the English would understand.
Mind you, I don't like the guy who threatened you. I think that idiot should be put in a nice, 6 x 9 cell with his roommate, Rufus T. Buttlove.
But those people who merely expressed anger and outrage at your antics and expressed it by NOT buying your albums, calling the local radio stations to request that they NOT play your music, well, you had that one coming.
Thursday, April 13, 2006
How Microsoft Hijacked the Internet
Remember when the Internet was first born? Remember how anyone with a simple command of HTML could post their own web page? And, so long as your browser supported the HTML *standard*, you could read that web page?
Obviously, that did not make Microsoft happy. Was it Netscape pushing Microsoft back into the corner & out of the limelight that did it? Who knows? What I can say is that they not only came back and pushed Netscape off of the map (Netscape who?), but they also took over the Internet. How many times have you gone to someone's web site and seen those dreaded words, "This site REQUIRES (my emphasis added) Internet Explorer Ver X or higher". What happened to the HTML standard? Did it die? Pull a MacArthur ("just faded away" for those of you who are a little short on history)?
Again, no. Microsoft said, "Hey, let's not only destroy Netscape, let's take over the Internet, too! HTML? BAH! We don't need no stinkin' HTML! We're MICROSOFT!"
So it goes. Obviously Microsoft was not content to merely suck the life blood from a competitor. Who would be?
Now I'm stuck occasionally having to use Internet Exploder, despite my wish to use Mozilla's Firefox whenever I can. I can say that I've noted several attempts (looking at firewall logs) of outside entities trying to get through to my computer. I've also noted that they line up perfectly for when I'm using IE as opposed to Firefox.
IE = lots of attempts
Firefox = all's quiet on the binary front.
Sigh.
Obviously, that did not make Microsoft happy. Was it Netscape pushing Microsoft back into the corner & out of the limelight that did it? Who knows? What I can say is that they not only came back and pushed Netscape off of the map (Netscape who?), but they also took over the Internet. How many times have you gone to someone's web site and seen those dreaded words, "This site REQUIRES (my emphasis added) Internet Explorer Ver X or higher". What happened to the HTML standard? Did it die? Pull a MacArthur ("just faded away" for those of you who are a little short on history)?
Again, no. Microsoft said, "Hey, let's not only destroy Netscape, let's take over the Internet, too! HTML? BAH! We don't need no stinkin' HTML! We're MICROSOFT!"
So it goes. Obviously Microsoft was not content to merely suck the life blood from a competitor. Who would be?
Now I'm stuck occasionally having to use Internet Exploder, despite my wish to use Mozilla's Firefox whenever I can. I can say that I've noted several attempts (looking at firewall logs) of outside entities trying to get through to my computer. I've also noted that they line up perfectly for when I'm using IE as opposed to Firefox.
IE = lots of attempts
Firefox = all's quiet on the binary front.
Sigh.
Thursday, January 19, 2006
Don't Bother, Bin Ladin
I see bin Ladin has raised his ugly head. He scurried out of his rathole long enough to "warn" the US of future attacks, but to also diplomatically offer a "truce" if we pull out of Iraq and Afghanistan. In other words, he wants us to return to the status quo ante.
The only problem is that we were in neither Afghanistan nor Iraq on 11 September 2001.
Enough said.
What else you got to sell, idiot.
The only problem is that we were in neither Afghanistan nor Iraq on 11 September 2001.
Enough said.
What else you got to sell, idiot.
Monday, January 02, 2006
The NSLU2: One, Big Linksys Bug Report
I purchased a Linksys NSLU2 Network File Server some time back. I recently upgraded the firmware to the latest version (called 2.3R63). Some time after that, I noticed that the hard drive (a Maxtor OneTouch 120 GB USB 2.0 hard drive) was being accessed every 2 - 3 seconds. At first, I thought my NSLU2 had been hacked. I have several firewalls, all of which are logged. I checked them all and found nothing. Still, I loaded an old computer with Linux then ran Ethereal in promiscuous mode. Again, nothing. The only thing from the server was a standard broadcast letting the network know every now and then that it was there and alive.
So began my journey. Rather than walking step-by-step, let me summarize what I discovered:
* The problem of the disk being accessed constantly (every 2 - 3 seconds) is in the latest firmware (2.3R63). No matter what I tried, it always had that problem. I tried different format types (NTFS, FAT32, and the original EXT3). The only thing that worked was reverting to a previous firmware version (2.3R29).
* After reverting to the previous firmware version (2.3R29), I noticed that I could read and write much quicker.
* Resetting the box is not as easy as it sounds. I tried resetting the box, but found that some settings (the server name, DNS addresses, gateway address, e-mail address) always stayed. It took me a while to figure out how to actually ERASE EVERYTHING. I discovered one method to do a partial reset (Method #1 below) two methods to reset everything (#2 & #3 below):
- Method #1: Using the tip of a paper clip, push in the reset button for about 3 seconds and let go. The box should beep. Then push in the button until it beeps again (should take about 10 seconds). This resets the IP address to 192.168.1.77. The second time resets the password. Note that neither of these does anything with such settings as the DNS, gateway, or the e-mail address.
- Method #2: From the home page of the web interface, go to "Administration" followed by the "System" page. At the bottom of the page is a button called, "Restore Default Config". Hit this button and wait! It will take about two minutes for it to completely reset. At that time, all of the memory should have been dumped. Any accounts you set up should be gone as should all of the other settings.
- Method #3: Use a program downloaded from Linksys called "EraseAll". I downloaded it from Linksys in a file called "EraseAll.zip". It was a zipped (meaning "compressed") file. Inside was a program called "EraseAll (for EFG120).exe" Even though it says that it's for the EFG120 (another Linksys network server product), I tried it (out of desperation) and found that it worked. And by "worked", I mean that it completely erased the previous firmware, EVERY setting, and installed the new firmware. I also used it to go back to previous firmware versions. When I used it, it was as if I had just taken the unit right out of the box. NOTE: I used an older Windows 98 computer to use this program. I did not try it from my Windows XP box. It would probably work; I just did not attempt it.
* If you have had a hard drive connected to the NSLU2 under previous firmware versions (2.3R29 or earlier), it had to be formatted using the web interface. The format version is compatible with Linux. (As a matter of fact, I connected the hard drive directly to a computer running Fedora Core 4.0 Linux. It was able to read the hard drive, see the files, and read the filenames. However, I could not access any of them.) If you use the newest firmware (2.3R63), you will be able to format a drive using either NTFS (the NT/2000/XP) format or FAT32 (older Windows format) then connect it directly to the NSLU2.
* The Linksys NSLU2 manual says, in several places, not to disconnect a drive when the unit is powered on. Unfortunately, it does not say what the consequences are. Therefore, turn the unit off before connecting and disconnecting a drive.
* To turn the unit off, just push in the button on the front until the unit beeps. Then let go.
* When connecting a drive, turn the unit off (see above), connect the drive, turn the drive on, then turn the NSLU2 on. It will take about two minutes for everything to be ready.
Best of luck to you all!
So began my journey. Rather than walking step-by-step, let me summarize what I discovered:
* The problem of the disk being accessed constantly (every 2 - 3 seconds) is in the latest firmware (2.3R63). No matter what I tried, it always had that problem. I tried different format types (NTFS, FAT32, and the original EXT3). The only thing that worked was reverting to a previous firmware version (2.3R29).
* After reverting to the previous firmware version (2.3R29), I noticed that I could read and write much quicker.
* Resetting the box is not as easy as it sounds. I tried resetting the box, but found that some settings (the server name, DNS addresses, gateway address, e-mail address) always stayed. It took me a while to figure out how to actually ERASE EVERYTHING. I discovered one method to do a partial reset (Method #1 below) two methods to reset everything (#2 & #3 below):
- Method #1: Using the tip of a paper clip, push in the reset button for about 3 seconds and let go. The box should beep. Then push in the button until it beeps again (should take about 10 seconds). This resets the IP address to 192.168.1.77. The second time resets the password. Note that neither of these does anything with such settings as the DNS, gateway, or the e-mail address.
- Method #2: From the home page of the web interface, go to "Administration" followed by the "System" page. At the bottom of the page is a button called, "Restore Default Config". Hit this button and wait! It will take about two minutes for it to completely reset. At that time, all of the memory should have been dumped. Any accounts you set up should be gone as should all of the other settings.
- Method #3: Use a program downloaded from Linksys called "EraseAll". I downloaded it from Linksys in a file called "EraseAll.zip". It was a zipped (meaning "compressed") file. Inside was a program called "EraseAll (for EFG120).exe" Even though it says that it's for the EFG120 (another Linksys network server product), I tried it (out of desperation) and found that it worked. And by "worked", I mean that it completely erased the previous firmware, EVERY setting, and installed the new firmware. I also used it to go back to previous firmware versions. When I used it, it was as if I had just taken the unit right out of the box. NOTE: I used an older Windows 98 computer to use this program. I did not try it from my Windows XP box. It would probably work; I just did not attempt it.
* If you have had a hard drive connected to the NSLU2 under previous firmware versions (2.3R29 or earlier), it had to be formatted using the web interface. The format version is compatible with Linux. (As a matter of fact, I connected the hard drive directly to a computer running Fedora Core 4.0 Linux. It was able to read the hard drive, see the files, and read the filenames. However, I could not access any of them.) If you use the newest firmware (2.3R63), you will be able to format a drive using either NTFS (the NT/2000/XP) format or FAT32 (older Windows format) then connect it directly to the NSLU2.
* The Linksys NSLU2 manual says, in several places, not to disconnect a drive when the unit is powered on. Unfortunately, it does not say what the consequences are. Therefore, turn the unit off before connecting and disconnecting a drive.
* To turn the unit off, just push in the button on the front until the unit beeps. Then let go.
* When connecting a drive, turn the unit off (see above), connect the drive, turn the drive on, then turn the NSLU2 on. It will take about two minutes for everything to be ready.
Best of luck to you all!
Subscribe to:
Posts (Atom)