Saturday, December 26, 2015

Andy's Beef Wellington 2015

We did this last year ( but have refined it and had even more fun.

I despair of cooking instructions that say "season to taste" and "cook until done." So herewith is my own nerdy geek approach to a deontological preparation of Beef Wellington and its accoutrements...

We learned a bit of history of why it is called what it is.

One theory is that it is a celebration of Wellington's defeat of Napoleon by taking an intrinsically French dish (boeuf en croute) and making it intrinsically English as a final snub over Wellington's defeat of Napoleon.

First, however, reflect on the Duke of Wellington. This was one huge suck-up guy: commissioned in 1787, soon became  aide-de-camp to two successive Lords Lieutenant of IrelandHe was a colonel by 1796, barely nine years later (most people take some twenty years to reach that rank: Army Colonel, Navy Captain).

Be that as it may, he certainly was one accomplished fellow. And he decidedly defeated Napoleon.

I just wonder about his love life. 

But whatever, the meal is pretty wonderful and a lot of fun (if time consuming) to prepare (and consume). :-)

I happily spent about three hours preparing and another two executing in the excellent company of a friend and a lovely bottle of Malbec...

I drew inspiration this year from Tyler Florence:

His major contribution was his pointing me to Duxelles, a mix of mushrooms and herbs and other good stuff that supplants the hideous (IMHO) offal-based paté..

As good as it is, I have adapted it as described below. 

So, with all that, pour yourself a small (100ml) glass of red wine and get started:

First, collect the ingredients. Tyler is targeting a three pound roast, I had a one pound Chateaubriand. So I divided his ingredients by three: half a pound (8 oz.) of mushrooms. But not enough, next time go for a pound of mixed mushrooms for a pound of meat.

Shaw's vegetable team are pretty awesome: fresh oyster, shitake, and portabella mushrooms, so I mixed them up. (The checkout counter calls them "Exotic" mushrooms...)

Next, add to Tyler's recipe: I want chestnuts. 

Yes I know, roasting chestnuts by an open fire. Except it is 60°F outside and the fellow who promised me firewood sold it to someone else. So to heck with the open fire, do otherwise: Just roast them on a pan in the oven:

Note the 425°F oven instructions. This comes in handy, as bread requires 450°F while the Beef Wellington returns to 425°F. Time management, later.

OK, we chop all that up and put it in the mix and now are ready to cook the duxelles:

in a skillet at a low heat. As Tyler points out, the point is to remove as much liquid as possible while blending the flavors, so as to approximate a paté without including the offal. But do not throw away or burn off the liquid. Reserve it for the sauce (later):

