Category Archives: Administrative

Amazon.com

Very weird. I cannot access the website from this computer. It’s not a route issue, because I can get to it from her Windows machine, but on my Linux machine, it times out. Traceroute output is:

$ traceroute amazon.com
traceroute to amazon.com (176.32.98.166), 30 hops max, 60 byte packets
1 * * *
2 81.d6.9bc0.ip4.static.sl-reverse.com (192.155.214.129) 17.514 ms 17.540 ms 17.560 ms
3 ae22.dar01.sjc01.networklayer.com (50.23.118.158) 19.775 ms 17.523 ms 19.857 ms
4 ae9.bbr02.eq01.sjc02.networklayer.com (50.97.19.166) 19.543 ms 19.665 ms 19.535 ms
5 ae6.cbs02.eq01.sjc02.networklayer.com (50.97.17.78) 20.183 ms * *
6 ae0.cbs02.cs01.lax01.networklayer.com (50.97.17.86) 26.906 ms 27.243 ms 27.196 ms
7 * * *
8 * * *
9 ae2.dar01.dal13.networklayer.com (169.45.18.37) 57.537 ms 54.337 ms 55.683 ms
10 * ae16.cbs02.eq01.dal03.networklayer.com (169.45.18.90) 54.432 ms 57.155 ms
11 ae0.cbs01.tl01.atl01.networklayer.com (50.97.17.163) 82.146 ms 84.211 ms 85.019 ms
12 ae8.bbr01.tl01.atl01.networklayer.com (50.97.17.155) 72.644 ms 74.857 ms 72.502 ms
13 amazon.tieatl.telxgroup.net (198.32.132.95) 77.715 ms 74.947 ms 74.869 ms
14 * * *
15 * * *
16 * * *
17 178.236.3.31 (178.236.3.31) 88.314 ms 54.240.229.187 (54.240.229.187) 90.802 ms 54.240.229.217 (54.240.229.217) 84.928 ms
18 * * *
19 * * *
20 * * *
21 * * *
22 * * *
23 * * *
24 * * *
25 * * *
26 * * *
27 * * *
28 * * *
29 * * *
30 * * *

When I ping it, I get this:

$ ping amazon.com
PING amazon.com (176.32.103.205) 56(84) bytes of data.
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=1 ttl=233 time=79.8 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=2 ttl=233 time=80.7 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=3 ttl=233 time=79.8 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=4 ttl=233 time=82.8 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=5 ttl=233 time=79.7 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=6 ttl=233 time=78.7 ms
64 bytes from 176.32.103.205 (176.32.103.205): icmp_seq=7 ttl=233 time=79.2 ms
^C
— amazon.com ping statistics —
7 packets transmitted, 7 received, 0% packet loss, time 6005ms
rtt min/avg/max/mdev = 78.697/80.101/82.796/1.235 ms

When I try to browse to that IP address, I get this:

Your connection is not private

Attackers might be trying to steal your information from 176.32.103.205 (for example, passwords, messages, or credit cards). Learn more

NET::ERR_CERT_COMMON_NAME_INVALID

This server could not prove that it is 176.32.103.205; its security certificate is from *.peg.a2z.com. This may be caused by a misconfiguration or an attacker intercepting your connection.

**************************************************************

Anyone have any idea what might be going on? This only started in the past day or so.

Note: I have the same problem on my virtual Windows machine. I simply cannot access Amazon from this hardware.

[Update a while later]

None of the proferred explanations so far explain why it’s only (AFAIK) amazon.com.

[Afternoon update]

OK, the problem is with ExpressVPN. When I disconnect it, and put Google’s nameserver in /etc/resolv.conf, it works. So I guess I need to talk to them.

[Late afternoon update]

OK, the problem seemed to be the San Francisco VPN server (the default). When I connected to LA instead, the problem went away.

Fedora Problem

I’m running Fedora 31 (I know, I should update to at least 32), with two monitors. One monitor is always in Workspace 3 (its primary function is to display a virtual Windows installation). Sometimes, when the machine wakes up, only the main monitor will wake up. I can activate the other one by going into settings, changing it from “Join” to “Mirror,” then reverting. But the problem with this is that, in addition to being a PITA, it for some reason jumbles up my work spaces, moving things around that I then have to rearrange the way I want them. Does anyone have any suggestions?

[Update on November 6th)]

I upgraded to 32, and the problem seems to have gone away. So I guess it wasn’t just me.

[Bumped]

Continued Light Blogging

I’m sort of on vacation this week. I gave a talk in Omaha on Friday as part of a space panel with General Kwast and Joel Sercel, on the economics of space, to a Free Market Forum sponsored by Hillsdale College. It seemed to go well, and seemed to be an eye opener for many in the audience, so it was great to preach to someone other than the choir.

We’re in Michigan now, visiting family and checking out the fall colors for the first time in a long time. Unfortunately, I’m also boning up for my deposition next week in DC by Mann’s lawyer. So I’ll keep an eye on things, and post if something noteworthy happens, but consider this an open thread for now.

Virtual Box Woes

I just did a Fedora reboot after a kernel upgrade, and when I try to start Windows in Virtual Box, I get this error:

************************************************************

Kernel driver not installed (rc=-1908)
The VirtualBox Linux kernel driver is either not loaded or not set up correctly. Please try setting it up again by executing ‘/sbin/vboxconfig’ as root.

If your system has EFI Secure Boot enabled you may also need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system’s documentation for more information.

