Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    Network problem with Intel 82580

    Scheduled Pinned Locked Moved Hardware
    17 Posts 2 Posters 8.8k Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • P
      pioupiou38
      last edited by

      Hi everyone,

      I've got a problem with pfSense 2.0.1 (based on FreeBSD 8.1) and my network cards (Intel I340 T2 with controller intel 82580).

      I've followed this topic http://forum.pfsense.org/index.php/topic,26592.msg140323.html to compile the drivers on a FreeBSD 8.1 and upload the file if_igb.ko on my pfSense server (and put this in /boot/kernel)
      I've added the line if_igb_load="YES" on my /boot/loader.conf and restarted my server.

      After booting, I've configured my interfaces (with Vlan and IP address) and restart again.

      Despite this manipulations, nothing work. When I ping an address on my network, I've got the message
      ping: sendto : host is down  (but in fact, my host is really UP)

      I don't understand why this is not working… Can you help me please?

      Thanks in advance

      (PS : sorry for my poor english I'm french  ;D)

      1 Reply Last reply Reply Quote 0
      • stephenw10S
        stephenw10 Netgate Administrator
        last edited by

        That thread is very old.
        The Intel drivers in pfSense 2.0.1 are in fact newer than FreeBSD 8.1. They may well support your hardware already.
        Usually if the drivers do not support your NICs you cannot assign interfaces to them. It appears that the drivers are recognising and attaching to the NICs if you have assigned them.

        I suspect this may be a different problem.

        Was there any difference between the stock driver and your compiled module?

        Are there any errors in the boot log or system log?

        Steve

        1 Reply Last reply Reply Quote 0
        • P
          pioupiou38
          last edited by

          Hi, thanks for the answer.

          That thread is very old.
          […]
          Was there any difference between the stock driver and your compiled module?

          I dont know differences between those two drivers. I thought it was a driver problem so after many searches I found this topic and try it.
          After that, I'd got errors

          pfSense kernel : link_elf_lookup_symbol: missing symbol hash table

          so I've desactivated this driver.

          Are there any errors in the boot log or system log?

          Nothing in the boot log (except for the "normally log" like the ACPI warning or the ipw_monitor)
          In the system log I've errors like this :

          pfSense kernel: pci0: <base peripheral=""> at device 16.1 (no driver attached)
          […]

          pfSense kernel: pci0: <base peripheral=""> at device 26.1 (no driver attached)

          pfSense kernel: ppc0 cannot reserve I/O port range

          pfSense kernel: atrtc0 warning couldn't map I/O

          Is it normal?

          I'm plugged on a Cisco 3750GS and I've desactivated the port-security and other thing potentialy able to block my server.
          I've try to configure vlan interface in both (server+switch) but I've always the same problem :
          When I want to ping out of my server, I've got this error :

          ping : sendto: Host is down

          I've desactivated the firewall too (with pfctl -d) but nothing more…

          I don't know what is the problem, I think I've configured my server and my switch correctly....

          Regards,

          Vincent

          1 Reply Last reply Reply Quote 0
          • stephenw10S
            stephenw10 Netgate Administrator
            last edited by

            The kernel link error implies some compile problem. As I said the Intel driver in pfSense has been updated so I would think some of dependencies may have been also. Resulting in your driver missing some stuff.

            The two pci devices to which no driver could be found are not normally a problem. They will result in 'none' devices you can see using 'pciconf -l'. I have some that are Intel i2c bridges and such, not important for pfSense.

            ppc0 is a parallel port device. You should disable this in the BIOS if you can. The fact that it can't reserve any input/output address space for it may indicate a problem.
            atrtc0 is the real time clock. That could be more of a problem. Does pfSense maintain the correct time across boots?

            If the box is recognising both interfaces in the card as igb0 and igb1 then it's almost certainly not a driver problem.
            Is the card seeing the ethernet connection? Please give the output of 'ifconfig'.
            If it's showing the connection as active with the correct media type then all is well and the ethernet negotiation has succeeded.
            How are you assigning IP addresses?

            I would suspect possibly a mismatched speed/duplex or connection blocked at the switch.

            Steve

            1 Reply Last reply Reply Quote 0
            • P
              pioupiou38
              last edited by

              Hi, (Sorry for the long answer ^^)

              Does pfSense maintain the correct time across boots?

              Yes, it has the same time as configured on the bios.

              How are you assigning IP addresses?

              I've got 10 interfaces, 2 Broadcom and 8 Intel. I've configured LAGG0 with igb0, 2, 4 and 6, LAGG1 with igb1, 3, ,5 and 7.
              Both lagg are configured with two vlan  : 10 and 1010 for the one and 20 and 1020 for the second.
              I've plugged the LAN output on the BCE0 (cause I'm sure it works ^^) and configred  its @IP to access on the webconfigurator to configure the LAGG and vlan.

              Here the output of the ifconfig

              
bce0: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
        options=c00b8 <vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso,linkstate>ether 34:40:b5:d4:24:70
        inet 172.17.1.251 netmask 0xffffff00 broadcast 172.17.1.255
        inet6 fe80::3640:b5ff:fed4:2470%bce0 prefixlen 64 scopeid 0x1
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
bce1: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
        options=c00b8 <vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso,linkstate>ether 34:40:b5:d4:24:72
        inet 10.1.0.1 netmask 0xfffffffc broadcast 10.1.0.3
        inet6 fe80::3640:b5ff:fed4:2472%bce1 prefixlen 64 scopeid 0x2
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
igb0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=1bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4>ether 90:e2:ba:1d:ad:ca
        inet6 fe80::92e2:baff:fe1d:adca%igb0 prefixlen 64 scopeid 0x3
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
igb1: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=1bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4>ether 90:e2:ba:1d:ad:cb
        inet6 fe80::92e2:baff:fe1d:adcb%igb1 prefixlen 64 scopeid 0x4
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
igb2: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=1bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4>ether 90:e2:ba:1d:ad:ca
        inet6 fe80::92e2:baff:fe1d:a976%igb2 prefixlen 64 scopeid 0x5
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
igb3: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=1bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4>ether 90:e2:ba:1d:ad:cb
        inet6 fe80::92e2:baff:fe1d:a977%igb3 prefixlen 64 scopeid 0x6
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
igb4: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=1bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4>ether 90:e2:ba:1d:ad:ca
        inet6 fe80::92e2:baff:fe1d:a934%igb4 prefixlen 64 scopeid 0x7
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
igb5: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=1bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4>ether 90:e2:ba:1d:ad:cb
        inet6 fe80::92e2:baff:fe1d:a935%igb5 prefixlen 64 scopeid 0x8
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
igb6: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=1bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4>ether 90:e2:ba:1d:ad:ca
        inet6 fe80::92e2:baff:fe17:9a34%igb6 prefixlen 64 scopeid 0x9
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
igb7: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=1bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4>ether 90:e2:ba:1d:ad:cb
        inet6 fe80::92e2:baff:fe17:9a35%igb7 prefixlen 64 scopeid 0xa
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect (1000baseT <full-duplex>)
        status: active
