Lan unstable



  • I have just installed and configured pfsense and lan is unstable, every 2 min msn disconnect.

    Can anyone help me?

    Thanks



  • Probably, but without more information we're a little stuck ;) How about you start by telling us what version (number) of pfSense you installed and the hardware you installed it on - in particular the network cards.

    It would also help to know if this is known good hardware (including the network cable you're using) and what is in the pfSense system logs.



  • Server:
    CPU Type Intel(R) Core(TM)2 CPU 4300 @ 1.80GHz
    Version 2.0-RC1 (i386)
    built on Wed Mar 2 11:59:31 EST 2011
      WAN      (DHCP)
    10.1.1.2 100baseTX <full-duplex>LAN
    192.168.1.254 100baseTX <full-duplex>I guess both network cards are ok cause I tested them in other server running centOS.

    LAN > 192.168.1.254/24
    DHCP Server : 192.168.1.100 - 192.168.1.199
    Proxy server is enabled.

    System log:
    Mar 2 18:26:13 dhcpd: For info, please visit https://www.isc.org/software/dhcp/
    Mar 2 18:26:13 check_reload_status: updating dyndns lan
    Mar 2 18:26:15 apinger: Exiting on signal 15.
    Mar 2 18:26:16 check_reload_status: reloading filter
    Mar 2 18:26:16 apinger: Starting Alarm Pinger, apinger(29156)
    Mar 2 18:26:16 php: /interfaces.php: Creating rrd update script
    Mar 2 18:27:43 kernel: ste0: link state changed to DOWN
    Mar 2 18:27:43 check_reload_status: Linkup starting ste0
    Mar 2 18:27:43 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.1.254)
    Mar 2 18:27:48 kernel: ste0: link state changed to UP
    Mar 2 18:27:48 check_reload_status: Linkup starting ste0
    Mar 2 18:27:48 php: : Hotplug event detected for lan but ignoring since interface is configured with static IP (192.168.1.254)
    Mar 2 18:37:14 php: /index.php: webConfigurator authentication error for 'admin' from 192.168.1.103
    Mar 2 18:37:14 php: /index.php: webConfigurator authentication error for 'admin' from 192.168.1.103
    Mar 2 18:37:18 php: /index.php: webConfigurator authentication error for 'admin' from 192.168.1.103
    Mar 2 18:37:18 php: /index.php: webConfigurator authentication error for 'admin' from 192.168.1.103
    Mar 2 18:37:28 php: /index.php: webConfigurator authentication error for 'admin' from 192.168.1.103
    Mar 2 18:37:28 php: /index.php: webConfigurator authentication error for 'admin' from 192.168.1.103
    Mar 2 18:37:59 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.103
    Mar 2 18:37:59 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.103
    Mar 2 18:39:13 check_reload_status: syncing firewall
    Mar 2 18:39:25 check_reload_status: syncing firewall
    Mar 2 18:40:04 php: /pkg_edit.php: Reloading Squid for configuration sync
    Mar 2 18:40:04 check_reload_status: reloading filter
    Mar 2 18:40:04 check_reload_status: syncing firewall
    Mar 2 18:40:04 check_reload_status: reloading filter
    Mar 2 18:40:05 php: /pkg_edit.php: Reloading Squid for configuration sync
    Mar 2 18:40:05 check_reload_status: reloading filter
    Mar 2 18:40:21 php: /pkg_edit.php: Reloading Squid for configuration sync
    Mar 2 18:40:21 check_reload_status: reloading filter
    Mar 2 18:40:22 check_reload_status: syncing firewall
    Mar 2 18:40:22 check_reload_status: reloading filter
    Mar 2 18:40:23 php: /pkg_edit.php: Reloading Squid for configuration sync
    Mar 2 18:40:23 check_reload_status: reloading filter
    Mar 2 18:40:44 check_reload_status: syncing firewall
    Mar 2 18:40:48 check_reload_status: syncing firewall
    Mar 2 18:41:18 check_reload_status: syncing firewall
    Mar 2 18:41:21 check_reload_status: syncing firewall
    Mar 2 18:42:18 check_reload_status: syncing firewall
    Mar 2 18:42:22 check_reload_status: syncing firewall
    Mar 2 18:44:59 check_reload_status: syncing firewall
    Mar 2 18:45:01 check_reload_status: syncing firewall
    Mar 2 18:55:58 check_reload_status: syncing firewall
    Mar 2 18:55:59 check_reload_status: syncing firewall
    Mar 3 06:48:16 dhclient: RENEW
    Mar 3 06:48:16 dhclient: Creating resolv.conf
    Mar 3 09:57:22 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.102
    Mar 3 09:57:22 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.102
    Mar 3 10:03:24 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.102
    Mar 3 10:03:24 php: /index.php: Successful webConfigurator login for user 'admin' from 192.168.1.102

    Firewall log:

    Mar 3 10:10:14 LAN   192.168.1.117:49865   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49864   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49863   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49862   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49861   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49860   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49859   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49858   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49857   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49856   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49855   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49854   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49853   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49852   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49851   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49849   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49847   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49825   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49824   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49823   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49639   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49638   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49504   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49503   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49502   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49500   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49499   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49498   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49397   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49387   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49380   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49316   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49315   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49314   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49313   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49308   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49307   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49306   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49305   127.0.0.1:80 TCP:FA

    Mar 3 10:10:14 LAN   192.168.1.117:49304   127.0.0.1:80 TCP:FA

    Mar 3 10:10:28 LAN   192.168.1.117:49403   187.45.227.227:8080 TCP:FA

    Mar 3 10:10:28 LAN   192.168.1.117:49402   187.45.227.227:8080 TCP:FA

    Mar 3 10:10:28 LAN   192.168.1.117:49401   187.45.227.227:8080 TCP:FA

    Mar 3 10:10:28 LAN   192.168.1.117:49400   187.45.227.227:8080 TCP:FA

    Mar 3 10:10:28 LAN   192.168.1.117:49399   187.45.227.227:8080 TCP:FA

    Mar 3 10:10:28 LAN   192.168.1.117:49398   187.45.227.227:8080 TCP:FA

    Mar 3 10:10:39 WAN   112.200.178.59:52296   10.1.1.2:64324 UDP

    Mar 3 10:10:40 WAN   112.200.178.59:52296   10.1.1.2:64324 UDP

    Mar 3 10:10:40 WAN   112.200.178.59:52296   10.1.1.2:64324 UDP

    Mar 3 10:10:45 LAN   192.168.1.112:2107   72.14.204.100:443 TCP:RA

    DHCP log:

    Mar 3 10:02:26 dhcpd: DHCPINFORM from 192.168.1.121 via ste0
    Mar 3 10:02:26 dhcpd: DHCPACK to 192.168.1.121 (00:23:15:40:f1:14) via ste0
    Mar 3 10:02:28 dhcpd: DHCPINFORM from 192.168.1.115 via ste0
    Mar 3 10:02:28 dhcpd: DHCPACK to 192.168.1.115 (c4:17:fe:99:61:55) via ste0
    Mar 3 10:02:42 dhcpd: DHCPINFORM from 192.168.1.120 via ste0
    Mar 3 10:02:42 dhcpd: DHCPACK to 192.168.1.120 (00:24:2c:41:6f:02) via ste0
    Mar 3 10:02:53 dhcpd: DHCPINFORM from 192.168.1.112 via ste0
    Mar 3 10:02:53 dhcpd: DHCPACK to 192.168.1.112 (00:15:af:e9:9d:51) via ste0
    Mar 3 10:03:01 dhcpd: DHCPINFORM from 192.168.1.107 via ste0
    Mar 3 10:03:01 dhcpd: DHCPACK to 192.168.1.107 (00:17:c4:93:15:25) via ste0
    Mar 3 10:03:28 dhcpd: DHCPINFORM from 192.168.1.140 via ste0
    Mar 3 10:03:28 dhcpd: DHCPACK to 192.168.1.140 (00:23:14:9a:bd:84) via ste0
    Mar 3 10:04:17 dhcpd: DHCPDISCOVER from 00:24:21:cb:1b:7a via ste0
    Mar 3 10:04:18 dhcpd: DHCPOFFER on 192.168.1.122 to 00:24:21:cb:1b:7a (MFII) via ste0
    Mar 3 10:04:18 dhcpd: DHCPREQUEST for 192.168.1.122 (192.168.1.254) from 00:24:21:cb:1b:7a (MFII) via ste0
    Mar 3 10:04:18 dhcpd: DHCPACK on 192.168.1.122 to 00:24:21:cb:1b:7a (MFII) via ste0
    Mar 3 10:04:30 dhcpd: DHCPINFORM from 192.168.1.122 via ste0
    Mar 3 10:04:30 dhcpd: DHCPACK to 192.168.1.122 (00:24:21:cb:1b:7a) via ste0
    Mar 3 10:05:31 dhcpd: DHCPINFORM from 192.168.1.122 via ste0
    Mar 3 10:05:31 dhcpd: DHCPACK to 192.168.1.122 (00:24:21:cb:1b:7a) via ste0
    Mar 3 10:06:51 dhcpd: DHCPINFORM from 192.168.1.119 via ste0
    Mar 3 10:06:51 dhcpd: DHCPACK to 192.168.1.119 (00:21:00:41:c5:76) via ste0
    Mar 3 10:06:56 dhcpd: DHCPINFORM from 192.168.1.107 via ste0
    Mar 3 10:06:56 dhcpd: DHCPACK to 192.168.1.107 (00:17:c4:93:15:25) via ste0
    Mar 3 10:07:29 dhcpd: DHCPINFORM from 192.168.1.120 via ste0
    Mar 3 10:07:29 dhcpd: DHCPACK to 192.168.1.120 (00:24:2c:41:6f:02) via ste0
    Mar 3 10:07:55 dhcpd: DHCPINFORM from 192.168.1.115 via ste0
    Mar 3 10:07:55 dhcpd: DHCPACK to 192.168.1.115 (c4:17:fe:99:61:55) via ste0
    Mar 3 10:08:27 dhcpd: DHCPINFORM from 192.168.1.116 via ste0
    Mar 3 10:08:27 dhcpd: DHCPACK to 192.168.1.116 (00:23:4e:24:91:4d) via ste0
    Mar 3 10:08:57 dhcpd: DHCPINFORM from 192.168.1.140 via ste0
    Mar 3 10:08:57 dhcpd: DHCPACK to 192.168.1.140 (00:23:14:9a:bd:84) via ste0
    Mar 3 10:09:12 dhcpd: DHCPREQUEST for 192.168.1.110 from d8:5d:4c:88:b0:75 (usu-2316fe72d63) via ste0
    Mar 3 10:09:12 dhcpd: DHCPACK on 192.168.1.110 to d8:5d:4c:88:b0:75 (usu-2316fe72d63) via ste0
    Mar 3 10:09:47 dhcpd: DHCPINFORM from 192.168.1.122 via ste0
    Mar 3 10:09:47 dhcpd: DHCPACK to 192.168.1.122 (00:24:21:cb:1b:7a) via ste0
    Mar 3 10:09:52 dhcpd: DHCPREQUEST for 192.168.2.3 from 70:f1:a1:c6:d0:1a via ste0: wrong network.
    Mar 3 10:09:52 dhcpd: DHCPNAK on 192.168.2.3 to 70:f1:a1:c6:d0:1a via ste0
    Mar 3 10:09:52 dhcpd: DHCPDISCOVER from 70:f1:a1:c6:d0:1a via ste0
    Mar 3 10:09:53 dhcpd: DHCPOFFER on 192.168.1.123 to 70:f1:a1:c6:d0:1a (DQuile) via ste0
    Mar 3 10:09:53 dhcpd: DHCPREQUEST for 192.168.1.123 (192.168.1.254) from 70:f1:a1:c6:d0:1a (DQuile) via ste0
    Mar 3 10:09:53 dhcpd: DHCPACK on 192.168.1.123 to 70:f1:a1:c6:d0:1a (DQuile) via ste0
    Mar 3 10:09:54 dhcpd: DHCPINFORM from 192.168.1.102 via ste0
    Mar 3 10:09:54 dhcpd: DHCPACK to 192.168.1.102 (00:17:c4:93:08:b5) via ste0
    Mar 3 10:10:00 dhcpd: DHCPINFORM from 192.168.1.123 via ste0
    Mar 3 10:10:00 dhcpd: DHCPACK to 192.168.1.123 (70:f1:a1:c6:d0:1a) via ste0
    Mar 3 10:10:56 dhcpd: DHCPREQUEST for 192.168.1.140 from 00:23:14:9a:bd:84 (CaverMobile) via ste0
    Mar 3 10:10:56 dhcpd: DHCPACK on 192.168.1.140 to 00:23:14:9a:bd:84 (CaverMobile) via ste0
    Mar 3 10:11:14 dhcpd: DHCPINFORM from 192.168.1.140 via ste0
    Mar 3 10:11:14 dhcpd: DHCPACK to 192.168.1.140 (00:23:14:9a:bd:84) via ste0

    If you need any further information, let me know

    Thank you.</full-duplex></full-duplex>



  • I can't recognise any LAN instability in any of the logs you have posted.

    Is the issue that connections to MSN break at about two minute intervals? Do you get the same behaviour on other connections through the firewall? For example, if ssh to pfSense survives much longer than two minutes then your problem with MSN is unlikely to be LAN instability.



  • I've just checked that ssh still connected when msn disconnects.

    Probably it is a WAN problem.

    How can I check wan connection?

    Thank you



  • The logs would also show problems with the WAN interface. It could be your ISP or your ISP connected device (cable/ADSL modem etc)  - what about other connections to the Internet?


Log in to reply