Well, I might have an idea now of what's causing this issue, but I'm not totally sure. Here's the output of brctl show:
Code:
caseyfriday@fridaynode:~$ brctl show
bridge name bridge id STP enabled interfaces
br0 8000.7427ea486386 no eth0
vnet0
virbr0 8000.000000000000 yes
caseyfriday@fridaynode:~$
So I'm guessing vibr0 is the virtual bridge being used by the kvm? If so, that could be problematic, because here's the output of ifconfig:
Code:
caseyfriday@fridaynode:~$ ifconfig
br0 Link encap:Ethernet HWaddr 74:**:**:**:**:**
inet addr:192.168.0.100 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:312848 errors:0 dropped:0 overruns:0 frame:0
TX packets:744171 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:879466873 (879.4 MB) TX bytes:747974155 (747.9 MB)
eth0 Link encap:Ethernet HWaddr 74:**:**:**:**:**
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:282190 errors:0 dropped:0 overruns:0 frame:0
TX packets:178014 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:363054215 (363.0 MB) TX bytes:40208598 (40.2 MB)
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:22308 errors:0 dropped:0 overruns:0 frame:0
TX packets:22308 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:20714933 (20.7 MB) TX bytes:20714933 (20.7 MB)
virbr0 Link encap:Ethernet HWaddr d2:**:**:**:**:**
inet addr:192.168.122.1 Bcast:192.168.122.255 Mask:255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 B) TX bytes:0 (0.0 B)
vnet0 Link encap:Ethernet HWaddr fe:**:**:**:**:**
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:388443 errors:0 dropped:0 overruns:0 frame:0
TX packets:927506 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:500
RX bytes:881273680 (881.2 MB) TX bytes:1069554225 (1.0 GB)
caseyfriday@fridaynode:~$
vibr0 has an IP address not in the same subnet as the rest of my devices. So how can I set the IP address for vibr0, so that my VM's network bridge keeps it on the same subnet as everything else?
Edit: I've just read that vibr0 is for NAT only, and I'm not using NAT in my kvm - just using a bridge. I still don't know why I can't access my NAS's services, share iTunes, etc, while internet access is working fine.
Bookmarks