При выборе спящего или ждущего режимов монитор моргает и выходит на экран приветствия (авторизации).
3.9.5-301.fc19.i686.PAE
mate-window-manager 1.6.2-7.fc19
Перед этой проблемой создал на сетевке пару vlan'ов, и добавил роутинг.
Роутинг делал по этой рыбе (сильно не пинайте):
(В примере адреса первоисточника шаблона)
-----------------------------------------------------
$ iptables -A FORWARD -i eth0 -o eth1 -s 192.168.0.0/24 -j ACCEPT
$ iptables -A FORWARD -i eth1 -o eth0 -d 192.168.0.0/24 -j ACCEPT
$ iptables -P FORWARD DROP
$ iptables -A POSTROUTING -s 192.168.0.0/24 -o eth1 -j SNAT --to-source 10.188.106.33
-----------------------------------------------------
вывод dmesg
[ 4205.536814] IPv6: ADDRCONF(NETDEV_UP): enp6s0: link is not ready
[ 4205.561566] IPv6: ADDRCONF(NETDEV_UP): p2p1: link is not ready
[ 4205.561627] IPv6: ADDRCONF(NETDEV_UP): p2p1.1: link is not ready
[ 4205.561682] IPv6: ADDRCONF(NETDEV_UP): p2p1.234: link is not ready
[ 4205.561740] IPv6: ADDRCONF(NETDEV_UP): p2p1.888: link is not ready
[ 4205.562689] e100 0000:08:01.0 p2p1: NIC Link is Up 100 Mbps Full Duplex
[ 4205.562831] IPv6: ADDRCONF(NETDEV_CHANGE): p2p1: link becomes ready
[ 4205.562898] IPv6: ADDRCONF(NETDEV_CHANGE): p2p1.1: link becomes ready
[ 4205.562929] /dev/vmnet: open called by PID 3216 (vmnet-bridge)
[ 4205.562938] /dev/vmnet: hub 0 does not exist, allocating memory.
[ 4205.562951] IPv6: ADDRCONF(NETDEV_CHANGE): p2p1.234: link becomes ready
[ 4205.562959] /dev/vmnet: port on hub 0 successfully opened
[ 4205.562968] bridge-p2p1: up
[ 4205.563002] IPv6: ADDRCONF(NETDEV_CHANGE): p2p1.888: link becomes ready
[ 4205.563099] bridge-p2p1: attached
[ 4205.563153] bridge-p2p1: disabling the bridge on dev down
[ 4205.563169] bridge-p2p1: down
[ 4205.563176] bridge-p2p1: detached
[ 4205.563194] /dev/vmnet: open called by PID 3216 (vmnet-bridge)
[ 4205.563199] /dev/vmnet: hub 0 does not exist, allocating memory.
[ 4205.563219] /dev/vmnet: port on hub 0 successfully opened
[ 4205.563225] bridge-p2p1.234: can't bridge with p2p1.234, bad header length 18
[ 4205.563228] bridge-p2p1.234: enabling the bridge on dev up
[ 4205.563229] bridge-p2p1.234: can't bridge with p2p1.234, bad header length 18
[ 4205.563231] bridge-p2p1.234: interface p2p1.234 is not a valid Ethernet interface
[ 4205.563233] bridge-p2p1.234: attached
[ 4205.695665] userif-4: sent link down event.
[ 4205.695669] userif-4: sent link up event.
[ 4206.909905] userif-4: sent link down event.
[ 4206.909910] userif-4: sent link up event.
[ 4207.912566] userif-4: sent link down event.
[ 4207.912572] userif-4: sent link up event.
[ 4208.915303] userif-4: sent link down event.
[ 4208.915308] userif-4: sent link up event.
Вижу, что есть проблема, с p2p1.234, но природа мне не ясна,
собственно через этот интерфейс я сейчас с Вами общаюсь )
На всякий случай
Вывод ip route show
----------------------------------------------------
default via 178.74.XXX.XXX dev p2p1.234 proto static
172.16.158.0/24 dev vmnet8 proto kernel scope link src 172.16.158.1
178.74.0.0/16 dev p2p1.234 proto kernel scope link src 178.74.XXX.XXX metric 6
192.168.1.0/24 dev p2p1.888 proto kernel scope link src 192.168.1.1 metric 6
192.168.14.0/24 dev p2p1 proto kernel scope link src 192.168.14.100 metric 1
192.168.14.0/24 dev p2p1.1 proto kernel scope link src 192.168.14.100 metric 6
192.168.51.0/24 dev vmnet1 proto kernel scope link src 192.168.51.1
-----------------------------------------------------