Gerry Reno wrote:
Suren Karapetyan wrote:
It would help if You did "ifconfig" and "brctl show" on the host PC
while guest is running and posted it here. That way we could find out
what's happening.
BTW: Is eth0 on host configured via DHCPD or static?
I made some small progress. I had an existing bridge br0 and
virt-manager created a second bridge virbr0. vnet0 and vnet1 became
attached to my br0 bridge and not virbr0. Now I don't see why that
should be a problem but apparently it is. So I destroyed my bridge.
Changed the vm defines to reflect virbr0 and restarted everything. So
now in the guest I can ping 192.168.122.1 which is the virbr0. But
that's all I cannot get access to the lan. When I originally had setup
the images via virt-manager gui I selected shared networking and it was
showing br0(eth0) which was my original bridge. I was expecting it
would slave to this and then I would have a bridge to my lan address
space. But this did not work and I had access to nothing. So how can I
define a bridge on my lan and have the guests slave to it so that they
can get either a lan dhcp address or a static lan address?
Here are the current conditions:
eth0 Link encap:Ethernet HWaddr 00:1A:4D:5E:F6:36 inet
addr:192.168.1.15 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::21a:4dff:fe5e:f636/64 Scope:Link
UP BROADCAST RUNNING PROMISC MULTICAST MTU:1500 Metric:1
RX packets:27833013 errors:0 dropped:0 overruns:0 frame:0
TX packets:36339801 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3841204956 (3.5 GiB) TX bytes:1079379274 (1.0 GiB)
Interrupt:19 Base address:0xc000
lo Link encap:Local Loopback inet addr:127.0.0.1
Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:142210 errors:0 dropped:0 overruns:0 frame:0
TX packets:142210 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:286289024 (273.0 MiB) TX bytes:286289024 (273.0 MiB)
virbr0 Link encap:Ethernet HWaddr 00:FF:12:85:0F:D0 inet
addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
inet6 addr: fe80::1cc7:34ff:fe82:fdbc/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:5925 errors:0 dropped:0 overruns:0 frame:0
TX packets:5228 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:432804 (422.6 KiB) TX bytes:4295659 (4.0 MiB)
vnet0 Link encap:Ethernet HWaddr 00:FF:12:85:0F:D0 inet6
addr: fe80::2ff:12ff:fe85:fd0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:105 errors:0 dropped:0 overruns:0 frame:0
TX packets:269 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:17377 (16.9 KiB) TX bytes:17621 (17.2 KiB)
vnet1 Link encap:Ethernet HWaddr 00:FF:16:0F:7D:A0 inet6
addr: fe80::2ff:16ff:fe0f:7da0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:150 errors:0 dropped:0 overruns:0 frame:0
TX packets:147590 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:41461 (40.4 KiB) TX bytes:8863921 (8.4 MiB)
[root@grp-01-10-01 TEST1]# brctl show
bridge name bridge id STP enabled interfaces
pan0 8000.000000000000 no
virbr0 8000.00ff12850fd0 yes vnet0
vnet1
Regards,
Gerry
Your initial configuration was right.
I don't have much skills with bridges so maybe someone more experienced
could correct me but maybe You need ip_forwarding.
And also, bridged packets travel through iptables so You may need some
rules (libvirtd adds some but I don't remember if they are enough).
Could You switch to Your previews settings and post outputs for
ifconfig, brctl show, iptables -L -n -v?
--
fedora-devel-list mailing list
fedora-devel-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/fedora-devel-list
