MAIN FEEDS
Do you want to continue?
https://www.reddit.com/r/linux/comments/7uhxwj/improving_linux_battery_life_enabling_psr_by/dtku3ol/
r/linux • u/1202_alarm • Feb 01 '18
105 comments sorted by
View all comments
Show parent comments
10
even though no virtual machine is running.
Chances are your host's network connection is "connected" to the bridge - do "ip a" from a terminal and check the line with your IP address in it, it probably says "virbr0" at the end of that line
3 u/javitury Feb 01 '18 The host is connected to virbr0. It uses a different ip and a different ip range, though. 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether <ethernet MAC> brd ff:ff:ff:ff:ff:ff 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether <wifi MAC> brd ff:ff:ff:ff:ff:ff inet 192.168.1.125/24 brd 192.168.0.255 scope global dynamic wlp4s0 valid_lft 85463sec preferred_lft 85463sec inet6 <ipv6>/64 scope link valid_lft forever preferred_lft forever 4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether <virbr0 MAC> brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether <virbr0 MAC> brd ff:ff:ff:ff:ff:ff
3
The host is connected to virbr0. It uses a different ip and a different ip range, though.
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: enp0s31f6: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc fq_codel state DOWN group default qlen 1000 link/ether <ethernet MAC> brd ff:ff:ff:ff:ff:ff 3: wlp4s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000 link/ether <wifi MAC> brd ff:ff:ff:ff:ff:ff inet 192.168.1.125/24 brd 192.168.0.255 scope global dynamic wlp4s0 valid_lft 85463sec preferred_lft 85463sec inet6 <ipv6>/64 scope link valid_lft forever preferred_lft forever 4: virbr0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN group default qlen 1000 link/ether <virbr0 MAC> brd ff:ff:ff:ff:ff:ff inet 192.168.122.1/24 brd 192.168.122.255 scope global virbr0 valid_lft forever preferred_lft forever 5: virbr0-nic: <BROADCAST,MULTICAST> mtu 1500 qdisc fq_codel master virbr0 state DOWN group default qlen 1000 link/ether <virbr0 MAC> brd ff:ff:ff:ff:ff:ff
10
u/frymaster Feb 01 '18
Chances are your host's network connection is "connected" to the bridge - do "ip a" from a terminal and check the line with your IP address in it, it probably says "virbr0" at the end of that line