[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Сетевуха работает только в promisc режиме



20.05.2012 21:00, Eugene Berdnikov пишет:
> On Sun, May 20, 2012 at 07:58:40PM +0400, "Артём Н." wrote:
>> 20.05.2012 15:41, Eugene Berdnikov пишет:
>>>  Запишите в файлики выдачу "sysctl -a | fgrep eth1" и "ip route list"
>>>  и сравните для вариантов с nm и ifupdown.
>>>
>>>  Для случая с nm ещё хорошо бы записать дамп трафика на eth1,
>>>  чтобы убедиться, что пакеты (не) вылетают из eth1, а обратные
>>>  пакеты идут на mac интерфейса (или на другой mac). Учтите, что
>>>  tcpdump, запущенный без -p, сам переводит интерфейс в promisc.
>>
>> Всё-равно не понятно.
>>
>> Различия:
>> < net.ipv6.conf.eth1.accept_ra = 2
>> ---
>>> net.ipv6.conf.eth1.accept_ra = 0
>> 85,88d84
>> < net.decnet.conf.eth1.priority = 0
>> < net.decnet.conf.eth1.t2 = 1
>> < net.decnet.conf.eth1.t3 = 10
>> < net.decnet.default_device = eth1
>> 92,93d87
>> < default via 192.168.1.1 dev eth1  proto static
>> < 192.168.1.0/24 dev eth1  proto kernel  scope link  src 192.168.1.3
> 
>  Прежде всего, в случае nm нет никаких маршрутов через eth1.
>  Сеть в такой конфигурации работать не будет, это и ежу понятно.
Я добавлял вручную (в случае с nm), по крайней мере, маршрут по умолчанию.
Всё-равно не работало. Маршруты же должны сами установиться, если работает DHCP?
И ещё до этого я задавал настройки конфигурации nm и вручную (в случае с одним
модемом там сложно ошибиться).

>  Хотя меня удивляет то, что в дампе видны arp-request'ы, как будто
>  кто-то пытается послать юникастовый пакет через eth1 при
>  отсутствии маршрута на этот интерфейс... но может быть, я какой-то
>  простой причины для arp'а не вспоминаю.
Кстати, модем его видит и arp таблице модема появляется запись.

>  Кроме того, в дампе только исходящие пакеты. Вероятно, связи со шлюзом
>  просто нет, несмотря на флаги интерфейса UP и RINNING. Хотелось бы
>  проверить, правильно ли выставлен duplex или скорость передачи,
>  сравните выдачу "mii-tool -v eth1" и "ethtool eth1".
В случае с интерфейсом, поднятым через ifup (с nm проверю завтра):
"root@dana:~# ethtool eth1
Settings for eth1:
        Supported ports: [ TP MII ]
        Supported link modes:   10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Supported pause frame use: No
        Supports auto-negotiation: Yes
        Advertised link modes:  10baseT/Half 10baseT/Full
                                100baseT/Half 100baseT/Full
                                1000baseT/Half 1000baseT/Full
        Advertised pause frame use: Symmetric Receive-only
        Advertised auto-negotiation: Yes
        Link partner advertised link modes:  10baseT/Half 10baseT/Full
                                             100baseT/Half 100baseT/Full
        Link partner advertised pause frame use: Symmetric
        Link partner advertised auto-negotiation: Yes
        Speed: 100Mb/s
        Duplex: Full
        Port: MII
        PHYAD: 0
        Transceiver: internal
        Auto-negotiation: on
        Supports Wake-on: pumbg
        Wake-on: g
        Current message level: 0x00000033 (51)
                               drv probe ifdown ifup
        Link detected: yes
root@dana:~# mii-tool -v eth1
eth1: negotiated 100baseTx-FD flow-control, link ok
  product info: vendor 00:07:32, model 17 rev 2
  basic mode:   autonegotiation enabled
  basic status: autonegotiation complete, link ok
  capabilities: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD
10baseT-HD
  advertising:  100baseTx-FD 100baseTx-HD 10baseT-FD 10baseT-HD flow-control
  link partner: 1000baseT-HD 1000baseT-FD 100baseTx-FD 100baseTx-HD 10baseT-FD
10baseT-HD flow-control"

>  В целом, конечно, клиника... А nm'у поднять какой-нибудь log level можно?
Есть опция log-level...
Вот, что он писал в syslog (где successfull, там уже, видимо, интерфейс был
поднят через ifup на этапе загрузки):
"May 20 11:20:47 dana NetworkManager[3070]:    SCPlugin-Ifupdown: init!
May 20 11:20:47 dana NetworkManager[3070]:    SCPlugin-Ifupdown:
update_system_hostname
May 20 11:20:47 dana NetworkManager[3070]:    SCPluginIfupdown: guessed
connection type (eth1) = 802-3-ethernet
May 20 11:20:47 dana NetworkManager[3070]:    SCPlugin-Ifupdown:
update_connection_setting_from_if_block: name:eth1, type:802-3-ethernet,
id:Ifupdown (eth1), uuid: 7b635ed6-2640-7ad8-675d-744db12dd9fa
May 20 11:20:47 dana NetworkManager[3070]:    SCPlugin-Ifupdown: adding eth1 to
iface_connections
May 20 11:20:47 dana NetworkManager[3070]:    SCPlugin-Ifupdown: adding iface
eth1 to well_known_interfaces
May 20 11:20:47 dana NetworkManager[3070]:    SCPlugin-Ifupdown: autoconnect
May 20 11:20:47 dana NetworkManager[3070]:    SCPluginIfupdown: management mode:
unmanaged
May 20 11:20:47 dana NetworkManager[3070]:    SCPlugin-Ifupdown: devices added
(path: /sys/devices/pci0000:00/0000:00:1c.7/0000:01:00.0/net/eth1, iface: eth1)
May 20 11:20:47 dana NetworkManager[3070]:    SCPluginIfupdown: locking wired
connection setting
May 20 11:20:47 dana NetworkManager[3070]:    SCPlugin-Ifupdown: devices added
(path: /sys/devices/virtual/net/lo, iface: lo)
May 20 11:20:47 dana NetworkManager[3070]:    SCPlugin-Ifupdown: device added
(path: /sys/devices/virtual/net/lo, iface: lo): no ifupdown configuration found.
May 20 11:20:47 dana NetworkManager[3070]:    SCPlugin-Ifupdown: end _init.
May 20 11:20:47 dana NetworkManager[3070]: <info> Loaded plugin ifupdown: (C)
2008 Canonical Ltd.  To report bugs please use the NetworkManager mailing list.
May 20 11:20:47 dana NetworkManager[3070]: <info> Loaded plugin keyfile: (c)
2007 - 2010 Red Hat, Inc.  To report bugs please use the NetworkManager mailing
list.
May 20 11:20:47 dana NetworkManager[3070]:    Ifupdown: get unmanaged devices
count: 1
May 20 11:20:47 dana NetworkManager[3070]:    SCPlugin-Ifupdown: (26970928) ...
get_connections.
May 20 11:20:47 dana NetworkManager[3070]:    SCPlugin-Ifupdown: (26970928) ...
get_connections (managed=false): return empty list.
May 20 11:20:47 dana NetworkManager[3070]:    keyfile: parsing eth1 ...
May 20 11:20:47 dana NetworkManager[3070]:    keyfile:     read connection 'eth1'
May 20 11:20:47 dana NetworkManager[3070]:    Ifupdown: get unmanaged devices
count: 1
May 20 11:20:47 dana NetworkManager[3070]: <info> trying to start the modem
manager...
May 20 11:20:47 dana dbus[2099]: [system] Activating service
name='org.freedesktop.ModemManager' (using servicehelper)
May 20 11:20:47 dana NetworkManager[3070]: <info> monitoring kernel firmware
directory '/lib/firmware'.
May 20 11:20:47 dana NetworkManager[3070]: <info> WiFi enabled by radio
killswitch; enabled by state file
May 20 11:20:47 dana NetworkManager[3070]: <info> WWAN enabled by radio
killswitch; enabled by state file
May 20 11:20:47 dana NetworkManager[3070]: <info> WiMAX enabled by radio
killswitch; enabled by state file
May 20 11:20:47 dana NetworkManager[3070]: <info> Networking is enabled by state
file
May 20 11:20:47 dana NetworkManager[3070]: <warn> failed to allocate link cache:
(-10) Operation not supported
May 20 11:20:47 dana NetworkManager[3070]: <info> (eth1): carrier is ON
May 20 11:20:47 dana NetworkManager[3070]: <info> (eth1): new Ethernet device
(driver: 'r8169' ifindex: 2)
May 20 11:20:47 dana NetworkManager[3070]: <info> (eth1): exported as
/org/freedesktop/NetworkManager/Devices/0
May 20 11:20:47 dana NetworkManager[3070]: <info> (eth1): now managed
May 20 11:20:47 dana NetworkManager[3070]: <info> (eth1): device state change:
unmanaged -> unavailable (reason 'managed') [10 20 2]
May 20 11:20:47 dana NetworkManager[3070]: <info> (eth1): preparing device.
May 20 11:20:47 dana NetworkManager[3070]: <info> (eth1): deactivating device
(reason 'managed') [2]
May 20 11:20:47 dana NetworkManager[3070]: <warn> bluez error getting default
adapter: The name org.bluez was not provided by any .service files
May 20 11:20:47 dana NetworkManager[3070]: <info> (eth1): device state change:
unavailable -> disconnected (reason 'none') [20 30 0]
May 20 11:20:47 dana NetworkManager[3070]: <info> Auto-activating connection 'eth1'.
May 20 11:20:47 dana NetworkManager[3070]: <info> Activation (eth1) starting
connection 'eth1'
May 20 11:20:47 dana NetworkManager[3070]: <info> (eth1): device state change:
disconnected -> prepare (reason 'none') [30 40 0]
May 20 11:20:47 dana NetworkManager[3070]: <info> Activation (eth1) Stage 1 of 5
(Device Prepare) scheduled...
May 20 11:20:47 dana NetworkManager[3070]: <info> Activation (eth1) Stage 1 of 5
(Device Prepare) started...
May 20 11:20:47 dana NetworkManager[3070]: <info> Activation (eth1) Stage 2 of 5
(Device Configure) scheduled...
May 20 11:20:47 dana NetworkManager[3070]: <info> Activation (eth1) Stage 1 of 5
(Device Prepare) complete.
May 20 11:20:47 dana NetworkManager[3070]: <info> Activation (eth1) Stage 2 of 5
(Device Configure) starting...
May 20 11:20:47 dana NetworkManager[3070]: <info> (eth1): device state change:
prepare -> config (reason 'none') [40 50 0]
May 20 11:20:47 dana NetworkManager[3070]: <info> Activation (eth1) Stage 2 of 5
(Device Configure) successful."

Ещё, я заметил интересную запись (device state change: ip-config -> failed
(reason 'ip-config-unavailable')):
"May 20 10:36:46 dana NetworkManager[2855]: <warn> (eth1): DHCPv4 request timed out.
May 20 10:36:46 dana NetworkManager[2855]: <info> (eth1): canceled DHCP
transaction, DHCP client pid 2949
May 20 10:36:46 dana NetworkManager[2855]: <info> Activation (eth1) Stage 4 of 5
(IPv4 Configure Timeout) scheduled...
May 20 10:36:46 dana NetworkManager[2855]: <info> Activation (eth1) Stage 4 of 5
(IPv4 Configure Timeout) started...
May 20 10:36:46 dana NetworkManager[2855]: <info> (eth1): device state change:
ip-config -> failed (reason 'ip-config-unavailable') [70 120 5]
May 20 10:36:46 dana NetworkManager[2855]: <warn> Activation (eth1) failed.
May 20 10:36:46 dana NetworkManager[2855]: <info> Activation (eth1) Stage 4 of 5
(IPv4 Configure Timeout) complete.
May 20 10:36:46 dana NetworkManager[2855]: <info> (eth1): device state change:
failed -> disconnected (reason 'none') [120 30 0]
May 20 10:36:46 dana NetworkManager[2855]: <info> (eth1): deactivating device
(reason 'none') [0]
May 20 10:36:47 dana kernel: [   79.468614] audit_printk_skb: 78 callbacks
suppressed
May 20 10:36:47 dana kernel: [   79.468616] type=1400 audit(1337495807.763:38):
apparmor="DENIED" operation="file_lock" parent=4273
profile="/usr/lib/iceweasel/iceweasel" name="/home/artiom/.nv/GLCache/0d4f411$
May 20 10:36:49 dana NetworkManager[2855]: <info> Auto-activating connection 'eth1'.
May 20 10:36:49 dana NetworkManager[2855]: <info> Activation (eth1) starting
connection 'eth1'
May 20 10:36:49 dana NetworkManager[2855]: <info> (eth1): device state change:
disconnected -> prepare (reason 'none') [30 40 0]"


Reply to: