network doesn't works well about busybear-linux HOT 7 CLOSED

from busybear-linux.

@michaeljclark Sorry to mention you I think you just answer my second question . For this question I follow your steps and works now I can see eth0 again even I force to kill busybear-linux.

My first quetion is : my host bridge(br0) is 192.168.80.73 but eh0 in busybear is always 192.168.100.2 , why does it happened ? Anything else I can do ?

Thx

from busybear-linux.

192.168.100.2 is set inside guest:
root@ucbvax:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
address 192.168.100.2
netmask 255.255.255.0
broadcast 192.168.0.255
gateway 192.168.100.1

I could ssh to guest, but my guest always report:
ntpd: bad address '1.pool.ntp.org'
ntpd: bad address '0.pool.ntp.org'
Still not resolved

from busybear-linux.

I am having the same problems with the network as the previous two comments ie no network connectivity as shown by the "ntpd: bad address '1.pool.ntp.org'" errors. I believe I have set up the bridge correctly and can see that tap0 is being attached by the startup script. On the host (Ubuntu 20.04)

macd@macd-lp:~$ brctl show br0
bridge name	bridge id		STP enabled	interfaces
br0		8000.9ecf16a76bb0	yes		enp9s0
							tap0

On the guest

root@busybear:~# cat /etc/network/interfaces 
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
	address 192.168.122.2
	netmask 255.255.255.0
	broadcast 192.168.122.255
	gateway 192.168.122.1

Doing the ifdown eth0 ifup eth0 did not help. Also the scripts do have access to ifconfig.
Perhaps this is only a problem with documentation, but after reading a half a dozen blog posts and the Ubuntu documentation on bridged networking, I still do not have a solution. Any pointers (or fixes?) would be appreciated.

from busybear-linux.

OK, maybe this should be obvious, but a couple of changes to the /etc/network/interfaces file will make this work. On the host, use ifconfig to get the ip address. In my case this is 192.168.1.113. Use this for the gateway address in interfaces file. Then choose an ip address that won't clash, in my case I chose 192.168.1.123. Then use ifdown eth0 followed by ifup eth0 (on the guest busybear linux)

root@busybear:~# cat /etc/network/interfaces
auto lo
iface lo inet loopback

auto eth0
iface eth0 inet static
	address 192.168.1.123
	netmask 255.255.255.0
	broadcast 192.168.122.255
	gateway 192.168.1.113

Finally, I changed ntp.conf to that below. But still getting timeouts although system clock has been updated. Probably ntp still needs better config info.

root@busybear:~# cat /etc/ntp.conf
server 0.north-america.pool.ntp.org
server 1.north-america.pool.ntp.org

from busybear-linux.

from busybear-linux.

I installed libvirt-bin (via pkg manager), and this solved my issues: busybear could use eth0 even though there was no eth0 on the host, via the virbr0 network interface (from libvirt-bin).

This is w.r.t. booting via busybear-linux/scripts/start-qemu.sh.

from busybear-linux.