Re: Connectivity for a qemu guest; was Re: Connection of a qemu guest to the 'net.

[Berto Furth]

There's no problem running a system as both a router and a host/desktop/server 
of any other kind.

On Mon, 22 Mar 2021, at 19:05, Steve Litt wrote:
> Berto Furth said on Sun, 21 Mar 2021 08:32:28 +1100
> 
> >Hi Steve,
> >
> >I'll let Peter reply but here's my brief thought.
> >
> >On Sun, 21 Mar 2021, at 02:57, Steve Litt wrote:
> >> peter@easthope.ca said on Fri, 19 Mar 2021 09:33:07 -0700
> >> 
> >>   
> >> >(4) Q: Why does qemu involve a bridge rather than only routing?
> >> >
> >> >A: My hypothesis.  Routing requires adjustment of iptables. Direct 
> >> >editing of iptables is difficult and error prone for non-experts.
> >> >An alternative is to use Shorewall or similar functionality.
> >> >Shorewall is large package.  Imposing dependance of qemu on
> >> >Shorewall will be unwelcome to some users.  A bridge is an
> >> >expedient solution.   
> >> 
> >> I'm unclear as to how "routing" is an alternative to a bridge and
> >> vice versa. Would this "routing" take place on the hardware host, or
> >> the software guest? Did you by any chance mean NAT instead of
> >> "routing"?  
> >
> >Routing would take place on the host. The host would be reconfigured
> >to be a router and the guests would be on their own IP subnet.
> 
> If I reconfigured the metal host to be a router, could I still run that
> metal host as a day to day desktop computer? Would I need to change
> anything to do so?
> 
> Thanks,
> 
> SteveT
> 
> Steve Litt 
> Spring 2021 featured book: Troubleshooting Techniques of the Successful
> Technologist http://www.troubleshooters.com/techniques
> 
>