Не поднимается WAN после сбоя



  • Друзья! Такая проблема.
    После сбоя в сети WAN не поднимается до тех пор, пока не передёрнешь кабель или не сделаешь перезагрузку. Подскажите каким способом можно сделать, чтобы pfSense сам поднимал соединение с провайдером.

    pfSense
    2.0.1-RELEASE (i386)
    built on Mon Dec 12 18:24:17 EST 2011
    FreeBSD 8.1-RELEASE-p6



  • Читаем-выкладываем логи. Телепатов пока нет :(



  • Спасибо за ответ. Уже что-то  :)

    Вот системные логи с момента отключения и до момента включения путём передёргивания шнура.

    Jul 23 13:54:28 apinger: ALARM: WAN(89.222.229.254) *** down ***
    Jul 23 13:54:38 check_reload_status: Reloading filter
    Jul 23 13:55:05 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 13:55:05 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 13:55:33 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.11
    Jul 23 13:55:33 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.11
    Jul 23 13:58:26 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 13:58:26 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:00:40 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:00:40 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:01:47 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:01:47 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:05:08 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:05:08 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:08:28 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:08:28 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:10:40 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:10:40 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:11:50 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:11:50 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:15:10 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:15:10 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:18:32 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:18:32 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:20:41 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:20:41 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:21:52 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:21:52 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:25:14 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:25:14 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:27:24 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:27:24 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:28:34 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:28:34 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:30:42 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:30:42 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:31:55 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:31:55 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:35:16 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:35:16 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:38:37 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:38:37 bandwidthd: DNS timeout for 192.168.1.70: This problem reduces graphing performance
    Jul 23 14:39:29 check_reload_status: Linkup starting rl3
    Jul 23 14:39:29 kernel: rl3: link state changed to DOWN
    Jul 23 14:39:35 php: : DEVD Ethernet detached event for wan
    Jul 23 14:39:35 dhclient[26851]: connection closed
    Jul 23 14:39:35 dhclient[26851]: connection closed
    Jul 23 14:39:35 dhclient[26851]: exiting.
    Jul 23 14:39:35 dhclient[26851]: exiting.
    Jul 23 14:39:36 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:37 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:37 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:37 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:38 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:39 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:39 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:39 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:39 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:41 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:41 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:43 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:43 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:43 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:45 kernel: arpresolve: can't allocate llinfo for 89.222.229.254
    Jul 23 14:39:45 check_reload_status: Linkup starting rl3
    Jul 23 14:39:45 kernel: rl3: link state changed to UP
    Jul 23 14:39:50 php: : DEVD Ethernet attached event for wan
    Jul 23 14:39:50 php: : HOTPLUG: Configuring interface wan
    Jul 23 14:39:50 dhclient: PREINIT
    Jul 23 14:39:51 dhclient[43295]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 14:39:52 dhclient[43295]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 14:39:54 dhclient[43295]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 14:39:57 dhclient[43295]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 14:40:05 dhclient[43295]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 2
    Jul 23 14:40:07 dhclient[43295]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 3
    Jul 23 14:40:10 dhclient[43295]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 3
    Jul 23 14:40:13 dhclient[43295]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 8
    Jul 23 14:40:21 dhclient[43295]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 21
    Jul 23 14:40:42 dhclient[43295]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 15
    Jul 23 14:40:57 dhclient[43295]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 9
    Jul 23 14:41:06 dhclient[43295]: No DHCPOFFERS received.
    Jul 23 14:41:06 dhclient[43295]: Trying recorded lease 89.222.229.104
    Jul 23 14:41:06 dhclient: TIMEOUT
    Jul 23 14:41:06 dhclient: Starting add_new_address()
    Jul 23 14:41:06 dhclient: ifconfig rl3 inet 89.222.229.104 netmask 255.255.255.0 broadcast 89.222.229.255
    Jul 23 14:41:06 dhclient: New IP Address (rl3): 89.222.229.104
    Jul 23 14:41:06 dhclient: New Subnet Mask (rl3): 255.255.255.0
    Jul 23 14:41:06 dhclient: New Broadcast Address (rl3): 89.222.229.255
    Jul 23 14:41:06 dhclient: New Routers (rl3): 89.222.229.254
    Jul 23 14:41:07 dhclient: New Routers (rl3): 89.222.229.254
    Jul 23 14:41:18 dhclient: Deleting old routes
    Jul 23 14:41:18 dhclient[43295]: bound: renewal in 96837 seconds.
    Jul 23 15:05:53 check_reload_status: Linkup starting rl3
    Jul 23 15:05:53 kernel: rl3: link state changed to DOWN
    Jul 23 15:05:59 php: : DEVD Ethernet detached event for wan
    Jul 23 15:05:59 dhclient[43758]: connection closed
    Jul 23 15:05:59 dhclient[43758]: connection closed
    Jul 23 15:05:59 dhclient[43758]: exiting.
    Jul 23 15:05:59 dhclient[43758]: exiting.
    Jul 23 15:06:06 check_reload_status: Linkup starting rl3
    Jul 23 15:06:06 kernel: rl3: link state changed to UP
    Jul 23 15:06:12 php: : DEVD Ethernet attached event for wan
    Jul 23 15:06:12 php: : HOTPLUG: Configuring interface wan
    Jul 23 15:06:12 dhclient: PREINIT
    Jul 23 15:06:12 dhclient[34232]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 15:06:14 dhclient[34232]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 15:06:18 dhclient[34232]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 15:06:20 check_reload_status: Linkup starting rl3
    Jul 23 15:06:20 kernel: rl3: link state changed to DOWN
    Jul 23 15:06:22 check_reload_status: Linkup starting rl3
    Jul 23 15:06:22 kernel: rl3: link state changed to UP
    Jul 23 15:06:24 check_reload_status: Linkup starting rl3
    Jul 23 15:06:24 kernel: rl3: link state changed to DOWN
    Jul 23 15:06:25 php: : DEVD Ethernet detached event for wan
    Jul 23 15:06:26 dhclient[34246]: connection closed
    Jul 23 15:06:26 dhclient[34246]: connection closed
    Jul 23 15:06:26 php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf rl3 > /tmp/rl3_output > /tmp/rl3_error_output' returned exit code '15', the output was ''
    Jul 23 15:06:26 dhclient[34246]: exiting.
    Jul 23 15:06:26 dhclient[34246]: exiting.
    Jul 23 15:06:26 check_reload_status: Linkup starting rl3
    Jul 23 15:06:26 kernel: rl3: link state changed to UP
    Jul 23 15:06:28 php: : DEVD Ethernet attached event for wan
    Jul 23 15:06:28 php: : HOTPLUG: Configuring interface wan
    Jul 23 15:06:28 dhclient: PREINIT
    Jul 23 15:06:28 dhclient[29107]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 15:06:29 dhclient[29107]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 15:06:30 dhclient[29107]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 15:06:32 dhclient[29107]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 15:06:34 php: : DEVD Ethernet detached event for wan
    Jul 23 15:06:34 dhclient[29242]: connection closed
    Jul 23 15:06:34 dhclient[29242]: connection closed
    Jul 23 15:06:34 dhclient[29242]: exiting.
    Jul 23 15:06:34 dhclient[29242]: exiting.
    Jul 23 15:06:34 php: : The command '/sbin/dhclient -c /var/etc/dhclient_wan.conf rl3 > /tmp/rl3_output > /tmp/rl3_error_output' returned exit code '15', the output was ''
    Jul 23 15:06:36 php: : DEVD Ethernet attached event for wan
    Jul 23 15:06:36 php: : HOTPLUG: Configuring interface wan
    Jul 23 15:06:36 dhclient: PREINIT
    Jul 23 15:06:36 dhclient[62947]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 15:06:38 dhclient[62947]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 15:06:42 dhclient[62947]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 15:06:47 dhclient[62947]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 1
    Jul 23 15:06:48 dhclient[62947]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 1
    Jul 23 15:06:49 dhclient[62947]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 1
    Jul 23 15:06:50 dhclient[62947]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 2
    Jul 23 15:06:52 dhclient[62947]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 3
    Jul 23 15:06:55 dhclient[62947]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 6
    Jul 23 15:07:01 dhclient[62947]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 11
    Jul 23 15:07:12 dhclient[62947]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 11
    Jul 23 15:07:23 dhclient[62947]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 18
    Jul 23 15:07:41 dhclient[62947]: DHCPDISCOVER on rl3 to 255.255.255.255 port 67 interval 7
    Jul 23 15:07:48 dhclient[62947]: No DHCPOFFERS received.
    Jul 23 15:07:48 dhclient[62947]: Trying recorded lease 89.222.229.104
    Jul 23 15:07:48 dhclient: TIMEOUT
    Jul 23 15:07:48 dhclient: Starting add_new_address()
    Jul 23 15:07:48 dhclient: ifconfig rl3 inet 89.222.229.104 netmask 255.255.255.0 broadcast 89.222.229.255
    Jul 23 15:07:48 dhclient: New IP Address (rl3): 89.222.229.104
    Jul 23 15:07:48 dhclient: New Subnet Mask (rl3): 255.255.255.0
    Jul 23 15:07:48 dhclient: New Broadcast Address (rl3): 89.222.229.255
    Jul 23 15:07:48 dhclient: New Routers (rl3): 89.222.229.254
    Jul 23 15:07:49 dhclient: New Routers (rl3): 89.222.229.254
    Jul 23 15:08:00 dhclient: Deleting old routes
    Jul 23 15:08:00 dhclient[62947]: bound: renewal in 95235 seconds.
    Jul 23 18:04:08 check_reload_status: Linkup starting rl3
    Jul 23 18:04:08 kernel: rl3: link state changed to DOWN
    Jul 23 18:04:13 php: : DEVD Ethernet detached event for wan
    Jul 23 18:04:13 dhclient[63213]: connection closed
    Jul 23 18:04:13 dhclient[63213]: connection closed
    Jul 23 18:04:13 dhclient[63213]: exiting.
    Jul 23 18:04:13 dhclient[63213]: exiting.
    Jul 23 18:04:24 check_reload_status: Linkup starting rl3
    Jul 23 18:04:24 kernel: rl3: link state changed to UP
    Jul 23 18:04:30 php: : DEVD Ethernet attached event for wan
    Jul 23 18:04:30 php: : HOTPLUG: Configuring interface wan
    Jul 23 18:04:30 dhclient: PREINIT
    Jul 23 18:04:30 dhclient[61796]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 18:04:32 dhclient[61796]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 18:04:37 dhclient[61796]: DHCPREQUEST on rl3 to 255.255.255.255 port 67
    Jul 23 18:04:37 dhclient[61796]: DHCPACK from 10.228.106.33
    Jul 23 18:04:37 dhclient: REBOOT
    Jul 23 18:04:37 dhclient: Starting add_new_address()
    Jul 23 18:04:37 dhclient: ifconfig rl3 inet 89.222.229.104 netmask 255.255.255.0 broadcast 89.222.229.255
    Jul 23 18:04:37 dhclient: New IP Address (rl3): 89.222.229.104
    Jul 23 18:04:37 dhclient: New Subnet Mask (rl3): 255.255.255.0
    Jul 23 18:04:37 dhclient: New Broadcast Address (rl3): 89.222.229.255
    Jul 23 18:04:37 dhclient: New Routers (rl3): 89.222.229.254
    Jul 23 18:04:37 dhclient: Adding new routes to interface: rl3
    Jul 23 18:04:37 dhclient: /sbin/route add default 89.222.229.254
    Jul 23 18:04:37 dhclient: Creating resolv.conf
    Jul 23 18:04:37 check_reload_status: rc.newwanip starting rl3
    Jul 23 18:04:37 dhclient[61796]: bound to 89.222.229.104 – renewal in 145290 seconds.
    Jul 23 18:04:38 apinger: alarm canceled: WAN(89.222.229.254) *** down ***
    Jul 23 18:04:40 apinger: alarm canceled: WAN(89.222.229.254) *** delay ***
    Jul 23 18:04:43 php: : rc.newwanip: Informational is starting rl3.
    Jul 23 18:04:43 php: : rc.newwanip: on (IP address: 89.222.229.104) (interface: wan) (real interface: rl3).
    Jul 23 18:04:43 php: : ROUTING: setting default route to 89.222.229.254
    Jul 23 18:04:43 check_reload_status: Reloading filter
    Jul 23 18:04:43 check_reload_status: Reloading filter
    Jul 23 18:04:43 apinger: Exiting on signal 15.
    Jul 23 18:04:44 apinger: Starting Alarm Pinger, apinger(59635)
    Jul 23 18:04:47 dnsmasq[42916]: reading /etc/resolv.conf
    Jul 23 18:04:47 dnsmasq[42916]: using nameserver 89.222.231.1#53
    Jul 23 18:04:47 dnsmasq[42916]: using nameserver 89.222.228.2#53
    Jul 23 18:04:47 dnsmasq[42916]: using nameserver 89.222.231.1#53
    Jul 23 18:04:47 dnsmasq[42916]: using nameserver 89.222.228.2#53



  • А WAN динамический?
    И тоже карточка Realtek. Есть возможность хотя-бы временно что-нить другое ( типа Intel-а/3Com-а) поставить?

    По теме:
    http://forum.pfsense.org/index.php?action=search2


    http://forum.pfsense.org/index.php/topic,43161.msg223336.html#msg223336

    Там, кажется, известная ошибка, в которой интерфейс может застрять в петле велосипеде вверх и вниз. Это произойдет, если вы заставили одного из параметров интерфейса, а не использовать авто. Например скорость соединения или МАС-адрес.
    Возможно, это была ваша проблема?

    http://redmine.pfsense.org/issues/1572


    Вариант проблемы при включенном
    Enabling MAC spoofing on WAN Interface using DHCP


    У меня аналогичная проблема с этим так интересно, если это связано. Я бегу мое WAN интерфейса DHCP. Если попытаться изменить скорость и дуплекс или MTU, WAN интерфейс цикла вверх и вниз без остановки. Единственный способ вернуться к нормальной, это установить скорость и дуплекс ничем, кроме "по умолчанию". Кроме того, опция MTU должно быть совершенно пустой.



  • Друзья!
    Пока суть да дело, заработало!
    Произошло это после того когда я произвёл манипуляции, совершенно по другой теме.

    Подробней.

    1. В закладке System: General Setup была установлена галочка показанная на рисунке p1.jpg

    2. В закладке Interfaces: WAN была убрана галочка показанная на рисунке p2.jpg

    В логах появилась строка на запрос IP адреса. И WAN стал подниматься сам.
    Не понятно только, послужило ли именно это на решение вопроса или сия манипуляция вызвала перенастройку интерфейса.
    Также было замечено, что данная настройка влияет на ускорение  работы GUI в режиме OFF line (помню где то поднималась такая тема).

    Да WAN динамический.

    P.S. Не пойму как вставлять рисунок в тексте  :(





Locked