David Mc Carthy
@davidehmcee.bsky.social
Chip designer. Academic currently in industry. He/him. Interested in vintage computers, mostly 90s RISC/unix stuff. Also interested in bridge (the card game) and video games.
Oh wow nice find... oh its a nanoraptor.
Good to see you're back on form!
Good to see you're back on form!
September 6, 2025 at 11:00 AM
Oh wow nice find... oh its a nanoraptor.
Good to see you're back on form!
Good to see you're back on form!
My Norton is from back when he was still at the company so yes, entirely possible I might need an update.
April 21, 2025 at 7:53 PM
My Norton is from back when he was still at the company so yes, entirely possible I might need an update.
And it works, accessible from both the host and devices on the network and the host. Only cost I guess is that packets are going through two virtual L2 switches but I think that was the case even with a macvlan directly attached to the bridge. (7/?)
January 8, 2025 at 2:30 PM
And it works, accessible from both the host and devices on the network and the host. Only cost I guess is that packets are going through two virtual L2 switches but I think that was the case even with a macvlan directly attached to the bridge. (7/?)
From all this reading on container networks I learned with a veth is. What I came up with in the end was to create my own veth pair, one end in the existing bridge with the physical interfaces, and used the other end as a parent interface for a macvlan container network. (6/?)
January 8, 2025 at 2:30 PM
From all this reading on container networks I learned with a veth is. What I came up with in the end was to create my own veth pair, one end in the existing bridge with the physical interfaces, and used the other end as a parent interface for a macvlan container network. (6/?)
Next I tried macvlan. That works pretty well for other computers on the network accessing the container but has a major limitation in that the host server cant access the containers. For me that's a dealbreaker, I want that connection for management and container non-container interactions. (5/?)
January 8, 2025 at 2:30 PM
Next I tried macvlan. That works pretty well for other computers on the network accessing the container but has a major limitation in that the host server cant access the containers. For me that's a dealbreaker, I want that connection for management and container non-container interactions. (5/?)
Of the container networking models available "bridge" seems like the obvious one but that doesn't seem to want to use an existing bridge, instead it wants to make its own private bridge and NAT that. (4/?)
January 8, 2025 at 2:29 PM
Of the container networking models available "bridge" seems like the obvious one but that doesn't seem to want to use an existing bridge, instead it wants to make its own private bridge and NAT that. (4/?)
For networking these containers I want to appear as if they were extra physical machines on the network. I already have a bridge configured on the server so that both wired and wireless can see each other, so adding the containers to that is the general plan. (3/?)
January 8, 2025 at 2:29 PM
For networking these containers I want to appear as if they were extra physical machines on the network. I already have a bridge configured on the server so that both wired and wireless can see each other, so adding the containers to that is the general plan. (3/?)
Up to now, everything has been running on a single linux install on an SBC, and I kind of want to that way for power consumption.
I chose podman as the container engine since it has a reputation for being light, though all of the following seems to be standard across linux containers. (2/?)
I chose podman as the container engine since it has a reputation for being light, though all of the following seems to be standard across linux containers. (2/?)
January 8, 2025 at 2:29 PM
Up to now, everything has been running on a single linux install on an SBC, and I kind of want to that way for power consumption.
I chose podman as the container engine since it has a reputation for being light, though all of the following seems to be standard across linux containers. (2/?)
I chose podman as the container engine since it has a reputation for being light, though all of the following seems to be standard across linux containers. (2/?)
With Maccy's youthful good looks its easy to forget what a long career he's had.
January 3, 2025 at 9:29 PM
With Maccy's youthful good looks its easy to forget what a long career he's had.
Received the book as a holiday gift this year. Can confirm, Very Pretty.
January 2, 2025 at 8:20 PM
Received the book as a holiday gift this year. Can confirm, Very Pretty.
oh wow that is quite the handle
December 15, 2024 at 3:31 AM
oh wow that is quite the handle
Aww, I was hoping it'd be passthrough so I could wire my setup computer -> mouse -> keybaord but no such luck.
October 14, 2023 at 1:18 PM
Aww, I was hoping it'd be passthrough so I could wire my setup computer -> mouse -> keybaord but no such luck.