So while that is simmering down, prep the rest. Cut out the eyes of the potatoes, get the rest of the mushrooms washed and cleaned, chop the ends off the green beans. (I don't like Tyler's "Wilted Greens", in fact I don't much like anything "wilted", including limp wrists...) And when done, we are ready to go into action:

Ah! And this is critical: SEAR THE MEAT.

The idea is to keep the juices inside the meat and not in the pastry!!

Last year we did not know this, so the juices ran and the bottom of the pastry was soggy. Once burned (or soggy), twice foolish.

Additionally, just to make sure, we used the turkey basting rack to keep the Wellington off the baking surface, to allow browning all around.

Phew. Another cup of wine and we are ready to execute:

Ooops. Not quite yet. The shell...

Tyler brilliantly suggests wrapping the duxelles with prosciutto. Yet another delicious barrier to sogging up the puff pastry. So we do so. 

I know there is a huge argument of whether you want or don't want the fat in the prosciutto. Personally, I do not. So I strip most of it away, but save some to serve as horizontal binder across all the fractured bits.

So we lay out the puff pastry and cover it with prosciutto:

Yet another level of detail into which we shall not delve, except to say: 

Most marketed "puff pastry" is margarine based. I wanted real butter, but could only buy it for a family of fifty (restaurant supply). OK, at the time I had some money so did so and froze the rest. It's been in the freezer for a year. And yes, Virginia, it dries out, even though frozen. So a huge opportunity for some capitalist purveying to the top percentiles with authentic prepared puff pastry using butter, not margarine. 

But I digress. In the event we used what we had.

As Tyler points out, first lay a spread of plastic film (Saran wrap, whatever) and lay the puff pastry on top of it.

OK, now this is the really tricky part. As I found out, if you have let the puff pastry thaw out too long it sticks to the paper. So the first batch was a total loss. So I got out the second one. Except it had broken in the freezer. :-( Third time's a charm, except it also had a few breaks. But letting it mellow a while until you didn't have to force it (about thirty minutes) I could spread it out on the counter and using just a few drops of water seal the cracks, then spread the duxelles on top over the prosciutto. Like I said, we probably needed another ¼ pound of mushrooms and herbs (next time):

Phew. A top up for the wine...

Now we can carefully put the beef on the duxelles topside down about three inches from the left edge of the pastry and then, with the aid of a large knife and spatula, lift the edges of the puff pastry and duxelles over the meat and roll the whole lot to the right, obviously keeping the underlying Saran out of the way. Then tuck the ends in and cover them with the ends of the plastic wrap.

The result:

The butcher manager at Shaw's Middletown, RI did a perfect job: uniform size.

Now let that solidify in the fridge for half an hour while we do other stuff.

Like, bake the bread that we had prepared earlier...

Time management:
• The Wellington requires 30 minutes or so to rest and solidify in the fridge.
• It then requires about 30-40 minutes in a 425°F oven.
• The previously prepared oven-ready bread requires a 450°F oven for about 30 minutes...
• The potatoes require a 425°F oven.

Duh, bake the bread while the Wellington rests, then reduce the temperature to 425°F for the meat and potatoes.

But when the time arrives, yet another important point:

Use a rack. Ensure Tyler's egg wash (whites of two eggs, save the other four eggs for tomorrow's omelette...) covers the whole assemblage, including the ends.

Last year we put the wrapped beef directly on the baking sheet. The bottom became soggy because of the juices. This year, despite the prosciutto, we expected the same, so used a turkey roasting rack to hold the entire assemblage up in the air. It worked just fine:

OK, yet another topup. Set the timer for 30 minutes to check things.

While the Wellington is doing it's thing get the vegetables, potatoes, and other stuff underway. Put the potatoes in the oven with the Wellington immediately:

Then choppity choppity on mushrooms:
and start simmering garlic, shallots, beef bouillon, four slices of butter, lemon, olive oil (including truffle oil),  red wine, mushroom stems, and the previously reserved duxelle juices for a sauce, and fifteen minutes into the drill put the beans in a steamer for about 15 minutes to come out at the same time as the meat:

And while that is going on, nick the remaining chestnuts and set them to roast in a pan under the meat in the oven, while preparing the bread to be rewarmed:

The meat thermometer is essential:

It looked done but the thermometer said 100°F, not 125°F.

Finally, it is done:

And it is served:

:-) Merry Christmas!

Friday, December 18, 2015

Due Process

The need for due process:

This cannot be watched by too many people:

"What about the eight amendment? What if we say: "You cannot get a lawyer until you petitition the Government to get of the List?

"What about the first? What if we say: "You cannot get a Google account or go to church until you petitition the Government to get of the List?

"What about..."

Climate, Damned Climate, and Lies

"I’m reminded of a line from one of C.S. Lewis’s Narnia stories (The Magician’s Nephew), which runs: “Now the trouble about trying to make yourself stupider than you really are is that you very often succeed.” And the climatistas are certainly willing to oblige."

Nothing more to say: Just the facts...


Monday, December 14, 2015

How to connect an AT&T Velocity WiFi Hotspot as a LAN router

BLUF: turn off static IPas.

