Comment 5 for bug 1908012

Sorry, that is not the same!!

I'm connected to a router and a router does give me the IP address, a
bridge does not provide you with an IP address, so the system will
react differently.

As you should have noticed from my description, it goes wrong trying to
get a web address resolved after having received my IP address from the
router's DHCP.

Note that I use TWO routers. the one closest to my desktop gives the IP
address (router=192.168.1.1), but both need to be connected to get to
the internet. The other one from the ISP has 192.168.0.1. The cable
between both routers was broken.

It is the configuration I did choose, to get wifi coverage in whole the
house.

Like I said I have done my part, there is nothing more I can do, since
you do not seem to understand the issue.

On Mon, 2021-01-04 at 11:30 +0000, Christian Ehrhardt  wrote:
> Thank you for your explanations BertN45,
> I've taken a VM and tried to replicate your scenario by keeping it
> connected to a bridge, but that bridge not connected anywhere else).
> That should match your case - but Ubuntu Server as well as Ubuntu
> Desktop guests started well in my case.
>
> So either it must be something special (package installed,
> configuration) in your failing Ubuntu systems OR your network issue
> was more complex than just "connected to net, but not the internet".
> Either way we'd need more details and tries on your end, since you
> stated that you won#t come/reply back we are again at what Lucas
> mentioned - a not actionable bug.
>
> Therefore I'm keeping it in incomplete state so that it can auto-
> expire
> if no further updates happen.
>