pflog0: flags=100 <promisc>metric 0 mtu 33664
pfsync0: flags=41 <up,running>metric 0 mtu 1460
        pfsync: syncdev: bce1 syncpeer: 10.1.0.2 maxupd: 128 syncok: 1
enc0: flags=0<> metric 0 mtu 1536
lo0: flags=8049 <up,loopback,running,multicast>metric 0 mtu 16384
        options=3 <rxcsum,txcsum>inet 127.0.0.1 netmask 0xff000000
        inet6 ::1 prefixlen 128
        inet6 fe80::1%lo0 prefixlen 64 scopeid 0xe
        nd6 options=3 <performnud,accept_rtadv>lagg0: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=1bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4>ether 90:e2:ba:1d:ad:ca
        inet6 fe80::92e2:baff:fe1d:adca%lagg0 prefixlen 64 scopeid 0xf
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect
        status: active
        laggproto failover
        laggport: igb6 flags=0<>
        laggport: igb4 flags=0<>
        laggport: igb2 flags=0<>
        laggport: igb0 flags=5 <master,active>lagg1: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=1bb <rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4>ether 90:e2:ba:1d:ad:cb
        inet6 fe80::92e2:baff:fe1d:adcb%lagg1 prefixlen 64 scopeid 0x10
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect
        status: active
        laggproto failover
        laggport: igb7 flags=0<>
        laggport: igb5 flags=0<>
        laggport: igb3 flags=0<>
        laggport: igb1 flags=5 <master,active>lagg0_vlan10: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=3 <rxcsum,txcsum>ether 90:e2:ba:1d:ad:ca
        inet6 fe80::3640:b5ff:fed4:2470%lagg0_vlan10 prefixlen 64 scopeid 0x11
        inet 192.168.1.251 netmask 0xffffff00 broadcast 192.168.1.255
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect
        status: active
        vlan: 10 parent interface: lagg0
lagg0_vlan1010: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
        options=3 <rxcsum,txcsum>ether 90:e2:ba:1d:ad:ca
        inet6 fe80::3640:b5ff:fed4:2470%lagg0_vlan1010 prefixlen 64 scopeid 0x12
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect
        status: active
        vlan: 1010 parent interface: lagg0
lagg1_vlan20: flags=8943 <up,broadcast,running,promisc,simplex,multicast>metric 0 mtu 1500
        options=3 <rxcsum,txcsum>ether 90:e2:ba:1d:ad:cb
        inet6 fe80::3640:b5ff:fed4:2470%lagg1_vlan20 prefixlen 64 scopeid 0x13
        inet 192.168.2.251 netmask 0xffffff00 broadcast 192.168.2.255
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect
        status: active
        vlan: 20 parent interface: lagg1
lagg1_vlan1020: flags=8843 <up,broadcast,running,simplex,multicast>metric 0 mtu 1500
        options=3 <rxcsum,txcsum>ether 90:e2:ba:1d:ad:cb
        inet6 fe80::3640:b5ff:fed4:2470%lagg1_vlan1020 prefixlen 64 scopeid 0x14
        inet 172.17.2.251 netmask 0xffffff00 broadcast 172.17.2.255
        nd6 options=3 <performnud,accept_rtadv>media: Ethernet autoselect
        status: active
        vlan: 1020 parent interface: lagg1
vip1: flags=49 <up,loopback,running>metric 0 mtu 1500
        inet 192.168.1.254 netmask 0xffffff00
        carp: MASTER vhid 1 advbase 1 advskew 0
vip2: flags=49 <up,loopback,running>metric 0 mtu 1500
        inet 192.168.2.254 netmask 0xffffff00
        carp: MASTER vhid 2 advbase 1 advskew 0</up,loopback,running></up,loopback,running></performnud,accept_rtadv></rxcsum,txcsum></up,broadcast,running,simplex,multicast></performnud,accept_rtadv></rxcsum,txcsum></up,broadcast,running,promisc,simplex,multicast></performnud,accept_rtadv></rxcsum,txcsum></up,broadcast,running,simplex,multicast></performnud,accept_rtadv></rxcsum,txcsum></up,broadcast,running,promisc,simplex,multicast></master,active></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4></up,broadcast,running,promisc,simplex,multicast></master,active></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4></up,broadcast,running,promisc,simplex,multicast></performnud,accept_rtadv></rxcsum,txcsum></up,loopback,running,multicast></up,running></promisc></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4></up,broadcast,running,promisc,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4></up,broadcast,running,promisc,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4></up,broadcast,running,promisc,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4></up,broadcast,running,promisc,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4></up,broadcast,running,promisc,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4></up,broadcast,running,promisc,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4></up,broadcast,running,promisc,simplex,multicast></full-duplex></performnud,accept_rtadv></rxcsum,txcsum,vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,tso4></up,broadcast,running,promisc,simplex,multicast></full-duplex></performnud,accept_rtadv></vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso,linkstate></up,broadcast,running,simplex,multicast></full-duplex></performnud,accept_rtadv></vlan_mtu,vlan_hwtagging,jumbo_mtu,vlan_hwcsum,vlan_hwtso,linkstate></up,broadcast,running,simplex,multicast>

              Here it's my boot log :

              