The AT&T Velocity WiFi hot spot can indeed function as a router for up to eight devices on a given subnet (e.g., Devices shall be recognized and connected for normal LAN and WAN operations, but only if connected to the Subnet through DHCP. Static IP addresses are not supported and shall not connect.


I recently bought a contract for the AT&T Velocity WiFi Hotspot:

Very sweet.

My intent is to move from a landline ISP to the AT&T wireless provider since I'm changing my lifestyle to something considerably more mobile than the present.

It sets up two subnets: Main and Guest. You can set up different permissions for each and it supports up to eight users on Main and two on Guest.

I presently wirelessly entertain two laptops, a cellphone, a tablet, a printer, and an audio player (Logitech Squeezebox) (six devices) all connected to my ( LAN. It has Internet connectivity through a Belkin N+ router connected with CAT 5 cable to a Motorola modem, connected in turn with coax to the local cable Internet provider.

They all sing and dance together. I can send audio streams from the Logitech Media Server - LMS installed on the laptop to the audio player (Squeezebox), print streams to the printer, sync the cellphone calendar with the OwnCloud server on the laptop, download the London Times to the tablet and more.

All cool.

But my current measly 300 MB AT&T cellphone account costs ~$90 a month. The cable service, offers 250 GB data a month, of which I only use around 20 GB — I don't watch television or play games. Just browsing, email, remote server administration, and system upgrade and software downloads, So I don't need no steenking 250 GB.

And the steenking cable bill is ~$60 a month.

So I'm paying $150 a month for a lot of what I don't want or need (too much landline throughput) and too little of what I do want (mobile wireless throughput).

Hence the change: I can cancel the landline and get 20 GB of AT&T wireless throughput for about the same amount as the previous combination.

But only one catch: how to connect the printer, audio, sync, etc?

Much googling, much experimentation. No Joy.

I could connect the cellphone, tablet, and laptop to the hot spot, but not the printer or audio device. They connect to with no complaint on their part, but the hot spot does not see them.

Much googling again:

• Get a wireless Ethernet bridge. Put it in line to receive WiFi from the hot spot ( and bridge it to the Ethernet port on the router. This would give me subnet to the hotspot. Then connect my devices as usual to the router at and it would all be fine.

     Sorry, the hot spot doesn't recognize the bridge either.

• Get smart about nmap, route -n, ip route add, and a host of other very geeky route table manipulation tools. I can now play the route tables like a keyboard. At least we figured out how to simultaneously connect Ethernet and WiFi (it's the "metrics", stupit...) but still no joy.

Hours spent. Interesting and informative hours, but a total waste of time insofar as solving the problem, except perhaps useful in eliminating many possible causes.

So time is a-wasting, let's just push the car back up the hill to see if the brakes fail again... :-(

Go back and set a static IP for the laptop on the hot spot network. Default gateway (the hot spot) is So let's set the laptop to Just like we did on the existing LAN: the default gateway (router) was 192.168.x.1, the network controller laptop was 192.168.x.2.

So change x=5 to x=7 and it should work the same, right?


Sigh, okay just stop thinking, just do the default: DHCP.

Poof! All of a sudden the laptop now connects. The hot spot does not support static IP addresses!!!

Woohoo! Finally!

Sure enough:

• Set the printer wireless configuration to "Automatic" (DHCP) and read its IPa: We have to go through reconfiguring yast2 printer (we're on Linux openSUSE 13.2 but the principles are the same for other OSs). And then it just works.

• Next the Squeezebox. Same same, change from static IPa to DHCP and it just works. Read its IPa:

• And the same for the CALDAV sync from Android to laptop. Enter the laptop's DHCP IPa ( and poof! it works.


The AT&T Velocity WiFi hot spot can indeed function as a router for up to eight devices on a given subnet (e.g., Devices shall be recognized and connected for normal LAN and WAN operations in the order directed by their metrics, but only if connected to the Subnet through DHCP. Static IP addresses are not supported and shall not connect.

Now I can get on to more important things..