Re: [PATCH v1 RFC 4/4] host: integrate router

[Yureka <yuka@yuka.dev>]

The code review of the router code is not helpful at this stage, as I 
hoped to convey in the cover letter.

We should however address the IPv4 support question (see below).


On 11/24/25 20:10, Demi Marie Obenour wrote:
> On 11/24/25 11:35, Yureka Lilian wrote:
>> This removes the old host bridge + taps glue, and instead connects the
>> apps to their net provider's router instance.
> As mentioned in my reply to the last email, I'd like to see the old
> code kept as an option until the router gains IPv4 support.  Right now,
> I have no way of testing this code except by setting up a VPN.

You will be able to test the code using the integration tests once I 
have adapted them. You can also always test against a local IPv6 
link-local target in your home network, or using pasta/passt emulation 
for testing handling of router advertisements.

Supporting both the host network path and the spectrum router at the 
same time adds a lot of complexity in start-vmm because of how 
differently they function, and I wouldn't consider it an option.

If IPv4 support is a requirement, I would propose adding rudimentary 
support for it to the router early in a similar fashion as IPv6 (with 
one IP per VM). Otherwise, I'm planning to add IPv4 support later with 
connection tracking and network address translation.