Nov 19 12:04:27 fw-int-01 kernel: Copyright (c) 1992-2010 The FreeBSD Project.
Nov 19 12:04:27 fw-int-01 kernel: Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
Nov 19 12:04:27 fw-int-01 kernel: The Regents of the University of California. All rights reserved.
Nov 19 12:04:27 fw-int-01 kernel: FreeBSD is a registered trademark of The FreeBSD Foundation.
Nov 19 12:04:27 fw-int-01 kernel: FreeBSD 8.1-RELEASE-p6 #0: Mon Dec 12 18:15:35 EST 2011
Nov 19 12:04:27 fw-int-01 kernel: root@FreeBSD_8.0_pfSense_2.0-AMD64.snaps.pfsense.org:/usr/obj./usr/pfSensesrc/src/sys/pfSense_SMP.8 amd64
Nov 19 12:04:27 fw-int-01 kernel: Timecounter "i8254" frequency 1193182 Hz quality 0
Nov 19 12:04:27 fw-int-01 kernel: CPU: Intel(R) Xeon(R) CPU           E5606  @ 2.13GHz (2133.42-MHz K8-class CPU)
Nov 19 12:04:27 fw-int-01 kernel: Origin = "GenuineIntel"  Id = 0x206c2  Family = 6  Model = 2c  Stepping = 2
Nov 19 12:04:27 fw-int-01 kernel: Features=0xbfebfbff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>Nov 19 12:04:27 fw-int-01 kernel: Features2=0x29ee3ff<sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,<b17>,DCA,SSE4.1,SSE4.2,POPCNT,AESNI>
Nov 19 12:04:27 fw-int-01 kernel: AMD Features=0x2c100800 <syscall,nx,page1gb,rdtscp,lm>Nov 19 12:04:27 fw-int-01 kernel: AMD Features2=0x1 <lahf>Nov 19 12:04:27 fw-int-01 kernel: TSC: P-state invariant
Nov 19 12:04:27 fw-int-01 kernel: real memory  = 17179869184 (16384 MB)
Nov 19 12:04:27 fw-int-01 kernel: avail memory = 16508887040 (15744 MB)
Nov 19 12:04:27 fw-int-01 kernel: ACPI APIC Table: <ibm   ="" thurley="">Nov 19 12:04:27 fw-int-01 kernel: FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
Nov 19 12:04:27 fw-int-01 kernel: FreeBSD/SMP: 2 package(s) x 1 core(s)
Nov 19 12:04:27 fw-int-01 kernel: cpu0 (BSP): APIC ID:  0
Nov 19 12:04:27 fw-int-01 kernel: cpu1 (AP): APIC ID: 32
Nov 19 12:04:27 fw-int-01 kernel: ACPI Warning: Invalid length for Pm1aControlBlock: 32, using default 16 (20100331/tbfadt-707)
Nov 19 12:04:27 fw-int-01 kernel: ioapic0 <version 2.0="">irqs 0-23 on motherboard
Nov 19 12:04:27 fw-int-01 kernel: ioapic1 <version 2.0="">irqs 24-47 on motherboard
Nov 19 12:04:27 fw-int-01 kernel: netisr_init: forcing maxthreads to 1 and bindthreads to 0 for device polling
Nov 19 12:04:27 fw-int-01 kernel: wlan: mac acl policy registered
Nov 19 12:04:27 fw-int-01 kernel: ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Nov 19 12:04:27 fw-int-01 kernel: ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Nov 19 12:04:27 fw-int-01 kernel: module_register_init: MOD_LOAD (ipw_monitor_fw, 0xffffffff80470e10, 0) error 1
Nov 19 12:04:27 fw-int-01 kernel: wpi: You need to read the LICENSE file in /usr/share/doc/legal/intel_wpi/.
Nov 19 12:04:27 fw-int-01 kernel: wpi: If you agree with the license, set legal.intel_wpi.license_ack=1 in /boot/loader.conf.
Nov 19 12:04:27 fw-int-01 kernel: module_register_init: MOD_LOAD (wpi_fw, 0xffffffff806548d0, 0) error 1
Nov 19 12:04:27 fw-int-01 kernel: ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Nov 19 12:04:27 fw-int-01 kernel: ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Nov 19 12:04:27 fw-int-01 kernel: module_register_init: MOD_LOAD (ipw_bss_fw, 0xffffffff80470cd0, 0) error 1
Nov 19 12:04:27 fw-int-01 kernel: ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw/.
Nov 19 12:04:27 fw-int-01 kernel: ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
Nov 19 12:04:27 fw-int-01 kernel: module_register_init: MOD_LOAD (ipw_ibss_fw, 0xffffffff80470d70, 0) error 1
Nov 19 12:04:27 fw-int-01 kernel: kbd1 at kbdmux0
Nov 19 12:04:27 fw-int-01 kernel: cryptosoft0: <software crypto="">on motherboard
Nov 19 12:04:27 fw-int-01 kernel: padlock0: No ACE support.
Nov 19 12:04:27 fw-int-01 kernel: acpi0: <ibm thurley="">on motherboard
Nov 19 12:04:27 fw-int-01 kernel: acpi0: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: acpi0: Power Button (fixed)
Nov 19 12:04:27 fw-int-01 kernel: acpi_hpet0: <high precision="" event="" timer="">iomem 0xfed00000-0xfed003ff on acpi0
Nov 19 12:04:27 fw-int-01 kernel: Timecounter "HPET" frequency 14318180 Hz quality 900
Nov 19 12:04:27 fw-int-01 kernel: Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
Nov 19 12:04:27 fw-int-01 kernel: acpi_timer0: <24-bit timer at 3.579545MHz> port 0x588-0x58b on acpi0
Nov 19 12:04:27 fw-int-01 kernel: cpu0: <acpi cpu="">on acpi0
Nov 19 12:04:27 fw-int-01 kernel: cpu1: <acpi cpu="">on acpi0
Nov 19 12:04:27 fw-int-01 kernel: pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
Nov 19 12:04:27 fw-int-01 kernel: pci0: <acpi pci="" bus="">on pcib0
Nov 19 12:04:27 fw-int-01 kernel: pcib1: <acpi pci-pci="" bridge="">irq 28 at device 1.0 on pci0
Nov 19 12:04:27 fw-int-01 kernel: pci11: <acpi pci="" bus="">on pcib1
Nov 19 12:04:27 fw-int-01 kernel: bce0: <broadcom netxtreme="" ii="" bcm5709="" 1000base-t="" (c0)="">mem 0x92000000-0x93ffffff irq 28 at device 0.0 on pci11
Nov 19 12:04:27 fw-int-01 kernel: miibus0: <mii bus="">on bce0
Nov 19 12:04:27 fw-int-01 kernel: brgphy0: <bcm5709c 10="" 100="" 1000basetx="" phy="">PHY 1 on miibus0
Nov 19 12:04:27 fw-int-01 kernel: brgphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
Nov 19 12:04:27 fw-int-01 kernel: bce0: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: bce0: ASIC (0x57092003); Rev (C0); Bus (PCIe x2, 5Gbps); B/C (6.2.0); Flags (MSI|MFW); MFW (NCSI 2.0.11)
Nov 19 12:04:27 fw-int-01 kernel: bce1: <broadcom netxtreme="" ii="" bcm5709="" 1000base-t="" (c0)="">mem 0x94000000-0x95ffffff irq 40 at device 0.1 on pci11
Nov 19 12:04:27 fw-int-01 kernel: miibus1: <mii bus="">on bce1
Nov 19 12:04:27 fw-int-01 kernel: brgphy1: <bcm5709c 10="" 100="" 1000basetx="" phy="">PHY 1 on miibus1
Nov 19 12:04:27 fw-int-01 kernel: brgphy1:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-FDX, auto
Nov 19 12:04:27 fw-int-01 kernel: bce1: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: bce1: ASIC (0x57092003); Rev (C0); Bus (PCIe x2, 5Gbps); B/C (6.2.0); Flags (MSI|MFW); MFW (NCSI 2.0.11)
Nov 19 12:04:27 fw-int-01 kernel: pcib2: <pci-pci bridge="">irq 29 at device 2.0 on pci0
Nov 19 12:04:27 fw-int-01 kernel: pci16: <pci bus="">on pcib2
Nov 19 12:04:27 fw-int-01 kernel: pcib3: <acpi pci-pci="" bridge="">irq 24 at device 3.0 on pci0
Nov 19 12:04:27 fw-int-01 kernel: pci21: <acpi pci="" bus="">on pcib3
Nov 19 12:04:27 fw-int-01 kernel: igb0: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.2.3="">mem 0x98080000-0x980fffff,0x98104000-0x98107fff irq 24 at device 0.0 on pci21
Nov 19 12:04:27 fw-int-01 kernel: igb0: Using MSIX interrupts with 2 vectors
Nov 19 12:04:27 fw-int-01 kernel: igb0: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: igb0: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: igb1: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.2.3="">mem 0x98000000-0x9807ffff,0x98100000-0x98103fff irq 34 at device 0.1 on pci21
Nov 19 12:04:27 fw-int-01 kernel: igb1: Using MSIX interrupts with 2 vectors
Nov 19 12:04:27 fw-int-01 kernel: igb1: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: igb1: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: pcib4: <acpi pci-pci="" bridge="">irq 26 at device 5.0 on pci0
Nov 19 12:04:27 fw-int-01 kernel: pci26: <acpi pci="" bus="">on pcib4
Nov 19 12:04:27 fw-int-01 kernel: igb2: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.2.3="">mem 0x97e80000-0x97efffff,0x97f04000-0x97f07fff irq 26 at device 0.0 on pci26
Nov 19 12:04:27 fw-int-01 kernel: igb2: Using MSIX interrupts with 2 vectors
Nov 19 12:04:27 fw-int-01 kernel: igb2: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: igb2: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: igb3: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.2.3="">mem 0x97e00000-0x97e7ffff,0x97f00000-0x97f03fff irq 25 at device 0.1 on pci26
Nov 19 12:04:27 fw-int-01 kernel: igb3: Using MSIX interrupts with 2 vectors
Nov 19 12:04:27 fw-int-01 kernel: igb3: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: igb3: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: pcib5: <acpi pci-pci="" bridge="">irq 30 at device 7.0 on pci0
Nov 19 12:04:27 fw-int-01 kernel: pci31: <acpi pci="" bus="">on pcib5
Nov 19 12:04:27 fw-int-01 kernel: igb4: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.2.3="">mem 0x97c80000-0x97cfffff,0x97d04000-0x97d07fff irq 30 at device 0.0 on pci31
Nov 19 12:04:27 fw-int-01 kernel: igb4: Using MSIX interrupts with 2 vectors
Nov 19 12:04:27 fw-int-01 kernel: igb4: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: igb4: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: igb5: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.2.3="">mem 0x97c00000-0x97c7ffff,0x97d00000-0x97d03fff irq 37 at device 0.1 on pci31
Nov 19 12:04:27 fw-int-01 kernel: igb5: Using MSIX interrupts with 2 vectors
Nov 19 12:04:27 fw-int-01 kernel: igb5: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: igb5: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: pcib6: <acpi pci-pci="" bridge="">irq 32 at device 9.0 on pci0
Nov 19 12:04:27 fw-int-01 kernel: pci36: <acpi pci="" bus="">on pcib6
Nov 19 12:04:27 fw-int-01 kernel: igb6: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.2.3="">mem 0x97a80000-0x97afffff,0x97b04000-0x97b07fff irq 32 at device 0.0 on pci36
Nov 19 12:04:27 fw-int-01 kernel: igb6: Using MSIX interrupts with 2 vectors
Nov 19 12:04:27 fw-int-01 kernel: igb6: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: igb6: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: igb7: <intel(r) 1000="" pro="" network="" connection="" version="" -="" 2.2.3="">mem 0x97a00000-0x97a7ffff,0x97b00000-0x97b03fff irq 42 at device 0.1 on pci36
Nov 19 12:04:27 fw-int-01 kernel: igb7: Using MSIX interrupts with 2 vectors
Nov 19 12:04:27 fw-int-01 kernel: igb7: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: igb7: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral,="" interrupt="" controller=""> at device 16.0 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral,="" interrupt="" controller=""> at device 16.1 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral,="" interrupt="" controller=""> at device 17.0 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral,="" interrupt="" controller=""> at device 17.1 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral,="" interrupt="" controller=""> at device 20.0 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral,="" interrupt="" controller=""> at device 20.1 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral,="" interrupt="" controller=""> at device 20.2 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral,="" interrupt="" controller=""> at device 20.3 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral=""> at device 22.0 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral=""> at device 22.1 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral=""> at device 22.2 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral=""> at device 22.3 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral=""> at device 22.4 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral=""> at device 22.5 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral=""> at device 22.6 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: pci0: <base peripheral=""> at device 22.7 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: uhci0: <intel 82801ji="" (ich10)="" usb="" controller="" usb-d="">port 0x20a0-0x20bf irq 17 at device 26.0 on pci0
Nov 19 12:04:27 fw-int-01 kernel: uhci0: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: usbus0: <intel 82801ji="" (ich10)="" usb="" controller="" usb-d="">on uhci0
Nov 19 12:04:27 fw-int-01 kernel: uhci1: <intel 82801ji="" (ich10)="" usb="" controller="" usb-e="">port 0x2080-0x209f irq 18 at device 26.1 on pci0
Nov 19 12:04:27 fw-int-01 kernel: uhci1: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: usbus1: <intel 82801ji="" (ich10)="" usb="" controller="" usb-e="">on uhci1
Nov 19 12:04:27 fw-int-01 kernel: ehci0: <intel 82801ji="" (ich10)="" usb="" 2.0="" controller="" usb-b="">mem 0x98221000-0x982213ff irq 19 at device 26.7 on pci0
Nov 19 12:04:27 fw-int-01 kernel: ehci0: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: usbus2: EHCI version 1.0
Nov 19 12:04:27 fw-int-01 kernel: usbus2: <intel 82801ji="" (ich10)="" usb="" 2.0="" controller="" usb-b="">on ehci0
Nov 19 12:04:27 fw-int-01 kernel: pcib7: <acpi pci-pci="" bridge="">irq 16 at device 28.0 on pci0
Nov 19 12:04:27 fw-int-01 kernel: pci1: <acpi pci="" bus="">on pcib7
Nov 19 12:04:27 fw-int-01 kernel: mfi0: <lsi megasas="" gen2="">port 0x1000-0x10ff mem 0x97940000-0x97943fff,0x97900000-0x9793ffff irq 16 at device 0.0 on pci1
Nov 19 12:04:27 fw-int-01 kernel: mfi0: Megaraid SAS driver Ver 3.00
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1179 (406637984s/0x0020/info) - Shutdown command received from host
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1180 (boot + 64s/0x0020/info) - Firmware initialization started (PCI ID 0079/1000/03c7/1014)
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1181 (boot + 64s/0x0020/info) - Firmware version 2.130.353-1663
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1182 (boot + 65s/0x0008/WARN) - Battery Not Present
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1183 (boot + 65s/0x0020/info) - Package version 12.12.0-0111
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1184 (boot + 65s/0x0020/info) - Board Revision 80C
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1185 (boot + 84s/0x0002/info) - Inserted: PD 08(e0xff/s1)
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1186 (boot + 84s/0x0002/info) - Inserted: PD 08(e0xff/s1) Info: enclPd=ffff, scsiType=0, portMap=00, sasAddr=5000c50048165ad5,0000000000000000
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1187 (boot + 84s/0x0002/info) - PD 08(e0xff/s1) FRU is 42D0633
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1188 (boot + 84s/0x0002/info) - Inserted: PD 09(e0xff/s0)
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1189 (boot + 84s/0x0002/info) - Inserted: PD 09(e0xff/s0) Info: enclPd=ffff, scsiType=0, portMap=01, sasAddr=5000c50048167fd5,0000000000000000
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1190 (boot + 84s/0x0002/info) - PD 09(e0xff/s0) FRU is 42D0633
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1191 (boot + 84s/0x0008/WARN) - BBU disabled; changing WB virtual disks to WT, Forced WB VDs are not affected
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1192 (406638079s/0x0020/info) - Time established as 11/19/12 11:01:19; (85 seconds since power on)
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1193 (406638143s/0x0020/info) - Time established as 11/19/12 11:02:23; (149 seconds since power on)
Nov 19 12:04:27 fw-int-01 kernel: mfi0: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: pcib8: <pci-pci bridge="">irq 16 at device 28.4 on pci0
Nov 19 12:04:27 fw-int-01 kernel: pci6: <pci bus="">on pcib8
Nov 19 12:04:27 fw-int-01 kernel: pcib9: <pci-pci bridge="">irq 16 at device 0.0 on pci6
Nov 19 12:04:27 fw-int-01 kernel: pci7: <pci bus="">on pcib9
Nov 19 12:04:27 fw-int-01 kernel: vgapci0: <vga-compatible display="">mem 0x96000000-0x96ffffff,0x97800000-0x97803fff,0x97000000-0x977fffff irq 16 at device 0.0 on pci7
Nov 19 12:04:27 fw-int-01 kernel: uhci2: <intel 82801ji="" (ich10)="" usb="" controller="" usb-a="">port 0x2060-0x207f irq 17 at device 29.0 on pci0
Nov 19 12:04:27 fw-int-01 kernel: uhci2: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: usbus3: <intel 82801ji="" (ich10)="" usb="" controller="" usb-a="">on uhci2
Nov 19 12:04:27 fw-int-01 kernel: uhci3: <intel 82801ji="" (ich10)="" usb="" controller="" usb-b="">port 0x2040-0x205f irq 18 at device 29.1 on pci0
Nov 19 12:04:27 fw-int-01 kernel: uhci3: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: usbus4: <intel 82801ji="" (ich10)="" usb="" controller="" usb-b="">on uhci3
Nov 19 12:04:27 fw-int-01 kernel: uhci4: <intel 82801ji="" (ich10)="" usb="" controller="" usb-c="">port 0x2020-0x203f irq 19 at device 29.2 on pci0
Nov 19 12:04:27 fw-int-01 kernel: uhci4: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: usbus5: <intel 82801ji="" (ich10)="" usb="" controller="" usb-c="">on uhci4
Nov 19 12:04:27 fw-int-01 kernel: ehci1: <intel 82801ji="" (ich10)="" usb="" 2.0="" controller="" usb-a="">mem 0x98220000-0x982203ff irq 17 at device 29.7 on pci0
Nov 19 12:04:27 fw-int-01 kernel: ehci1: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: usbus6: EHCI version 1.0
Nov 19 12:04:27 fw-int-01 kernel: usbus6: <intel 82801ji="" (ich10)="" usb="" 2.0="" controller="" usb-a="">on ehci1
Nov 19 12:04:27 fw-int-01 kernel: pcib10: <pci-pci bridge="">at device 30.0 on pci0
Nov 19 12:04:27 fw-int-01 kernel: pci41: <pci bus="">on pcib10
Nov 19 12:04:27 fw-int-01 kernel: isab0: <pci-isa bridge="">at device 31.0 on pci0
Nov 19 12:04:27 fw-int-01 kernel: isa0: <isa bus="">on isab0
Nov 19 12:04:27 fw-int-01 kernel: atapci0: <intel ich10="" sata300="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0x20f0-0x20ff,0x20e0-0x20ef irq 16 at device 31.2 on pci0
Nov 19 12:04:27 fw-int-01 kernel: ata0: <ata 0="" channel="">on atapci0
Nov 19 12:04:27 fw-int-01 kernel: ata0: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: ata1: <ata 1="" channel="">on atapci0
Nov 19 12:04:27 fw-int-01 kernel: ata1: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)
Nov 19 12:04:27 fw-int-01 kernel: atapci1: <intel ich10="" sata300="" controller="">port 0x2108-0x210f,0x2124-0x2127,0x2100-0x2107,0x2120-0x2123,0x20d0-0x20df,0x20c0-0x20cf irq 21 at device 31.5 on pci0
Nov 19 12:04:27 fw-int-01 kernel: atapci1: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: ata2: <ata 0="" channel="">on atapci1
Nov 19 12:04:27 fw-int-01 kernel: ata2: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: ata3: <ata 1="" channel="">on atapci1
Nov 19 12:04:27 fw-int-01 kernel: ata3: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: atrtc0: <at realtime="" clock="">port 0x70-0x77 irq 8 on acpi0
Nov 19 12:04:27 fw-int-01 kernel: atrtc0: Warning: Couldn't map I/O.
Nov 19 12:04:27 fw-int-01 kernel: orm0: <isa option="" rom="">at iomem 0xc0000-0xc7fff on isa0
Nov 19 12:04:27 fw-int-01 kernel: sc0: <system console="">at flags 0x100 on isa0
Nov 19 12:04:27 fw-int-01 kernel: sc0: VGA <16 virtual consoles, flags=0x300>
Nov 19 12:04:27 fw-int-01 kernel: vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
Nov 19 12:04:27 fw-int-01 kernel: atkbdc0: <keyboard controller="" (i8042)="">at port 0x60,0x64 on isa0
Nov 19 12:04:27 fw-int-01 kernel: atkbd0: <at keyboard="">irq 1 on atkbdc0
Nov 19 12:04:27 fw-int-01 kernel: kbd0 at atkbd0
Nov 19 12:04:27 fw-int-01 kernel: atkbd0: [GIANT-LOCKED]
Nov 19 12:04:27 fw-int-01 kernel: atkbd0: [ITHREAD]
Nov 19 12:04:27 fw-int-01 kernel: ppc0: cannot reserve I/O port range
Nov 19 12:04:27 fw-int-01 kernel: est0: <enhanced speedstep="" frequency="" control="">on cpu0
Nov 19 12:04:27 fw-int-01 kernel: p4tcc0: <cpu frequency="" thermal="" control="">on cpu0
Nov 19 12:04:27 fw-int-01 kernel: est1: <enhanced speedstep="" frequency="" control="">on cpu1
Nov 19 12:04:27 fw-int-01 kernel: est: CPU supports Enhanced Speedstep, but is not recognized.
Nov 19 12:04:27 fw-int-01 kernel: est: cpu_vendor GenuineIntel, msr 10
Nov 19 12:04:27 fw-int-01 kernel: device_attach: est1 attach returned 6
Nov 19 12:04:27 fw-int-01 kernel: p4tcc1: <cpu frequency="" thermal="" control="">on cpu1
Nov 19 12:04:27 fw-int-01 kernel: Timecounters tick every 1.000 msec
Nov 19 12:04:27 fw-int-01 kernel: IPsec: Initialized Security Association Processing.
Nov 19 12:04:27 fw-int-01 kernel: usbus0: 12Mbps Full Speed USB v1.0
Nov 19 12:04:27 fw-int-01 kernel: usbus1: 12Mbps Full Speed USB v1.0
Nov 19 12:04:27 fw-int-01 kernel: usbus2: 480Mbps High Speed USB v2.0
Nov 19 12:04:27 fw-int-01 kernel: usbus3: 12Mbps Full Speed USB v1.0
Nov 19 12:04:27 fw-int-01 kernel: usbus4: 12Mbps Full Speed USB v1.0
Nov 19 12:04:27 fw-int-01 kernel: usbus5: 12Mbps Full Speed USB v1.0
Nov 19 12:04:27 fw-int-01 kernel: usbus6: 480Mbps High Speed USB v2.0
Nov 19 12:04:27 fw-int-01 kernel: ugen0.1: <intel>at usbus0
Nov 19 12:04:27 fw-int-01 kernel: uhub0: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus0
Nov 19 12:04:27 fw-int-01 kernel: ugen1.1: <intel>at usbus1
Nov 19 12:04:27 fw-int-01 kernel: uhub1: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus1
Nov 19 12:04:27 fw-int-01 kernel: ugen2.1: <intel>at usbus2
Nov 19 12:04:27 fw-int-01 kernel: uhub2: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus2
Nov 19 12:04:27 fw-int-01 kernel: ugen3.1: <intel>at usbus3
Nov 19 12:04:27 fw-int-01 kernel: uhub3: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus3
Nov 19 12:04:27 fw-int-01 kernel: ugen4.1: <intel>at usbus4
Nov 19 12:04:27 fw-int-01 kernel: uhub4: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus4
Nov 19 12:04:27 fw-int-01 kernel: ugen5.1: <intel>at usbus5
Nov 19 12:04:27 fw-int-01 kernel: uhub5: <intel 1="" 9="" uhci="" root="" hub,="" class="" 0,="" rev="" 1.00="" 1.00,="" addr="">on usbus5
Nov 19 12:04:27 fw-int-01 kernel: ugen6.1: <intel>at usbus6
Nov 19 12:04:27 fw-int-01 kernel: uhub6: <intel 1="" 9="" ehci="" root="" hub,="" class="" 0,="" rev="" 2.00="" 1.00,="" addr="">on usbus6
Nov 19 12:04:27 fw-int-01 kernel: uhub0: 2 ports with 2 removable, self powered
Nov 19 12:04:27 fw-int-01 kernel: uhub1: 2 ports with 2 removable, self powered
Nov 19 12:04:27 fw-int-01 kernel: uhub3: 2 ports with 2 removable, self powered
Nov 19 12:04:27 fw-int-01 kernel: uhub4: 2 ports with 2 removable, self powered
Nov 19 12:04:27 fw-int-01 kernel: uhub5: 2 ports with 2 removable, self powered
Nov 19 12:04:27 fw-int-01 kernel: acd0: DVDR <ibm sata="" device="" 81y3661="" sa80="">at ata0-master UDMA100 SATA 1.5Gb/s
Nov 19 12:04:27 fw-int-01 kernel: mfi0: 1194 (406638201s/0x0020/info) - Host driver is loaded and operational
Nov 19 12:04:27 fw-int-01 kernel: mfid0: <mfi logical="" disk="">on mfi0
Nov 19 12:04:27 fw-int-01 kernel: mfid0: 139236MB (285155328 sectors) RAID volume '' is optimal
Nov 19 12:04:27 fw-int-01 kernel: SMP: AP CPU #1 Launched!
Nov 19 12:04:27 fw-int-01 kernel: Root mount waiting for: usbus6 usbus2
Nov 19 12:04:27 fw-int-01 kernel: uhub2: 6 ports with 6 removable, self powered
Nov 19 12:04:27 fw-int-01 kernel: uhub6: 6 ports with 6 removable, self powered
Nov 19 12:04:27 fw-int-01 kernel: Trying to mount root from ufs:/dev/mfid0s1a
Nov 19 12:04:27 fw-int-01 kernel: ugen3.2: <ibm>at usbus3
Nov 19 12:04:27 fw-int-01 kernel: ugen5.2: <motorola>at usbus5
Nov 19 12:04:27 fw-int-01 kernel: ukbd0: <keyboard>on usbus5
Nov 19 12:04:27 fw-int-01 kernel: kbd2 at ukbd0
Nov 19 12:04:27 fw-int-01 kernel: ums0: <mouse>on usbus5
Nov 19 12:04:27 fw-int-01 kernel: ums0: 5 buttons and [XYZ] coordinates ID=0
Nov 19 12:04:27 fw-int-01 kernel: pflog0: promiscuous mode enabled
Nov 19 12:04:28 fw-int-01 apinger: Starting Alarm Pinger, apinger(27402)
Nov 19 12:04:30 fw-int-01 php: : ROUTING: setting default route to 192.168.1.254
Nov 19 12:04:30 fw-int-01 check_reload_status: Updating all dyndns
Nov 19 12:04:30 fw-int-01 dnsmasq[37363]: started, version 2.55 cachesize 10000
Nov 19 12:04:30 fw-int-01 dnsmasq[37363]: compile time options: IPv6 GNU-getopt no-DBus I18N DHCP TFTP
Nov 19 12:04:30 fw-int-01 dnsmasq[37363]: reading /etc/resolv.conf
Nov 19 12:04:30 fw-int-01 dnsmasq[37363]: using nameserver 172.17.1.2#53
Nov 19 12:04:30 fw-int-01 dnsmasq[37363]: using nameserver 172.17.1.1#53
Nov 19 12:04:30 fw-int-01 dnsmasq[37363]: ignoring nameserver 127.0.0.1 - local interface
Nov 19 12:04:30 fw-int-01 dnsmasq[37363]: ignoring nameserver 127.0.0.1 - local interface
Nov 19 12:04:30 fw-int-01 dnsmasq[37363]: read /etc/hosts - 2 addresses
Nov 19 12:04:38 fw-int-01 apinger: ALARM: WANGW(192.168.1.254)  *** down ***
Nov 19 12:04:45 fw-int-01 php: : OpenNTPD is starting up.
Nov 19 12:04:48 fw-int-01 check_reload_status: Restarting ipsec tunnels
Nov 19 12:04:48 fw-int-01 check_reload_status: Reloading filter
Nov 19 12:04:50 fw-int-01 php: : Creating rrd update script
Nov 19 12:04:50 fw-int-01 php: : Restarting/Starting all packages.
Nov 19 12:04:53 fw-int-01 php: : IPSEC: One or more IPsec tunnel endpoints has changed its IP. Refreshing.
Nov 19 12:04:55 fw-int-01 check_reload_status: Reloading filter
Nov 19 12:05:28 fw-int-01 apinger: Error while feeding rrdtool: Broken pipe
Nov 19 12:05:53 fw-int-01 check_reload_status: Syncing firewall
Nov 19 12:05:58 fw-int-01 php: : Beginning XMLRPC sync to http://10.1.0.2:80.
Nov 19 12:05:58 fw-int-01 php: : XMLRPC sync successfully completed with http://10.1.0.2:80.
Nov 19 12:06:01 fw-int-01 php: : Filter sync successfully completed with http://10.1.0.2:80.
Nov 19 12:06:28 fw-int-01 apinger: /usr/local/bin/rrdtool respawning too fast, waiting 300s.
Nov 19 12:10:59 fw-int-01 sshd[15596]: Accepted keyboard-interactive/pam for root from 172.17.1.250 port 2546 ssh2
Nov 19 12:10:59 fw-int-01 sshlockout[43802]: sshlockout/webConfigurator v3.0 starting up</mouse></keyboard></motorola></ibm></mfi></ibm></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></intel></cpu></enhanced></cpu></enhanced></at></keyboard></generic></system></isa></at></ata></ata></intel></serial></ata></ata></intel></isa></pci-isa></pci></pci-pci></intel></intel></intel></intel></intel></intel></intel></intel></vga-compatible></pci></pci-pci></pci></pci-pci></lsi></acpi></acpi></intel></intel></intel></intel></intel></intel></intel(r)></intel(r)></acpi></acpi></intel(r)></intel(r)></acpi></acpi></intel(r)></intel(r)></acpi></acpi></intel(r)></intel(r)></acpi></acpi></pci></pci-pci></bcm5709c></mii></broadcom></bcm5709c></mii></broadcom></acpi></acpi></acpi></acpi></acpi></acpi></high></ibm></software></version></version></ibm ></lahf></syscall,nx,page1gb,rdtscp,lm></sse3,pclmulqdq,dtes64,mon,ds_cpl,vmx,smx,est,tm2,ssse3,cx16,xtpr,pdcm,<b17></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,apic,sep,mtrr,pge,mca,cmov,pat,pse36,clflush,dts,acpi,mmx,fxsr,sse,sse2,ss,htt,tm,pbe>

              Regards,

              Vincent

              1 Reply Last reply Reply Quote 0
              • stephenw10S
                stephenw10 Netgate Administrator
                last edited by

                Woh! Ok, a relatively complex setup.  ;)
                With that many interfaces and especially because you're using mutliport cards have you read/done this:
                http://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards

                I notice that one of your lagg groups has an IP directly and other one doesn't. Usually you do not want the VLAN host interface (in this case your lagg1) to have an IP.

                Are you using static IPs throughout?

                Which NICs are not working? Have you just added the I340 to a previously working setup?

                With setup like this is could be failing at any stage, without going through it step by step it's hard to say.  :-\

                I recommend disabling all NIC hardware features, especially hardware VLAN tagging. If you have a mix of cards in each lagg they may have different features resulting in unpredictable behavior. You can always re-enable them later once the underlying cause is found.

                Steve

                1 Reply Last reply Reply Quote 0
                • P
                  pioupiou38
                  last edited by

                  Thanks for the link, I'd read this before posting this topic and added those two lines to my /boot/local.conf.local "kern.ipc.nmbclusters="131072"
                  hw.igb.num_queues=1".

                  I notice that one of your lagg groups has an IP directly and other one doesn't. Usually you do not want the VLAN host interface (in this case your lagg1) to have an IP.
                  Are you using static IPs throughout?

                  Yes it's because I'm not using my LAGG1 yet. It corresponds to my LAN network and I decided to plug a direct cable between my switch and my server on the interface bce0 (broadcom) to have the webconfigurator and the SSH access. I plan to integrate this lagg when I'll be sure Intel's interfaces works correctly.
                  For the other interfaces, I'm using only static IPs, not DHCP.

                  Which NICs are not working? Have you just added the I340 to a previously working setup?

                  There are only Intel's NICs which don't work.
                  The I340 where already plugged into the server when I received it. I haven't install another OS on the server yet to test if it's the Intel's cards which don't work, if it's a freeBsd compatibility/configuration problem or a switch problem. I'll install a Debian on the second server to test it this afternoon.

                  If you have a mix of cards in each lagg they may have different features resulting in unpredictable behavior

                  Nop, I'm only use Intel's NICs for the LAGG (ideally, I'll have 4 port for a frontend, 4 port for a backend [the 8 Intel ports) and the 2 broadcom port for the pfsync link between my two firewall).

                  Thanks for your advance, I'll restart all from the beginning (again ^^). If I find the solution, I'll post it.

                  By the way, if anyone have an idea, don't hesitate to post.

                  Regards,

                  Vincent

                  1 Reply Last reply Reply Quote 0
                  • stephenw10S
                    stephenw10 Netgate Administrator
                    last edited by

                    Just to confirm then all your igb NICs are Intel I340 cards?

                    I do remember reading about some people having problems with VLAN on lagg. Probably best to have a good look through the forum.

                    The way to approach a problem like this is to implement it one step at a time. For example. Start off by assigning each NIC as a seperate interface. Check you can connect correctly to each one.
                    Then re-assign two of them as a lagg group. Check you can connect to it (with the appropriate switch config).
                    Assign all the NICs to the two lagg groups. Check you can connect to each one.
                    Then try adding VLANs into the mix and check again.
                    It will soon be obvious which stage is causing the problem.

                    Steve

                    1 Reply Last reply Reply Quote 0
                    • P
                      pioupiou38
                      last edited by

                      Hi,

                      Yes I confirm that my cards are Intel I-340 T2 (dual port) with controller intel 82580.

                      I tried to plug a computer on one intel port (igb1), without vlan and it works.
                      I can ping both sides. (the server and the computer).
                      When I try with vlan, it doesn't work. When I configure my switch without trunk but with vlan, it's the same thing, ping command returns to me Host is down…

                      I think it's a problem vlan not supporting by the card. I continue my investigation around the world (it could be a good name for a song by the way ^^)

                      1 Reply Last reply Reply Quote 0
                      • P
                        pioupiou38
                        last edited by

                        After reinstall pfSense on my two firwall and debugging switch part and network part, it works.

                        I think it was a switch's configuration trunk problem. I tested without vlan and lagg and add fonctionality progressively.

                        I have a last problem now. My configuration don't allow IP forwarding between two of my network configured. I've try many things but nothing works… I think it's a NAT problem but I can't determinate how can I resolve it...

                        1 Reply Last reply Reply Quote 0
                        • stephenw10S
                          stephenw10 Netgate Administrator
                          last edited by

                          Ah OK.
                          So in terms of actual addressable interfaces you have 4 VLAN interfaces (10,1010,20 and 1020) and LAN?
                          What are you wanting to happen between each interface in terms of routing or NAT?

                          Steve

                          1 Reply Last reply Reply Quote 0
                          • P
                            pioupiou38
                            last edited by

                            you have 4 VLAN interfaces (10,1010,20 and 1020) and LAN?

                            Yes it's true.
                            The VLAN 10 is for the production network of a frontend (where the client come from Internet), the VLAN 20 is for the production network of the backend (for exemple my Apache come from the frontend to access to the storage in backend). So I must have an IP forwarding between those two zone.

                            VLANs 1010 and 1020 are the administration network for the two zone. (I must have IP forwarding between those too)

                            I've made 4 VIPs in CARP mode (to have redundancy between my two firewall like it's explain on the doc and on the official site), one in each VLAN. Those VIPs will be gateway for client in each VLAN.

                            At this moment, from a private network connected to the frontend, I can access to the 10 and 1010 VLANs.
                            I add route to my VLAN 20 and 1020 like that

                            route add -net 192.168.2.0/24 192.168.1.254

                            where 192.168.1.254 is my VLAN 10 VIP.

                            I can access to my two VIP in VLAN20 and VLAN1020 but I can't go further.
                            I've leave the Outbound NAT in automatic mode and the other NAT parameter to default configuration.

                            Regards,

                            Vincent

                            1 Reply Last reply Reply Quote 0
                            • stephenw10S
                              stephenw10 Netgate Administrator
                              last edited by

                              Hmm, I think we are going to need a diagram here. I'm confused.  :-\

                              You should not need to add a route between the VLANs as long as clients on those subnets are using the pfSense box as a gateway. pfSense will route by default as long as you have firewall rules in place to allow it. With NAT set to auto NAT will take place beween interfaces that have a gateway set (which are treated as a WAN) and those that don't (LANs).

                              If you are using CARP which interface is pfsync using?

                              Steve

                              1 Reply Last reply Reply Quote 0
                              • P
                                pioupiou38
                                last edited by

                                Hi,

                                I made this diagram to help you to understand my architecture (in attachement).

                                If you are using CARP which interface is pfsync using?

                                I'm using the two broadcom NIC on a LAGG failover for pfsync.

                                The 8 other Intel NIC (named 'igb') are used for my backend and frontend. (4 on each part) on two lagg with two vlans on each lagg.
                                For the pfSense 01 : LAGG0 contained igb1+3+5+7 and is connected to the frontend (IP 192.168.1.1)
                                LAGG1 contained igb0+2+4+6 and is connected to the backend (IP 192.168.2.1)
                                LAGG2 contained bce0+1 and is used for pfsync (10.1.0.1)

                                For the pfSense 01 : LAGG0 : igb0+2+4+6 : frontend (192.168.1.2)
                                LAGG1 : igb1+3+5+7 : backend (192.168.2.2)
                                LAGG2 : bce0+1 : pfsync (10.1.0.2)

                                From my client (a network connected to the frontend by a gateway) I can ping all my interfaces (on each network and each pfsense) and my VIP. But I can't go further the VIP backend to ping a switch or server in backend for example.

                                On each network, the rule is "allow all protocol from all source to all destination".

                                Dessin1.jpg
                                Dessin1.jpg_thumb

                                1 Reply Last reply Reply Quote 0
                                • stephenw10S
                                  stephenw10 Netgate Administrator
                                  last edited by

                                  Check the subnet mask on the pfSense interfaces. By default they are /32 when you first enable them. They obviously need to have a bigger mask such as /24. Normally it becomes obvious when you try to enable DHCP but if you're not using that it can be easy to overlook.

                                  Steve

                                  1 Reply Last reply Reply Quote 0
                                  • P
                                    pioupiou38
                                    last edited by

                                    I've verified and all my submask are on /24….

                                    1 Reply Last reply Reply Quote 0
                                    • P
                                      pioupiou38
                                      last edited by

                                      Hi,

                                      The problem is resolved.
                                      It was a problem of route missing in backend to access to frontend. Now, it's works.

                                      This post can be marked in "resolved".

                                      Thanks to Steve to your advices and your patience to help me.

                                      Regards

                                      Vincent

                                      1 Reply Last reply Reply Quote 0
                                      • First post
                                        Last post
                                      Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.