where: suplibOsInit what: 3 VERR_VM_DRIVER_NOT_INSTALLED (-1908) – The support driver is not installed. On linux, open returned ENOENT.

**************************************************************

When I run /sbin/vboxconfig, I get:

******************************************************************

vboxdrv.sh: Stopping VirtualBox services.
vboxdrv.sh: Starting VirtualBox services.
vboxdrv.sh: Building VirtualBox kernel modules.
vboxdrv.sh: failed: Look at /var/log/vbox-setup.log to find out what went wrong.

There were problems setting up VirtualBox. To re-start the set-up process, run /sbin/vboxconfig as root. If your system is using EFI Secure Boot you may need to sign the kernel modules (vboxdrv, vboxnetflt, vboxnetadp, vboxpci) before you can load them. Please see your Linux system’s documentation for more information.

****************************************************************

Here’s the log:

****************************************************************

Building the main VirtualBox module.
Error building the module:
/tmp/vbox.0/Makefile-header.gmk:100: *** The variable KERN_DIR must be a kernel build folder and end with /build without a trailing slash, or KERN_VER must be set. Stop.

*******************************************************************

Now what?

[Noon update]

So I followed the instructions here, including the reboot, and still no joy. Now the error log is (click on “continue reading if you want to see it):

[Update a while later]

OK, it was the new kernel. I reverted to the previous one and it’s fine. I wonder if I should report this to Oracle, or Fedora, or both?

[Update a while later]

OK, I updated to the new version of VirtualBox, and it now works with the new kernel. I guess VB doesn’t automatically update when I do a general update. I should probably add the repository for it.

Continue reading Virtual Box Woes

Computer Problems

So the parts arrived today, and I’m installing the motherboard. The problem is, in addition to the 24-pin power connector, there are slots for an 8-pin and a 4-pin, right next to each other. But the PSU has no 4-pin connector; it only has an 8-pin, and four 6+2s. What am I supposed to do? I see that on my own X570 board from MSI (similar to the new one, but a different model), I didn’t use it, and it seems to be running OK. So just ignore?

[Update a while later]

Well, it seems to be running fine without it.

The good news: It works. The bad news: The new processor isn’t compatible with Windows 8.1; it says it needs to upgrade to 10. And I can’t get good screen resolution, which will probably get fixed after an upgrade.

[Wednesday-morning update]

OK, $200 later, we upgraded to 10, but still crap resolution. Had to install Nvidia drivers to clean things up. But now all seems well. So far.

Computer Fun

Patricia’s machine has been acting up for months, dying unexpectedly. I tried replacing CPU, memory, and power supply. Also cleaned the CPU heat sink. But to no avail, and now it shuts down almost immediately after boot. So it’s probably the motherboard.

And of course you can’t buy new FM-2 mobos any more, so it means new processor and memory as well, plus a graphics card, because the Ryzen doesn’t support on-board integrated graphics. So we just had to lay out about $600 for an upgrade, but it will be a much better machine, with a Ryzen 5 3600X (same as mine) and 32G of RAM in a single stick (upgradable to 128G). It will also be able to support multiple monitors. Unfortunately, it won’t be here before Tuesday.

[Sunday-morning update]

Wow, time flies. I just realized from an old blog post that her mobo was five years old.

Quarantine Lessons From Spaceflight

Thoughts on the similarities.

Meanwhile, we’re back home. As noted, we did drive up to Cambria (with the cats, which was…interesting — it was their first road trip, and Ember cried most of the way). It was relaxing up there, but a little weird, with all the restaurants being closed except for delivery or carry out, and most of the motels empty (we had a vacation rental across the street from the beach). We drove up to Ragged Point on Saturday (which was also closed except for gas and the general store), but no further into Big Sur, then perused the elephant seals on the way back to town. Not that many on the beach; it was just past mating season. A few week ago the beach at Piedras Blancas would have been full of them, fighting and fu**ing (I could have just written “mating,” but I liked the alliteration), and the mothers and pups trying to avoid being crushed by the bulls.

Did a three-mile hike Sunday on the bluffs above the ocean, and shot lots of pictures of breaching and fluking gray whales and their spouts as they migrated north. Very weird being up there on a weekend with so little traffic. I may post some, after we look at them to see how they came out.

Got back to Redondo Beach yesterday (the lack of heavy traffic on the 405 through Sepulveda Pass and West LA on a Monday afternoon was a little eerie), and now get to put the house back together after fumigation. The cats (who cried all the way back) are looking around and at each other like they’re wondering “Was that all some sort of weird dream?” Not infected, as far as we know (seems unlikely, considering that we were already hermits before this all started; it’s an introvert’s paradise).

[Update mid-morning]

One thing we saw up there that we never see in LA: Stars. We were across the street from the beach, and it was quite a dark neighborhood. Orion was very obvious, and I could easily see the Pleides naked eye. Milky Way wasn’t obvious, though.

Safer At Someone Else’s Home

California turned up the screws last night, but extermination is an exempted activity, so the fumigators are still coming today, and we’re still driving up to Cambria (and returning Monday) with the cats. If anyone stops us, I’m pretty sure that once we explain the situation, we’ll be waved on. But there is still plenty of traffic on the highways (though nothing like normal), so no reason to pull us over (unless I actually do something wrong). I may be a little less leadfoot than usual.

[Saturday-morning update]

Probably the quickest trip from LA to Cambria ever–about three and a half hours, which was good because we had a crying cat. Traffic was light, and moving along at 80 mph on the freeways. More anon.