Existe un registro de sucesos en pfsense????



  • ???  saludos, alguien conoce como ver los suscesos al arrancar y ejecutar el pfsense?  me explico, mis equipos con pfsense se guindan demasiado desde hace 1 semana, ahora existe algun archivo que yo pueda visualizar donde me indique que esta pasando, que error se esta generando? si es trafico, si es memoria, si es error de configuracion, o falla de algun hardware? para asi yo poder atacar el problema con claridad y no con simples conjeturas…  :-[

    gracias por sus comentarios.



  • ¡Hola!

    A parte de los logs que muestra la propia intefase web puedes recurrir, con la consola a;

    En la consola:

    dmesg | more

    te dirá cómo se reconoció tu hardware en el último arranque y los posibles cambios que se hayan producido (por ejemplo, desconexión/conexión de tarjetas de red).

    En /var/log tienes los distintos archivos de log. En FreeBSD estándar (pfSense es una distribución basada en FreeBSD 6.x) el archivo de mensajes principal es /var/log/messages. Por lo que parece, en pfSense es /var/log/system.log. En consecuencia, puedes hacer:

    cat /var/log/system.log | more

    Saludos,

    Josep Pujadas



  • :-) muchas gracias Sr. Bellera por su excelente respuesta…

    ejecute los comandos que usted me indico, obteniendose lo siguiente:

    dmesg |more
    Copyright (c) 1992-2006 The FreeBSD Project.
    Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
            The Regents of the University of California. All rights reserved.
    FreeBSD 6.1-RELEASE-p2 #0: Fri Jun 16 01:03:36 UTC 2006
        sullrich@builder.livebsd.com:/usr/obj.pfSense/usr/src/sys/pfSense.6
    Timecounter "i8254" frequency 1193182 Hz quality 0
    CPU: Intel Pentium III (864.56-MHz 686-class CPU)
      Origin = "GenuineIntel"  Id = 0x686  Stepping = 6
      Features=0x383f9ff<fpu,vme,de,pse,tsc,msr,pae,mce,cx8,sep,mtrr,pge,mca,cmov,pa<br>T,PSE36,MMX,FXSR,SSE>
    real memory  = 267042816 (254 MB)
    avail memory = 251609088 (239 MB)
    wlan: mac acl policy registered
    kbd1 at kbdmux0
    ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
    acpi0: <dell gx110 ="">on motherboard
    acpi0: Power Button (fixed)
    Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
    acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
    cpu0: <acpi cpu="">on acpi0
    pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
    pci0: <acpi pci="" bus="">on pcib0
    agp0: <intel 82810e="" (i810e="" gmch)="" svga="" controller="">mem 0xf8000000-0xfbffffff,0xff
    byte 1144Copyright (c) 1992-2006 The FreeBSD Project.
    Copyright (c) 1992-2006 The FreeBSD Project.
    Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
            The Regents of the University of California. All rights reserved.
    FreeBSD 6.1-RELEASE-p2 #0: Fri Jun 16 01:03:36 UTC 2006
        sullrich@builder.livebsd.com:/usr/obj.pfSense/usr/src/sys/pfSense.6
    Timecounter "i8254" frequency 1193182 Hz quality 0
    CPU: Intel Pentium III (864.56-MHz 686-class CPU)
      Origin = "GenuineIntel"  Id = 0x686  Stepping = 6
      Features=0x383f9ff <fpu,vme,de,pse,tsc,msr,pae,mce,cx8,sep,mtrr,pge,mca,cmov,pat,pse36,mmx,fxsr,sse>real memory  = 267042816 (254 MB)
    avail memory = 251609088 (239 MB)
    wlan: mac acl policy registered
    kbd1 at kbdmux0
    ath_hal: 0.9.16.16 (AR5210, AR5211, AR5212, RF5111, RF5112, RF2413, RF5413)
    acpi0: <dell gx110 ="">on motherboard
    acpi0: Power Button (fixed)
    Timecounter "ACPI-fast" frequency 3579545 Hz quality 1000
    acpi_timer0: <24-bit timer at 3.579545MHz> port 0x808-0x80b on acpi0
    cpu0: <acpi cpu="">on acpi0
    pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
    pci0: <acpi pci="" bus="">on pcib0
    agp0: <intel 82810e="" (i810e="" gmch)="" svga="" controller="">mem 0xf8000000-0xfbffffff,0xff000000-0xff07ffff irq 9 at device 1.0 on pci0
    pcib1: <acpi pci-pci="" bridge="">at device 30.0 on pci0
    pci1: <acpi pci="" bus="">on pcib1
    rl0: <accton 10="" 5030="" 5038="" mpx="" 100basetx="">port 0xec00-0xecff mem 0xfdfffc00-0xfdfffcff irq 10 at device 8.0 on pci1
    miibus0: <mii bus="">on rl0
    rlphy0: <realtek internal="" media="" interface="">on miibus0
    rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    rl0: Ethernet address: 00:30:f1:02:d2:2d
    xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xe880-0xe8ff mem 0xfdfff800-0xfdfff87f irq 5 at device 12.0 on pci1
    miibus1: <mii bus="">on xl0
    xlphy0: <3c905C 10/100 internal PHY> on miibus1
    xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    xl0: Ethernet address: 00:b0:d0💿bc:5b
    isab0: <pci-isa bridge="">at device 31.0 on pci0
    isa0: <isa bus="">on isab0
    atapci0: <intel ich="" udma66="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 on pci0
    ata0: <ata 0="" channel="">on atapci0
    ata1: <ata 1="" channel="">on atapci0
    uhci0: <intel 82801aa="" (ich)="" usb="" controller="">port 0xff80-0xff9f irq 11 at device 31.2 on pci0
    uhci0: [GIANT-LOCKED]
    usb0: <intel 82801aa="" (ich)="" usb="" controller="">on uhci0
    usb0: USB revision 1.0
    uhub0: Intel UHCI root hub, class 9/0, rev 1.00/1.00, addr 1
    uhub0: 2 ports with 2 removable, self powered
    pci0: <serial bus,="" smbus="">at device 31.3 (no driver attached)
    pci0: <multimedia, audio="">at device 31.5 (no driver attached)
    speaker0: <pc speaker="">port 0x61 on acpi0
    fdc0: <floppy drive="" controller="">port 0x3f0-0x3f5,0x3f7 irq 6 drq 2 on acpi0
    fdc0: [FAST]
    fd0: <1440-KB 3.5" drive> on fdc0 drive 0
    atkbdc0: <keyboard controller="" (i8042)="">port 0x60,0x64 irq 1 on acpi0
    atkbd0: <at keyboard="">irq 1 on atkbdc0
    kbd0 at atkbd0
    atkbd0: [GIANT-LOCKED]
    psm0: failed to get status.
    psm0: <ps 2="" mouse="">flags 0x1000 irq 12 on atkbdc0
    psm0: [GIANT-LOCKED]
    psm0: model Generic PS/2 mouse, device ID 171
    sio0: <16550A-compatible COM port> port 0x3f8-0x3ff irq 4 flags 0x10 on acpi0
    sio0: type 16550A
    sio1: <16550A-compatible COM port> port 0x2f8-0x2ff irq 3 on acpi0
    sio1: type 16550A
    ppc0: <ecp parallel="" printer="" port="">port 0x378-0x37f,0x778-0x77f irq 7 on acpi0
    ppc0: SMC-like chipset (ECP/EPP/PS2/NIBBLE) in COMPATIBLE mode
    ppc0: FIFO with 16/16/8 bytes threshold
    ppbus0: <parallel port="" bus="">on ppc0
    lpt0: <printer>on ppbus0
    lpt0: Interrupt-driven port
    ppi0: <parallel i="" o="">on ppbus0
    pmtimer0 on isa0
    orm0: <isa option="" roms="">at iomem 0xc0000-0xc7fff,0xc8000-0xd67ff,0xd6800-0xdffff on isa0
    sc0: <system console="">at flags 0x100 on isa0
    sc0: VGA <16 virtual consoles, flags=0x300>
    vga0: <generic isa="" vga="">at port 0x3c0-0x3df iomem 0xa0000-0xbffff on isa0
    Timecounter "TSC" frequency 864557065 Hz quality 800
    Timecounters tick every 1.000 msec
    Fast IPsec: Initialized Security Association Processing.
    ad0: 8056MB <seagate st38421a="" 6.01="">at ata0-master UDMA66
    acd0: CDROM <samsung cd-rom="" sn-124="" q009="">at ata1-master PIO4
    Trying to mount root from ufs:/dev/ad0s1a
    rl0: link state changed to UP
    xl0: link state changed to UP
    rl0: link state changed to DOWN
    arp: unknown hardware address format (0x4242)
    rl0: link state changed to UP
    pflog0: promiscuous mode enabled
    ipfw2 (+ipv6) initialized, divert loadable, rule-based forwarding enabled, defau
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4242)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4242)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4242)
    arp: unknown hardware address format (0x4500)

    y…

    cat /var/log/system.log | more

    17:51:30 server dnsmasq[1919]: reading /var/dhcpd/var/db/dhcpd.leases
    Aug 19 17:51:46 server last message repeated 3 times
    Aug 19 17:54:05 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 17:54:07 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 18:03:30 server last message repeated 4 times
    Aug 19 18:04:13 server kernel: arp: unknown hardware address format (0x4242)
    Aug 19 18:09:44 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 18:09:44 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 18:10:27 server last message repeated 7 times
    Aug 19 18:14:22 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 18:22:29 server last message repeated 3 times
    Aug 19 18:24:13 server kernel: arp: unknown hardware address format (0x4242)
    Aug 19 18:26:09 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 18:26:09 server kernel: arp: unknown hardware address format (0x4242)
    Aug 19 18:30:06 server last message repeated 4 times
    Aug 19 18:36:12 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 18:43:34 server last message repeated 3 times
    Aug 19 18:49:45 server dnsmasq[1919]: reading /var/dhcpd/var/db/dhcpd.leases
    Aug 19 18:50:06 server sshd[7286]: Accepted keyboard-interactive/pam for root fr
    om 192.168.1.228 port 1586 ssh2
    Aug 19 18:51:07 server dnsmasq[1919]: reading /var/dhcpd/var/db/dhcpd.leases
    Aug 19 18:51:30 server dnsmasq[1919]: reading /var/dhcpd/var/db/dhcpd.leases
    Aug 19 18:53:19 server last message repeated 2 times
    byte 1555 17:51:30 server dnsmasq[1919]: reading /var/dhcpd/var/db/dhcpd.leases
    Aug 19 17:51:46 server last message repeated 3 times
    Aug 19 17:54:05 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 17:54:07 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 18:03:30 server last message repeated 4 times
    Aug 19 18:04:13 server kernel: arp: unknown hardware address format (0x4242)
    Aug 19 18:09:44 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 18:09:44 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 18:10:27 server last message repeated 7 times
    Aug 19 18:14:22 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 18:22:29 server last message repeated 3 times
    Aug 19 18:24:13 server kernel: arp: unknown hardware address format (0x4242)
    Aug 19 18:26:09 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 18:26:09 server kernel: arp: unknown hardware address format (0x4242)
    Aug 19 18:30:06 server last message repeated 4 times
    Aug 19 18:36:12 server kernel: arp: unknown hardware address format (0x4500)
    Aug 19 18:43:34 server last message repeated 3 times
    Aug 19 18:49:45 server dnsmasq[1919]: reading /var/dhcpd/var/db/dhcpd.leases
    Aug 19 18:50:06 server sshd[7286]: Accepted keyboard-interactive/pam for root from 192.168.1.228 port 1586 ssh2
    Aug 19 18:51:07 server dnsmasq[1919]: reading /var/dhcpd/var/db/dhcpd.leases
    Aug 19 18:51:30 server dnsmasq[1919]: reading /var/dhcpd/var/db/dhcpd.leases
    Aug 19 18:53:19 server last message repeated 2 times
    Aug 19 18:54:29 server kernel: arp: unknown hardware address format (0x4500)
    g 19 17:45:40 server kernel: pcib0: <acpi host-pci="" bridge="">port 0xcf8-0xcff on acpi0
    Aug 19 17:45:40 server kernel: pci0: <acpi pci="" bus="">on pcib0
    Aug 19 17:45:40 server kernel: agp0: <intel 82810e="" (i810e="" gmch)="" svga="" controller="">mem 0xf8000000-0xfbffffff,0xff000000-0xff07ffff irq 9 at dev
    ice 1.0 on pci0
    Aug 19 17:45:40 server kernel: pcib1: <acpi pci-pci="" bridge="">at device 30.0 on pci0
    Aug 19 17:45:40 server kernel: pci1: <acpi pci="" bus="">on pcib1
    Aug 19 17:45:40 server kernel: rl0: <accton 10="" 5030="" 5038="" mpx="" 100basetx="">port 0xec00-0xecff mem 0xfdfffc00-0xfdfffcff irq 10 at device 8.0 on
    pci1
    Aug 19 17:45:40 server kernel: miibus0: <mii bus="">on rl0
    Aug 19 17:45:40 server kernel: rlphy0: <realtek internal="" media="" interface="">on miibus0
    Aug 19 17:45:40 server kernel: rlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    Aug 19 17:45:40 server kernel: rl0: Ethernet address: 00:30:f1:02:d2:2d
    Aug 19 17:45:40 server kernel: xl0: <3Com 3c905C-TX Fast Etherlink XL> port 0xe880-0xe8ff mem 0xfdfff800-0xfdfff87f irq 5 at device 12.0 on p
    ci1
    Aug 19 17:45:40 server kernel: miibus1: <mii bus="">on xl0
    Aug 19 17:45:40 server kernel: xlphy0: <3c905C 10/100 internal PHY> on miibus1
    Aug 19 17:45:40 server kernel: xlphy0:  10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, auto
    Aug 19 17:45:40 server kernel: xl0: Ethernet address: 00:b0:d0💿bc:5b
    Aug 19 17:45:40 server kernel: isab0: <pci-isa bridge="">at device 31.0 on pci0
    Aug 19 17:45:40 server kernel: isa0: <isa bus="">on isab0
    Aug 19 17:45:40 server kernel: atapci0: <intel ich="" udma66="" controller="">port 0x1f0-0x1f7,0x3f6,0x170-0x177,0x376,0xffa0-0xffaf at device 31.1 o
    n pci0
    Aug 19 17:45:40 server kernel: ata0: <ata 0="" channel="">on atapci0
    Aug 19 17:45:40 server kernel: ata1: <ata 1="" channel="">on atapci0
    Aug 19 17:45:40 server kernel: uhci0: <intel 82801aa="" (ich)="" usb="" controller="">port 0xff80-0xff9f irq 11 at device 31.2 on pci0
    Aug 19 17:45:40 server kernel: uhci0: [GIANT-LOCKED]
    byte 3565

    como ve señor Bellera da un error arp de un dispositivo desconocido, y tambien en el segundo comando habla de un formato de direccion de dispositivo desconocido…

    que puedo hacer??  no entiendo que debo revisar...  :-\

    muchas gracias por sus comentarios...</intel></ata></ata></intel></isa></pci-isa></mii></realtek></mii></accton></acpi></acpi></intel></acpi></acpi></samsung></seagate></generic></system></isa></parallel></printer></parallel></ecp></ps></at></keyboard></floppy></pc></multimedia,></serial></intel></intel></ata></ata></intel></isa></pci-isa></mii></realtek></mii></accton></acpi></acpi></intel></acpi></acpi></acpi></dell></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,sep,mtrr,pge,mca,cmov,pat,pse36,mmx,fxsr,sse></intel></acpi></acpi></acpi></dell></fpu,vme,de,pse,tsc,msr,pae,mce,cx8,sep,mtrr,pge,mca,cmov,pa<br>



  • ¡Hola!

    El problema parece referirse a IPV6. Como no he empleado nunca IPV6 no te puedo decir si es importante o no … De todas formas ...

    Yo descargaría la configuración XML en un lugar seguro de tu PC, instalaría la 1.2 BETA y cargaría de nuevo la configuración XML guardada.

    De esta forma migrarías de 1.0.1 (basada en FreeBSD 6.1) a 1.2 BETA (basada en FreeBSD 6.2), que reconoce más hardware.

    Tengo la 1.2 BETA-1 funcionando desde abril sin problemas. Y hace unas semanas salió ya la 1.2 BETA-2:

    http://www.bellera.cat/josep/pfsense/installacio_cs.html#download_pfsense

    Saludos,

    Josep Pujadas



  • Saludos!!!  8)

    Tal como me indicó migre de version 1.01 a 1.02 Beta, el sistema mejoró enormemente, ya no se guinda, aun asi sigue dando error, al ejecutar de nuevo los comandos de chequeo del sistema da:

    con:  dmesg | more:

    arp: unknown hardware address format (0x4242)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4500)
    arp: unknown hardware address format (0x4242)
    arp: unknown hardware address format (0x4500)

    con el cat /var/log/system.log | more  da:

    Sep 30 18:46:06 server dhclient[50510]: DHCPACK from 200.109.126.42
    Sep 30 18:46:06 server dhclient[50510]: bound to 190.38.182.18 – renewal in 144
    00 seconds.
    Sep 30 18:46:21 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 18:47:55 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 18:47:58 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 18:50:20 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 18:50:24 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 18:52:26 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 18:52:27 server last message repeated 2 times
    Sep 30 18:52:28 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 18:52:28 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 18:52:28 server last message repeated 2 times
    Sep 30 18:52:34 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 18:53:12 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 18:53:13 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 18:54:31 server kernel: arp: unknown hardware address format (0x4600)
    Sep 30 18:56:10 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 18:56:13 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 18:56:14 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 18:56:14 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 18:57:07 server last message repeated 2 times
    Sep 30 18:59:10 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 18:59:23 server last message repeated 2 times
    Sep 30 18:59:23 server kernel: arp: unknown hardware address format (0x4600)
    Sep 30 18:59:28 server kernel: arp: unknown hardware address format (0x4600)
    Sep 30 18:59:28 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 18:59:36 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:00:00 server check_reload_status: check_reload_status is starting
    Sep 30 19:00:03 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:00:03 server last message repeated 2 times
    Sep 30 19:02:00 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:05:37 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:09:02 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:11:18 server kernel: arp: unknown hardware address format (0x4600)
    Sep 30 19:13:45 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:15:09 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:15:10 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:15:52 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:15:52 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:16:05 server last message repeated 8 times
    Sep 30 19:16:34 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:16:34 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:16:51 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:17:15 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:18:06 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:18:06 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:18:06 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:19:27 server last message repeated 2 times
    Sep 30 19:19:36 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:20:21 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:20:57 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:21:25 server kernel: arp: unknown hardware address format (0x4600)
    Sep 30 19:22:21 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:22:56 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:23:32 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:27:05 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:27:08 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:27:12 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:27:13 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:28:14 server dnsmasq[6102]: reading /var/dhcpd/var/db/dhcpd.leases
    Sep 30 19:29:53 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:35:17 server last message repeated 4 times
    Sep 30 19:35:17 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:36:04 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:36:35 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:36:47 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:38:22 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:38:55 server dnsmasq[6102]: reading /var/dhcpd/var/db/dhcpd.leases
    Sep 30 19:40:07 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:40:07 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:40:08 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:40:32 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:41:18 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:41:55 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:42:14 server dnsmasq[6102]: reading /var/dhcpd/var/db/dhcpd.leases
    Sep 30 19:42:00 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:46:28 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:46:28 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:46:28 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:47:00 server kernel: arp: unknown hardware address format (0x4500)
    Sep 30 19:47:01 server last message repeated 5 times
    Sep 30 19:47:26 server kernel: arp: unknown hardware address format (0x4242)
    Sep 30 19:47:26 server kernel: arp: unknown hardware address format (0x4500)

    es decir al parecer sigue dando un error en la comunicacion… el demonio para gestionar ip v6 arranca normalmente

    Alguna idea de que pueda estar fallando?

    Gracias por sus comentarios....



  • ¡Hola!

    Parece que no es muy importante, a pesar de que podría tratarse de un ataque:

    http://www.bsdforums.org/forums/archive/index.php/t-24284.html

    Si buscas en Google

    server kernel: arp: unknown hardware address format

    verás un montón de entradas sobre el tema.

    En http://freebsd.active-venture.com/faq/networking.html#UNKNOWN-HW-ADDR-FORMAT se explica que se trata de una MAC address que no es correcta para FreeBSD.

    Saludos,

    Josep Pujadas



  • Saludos…  8)

    Algunos comentarios importantes acerca de la migracion:

    Con la Version 1.01 RC

    • RAM:  el consumo de memoria no pasaba de 25 % en 256 Mb

    • CPU:  el porcentaje de uso de CPU era muy bajo de 1 a 5 %

    • Reglas: al utilizar el wizard para filtrar por ejemplo las conexiones P2P fallaba, y se volvia extremadamente inestable

    • Multilogin: al habilitar el rechazo de conexiones multiples con un mismo usuario en captive portal por lo general fallaba, es decir si podian ingresar varios usuarios con la misma clave

    • WAN:  al fallar la conexion o el servicio de internet en la WAN el captive portal fallaba mas no lo indicaba, los usuarios no podian ingresar a internet, mas el servicio de captive portal estaba en verde y corriendo

    • SSH: en la mayoria de los casos en que tendia a fallar el servicio era necesario reiniciar el servidor con la herramienta Putty via ssh ya que via http o via https no se podia ya que no abria la pagina

    • Web en captive portal: La pagina de ingreso acepta imagenes pero el portal tiende a fallar y se torna lenta la conexion

    Con la Version 1.2 RC

    • RAM:  el consumo de memoria aumentó a 40 % en 256 Mb

    • CPU:  el porcentaje de uso de CPU aumentó a 15 %

    • Reglas: no se ha habilitado el wizard para filtrar o limitar las conexiones, se filtra ahora por reglas como lo indica el sr. Bellera en su tutorial, el cual funciona perfectamente (gracias Josep Pujadas excelente tutorial)

    • Multilogin: al habilitar el rechazo de conexiones multiples con un mismo usuario en captive portal funciona perfectamente y lo informa en el registro de logs en captive portal de manera automatica

    • WAN:  al fallar la conexion o el servicio de internet en la WAN el captive portal el servidor tiende a ponerse lento mientras repara la conexion, lo cual lo hace automaticamente y al reestablecerse la conexion con la WAN todo queda normal y sin fallos

    • SSH: la conexion via ssh y/o via ftp es eficiente y rapida

    • Web en captive portal: La pagina de ingreso acepta con facilidad imagenes y corre sin problemas

    Bueno, considero que la migracion mas que una opcion es una necesidad, tal como me lo recomendaron en este foro lo recomiendo a todos los usuarios que aun trabajan con la version 1.01 RC las ventajas son enormes.

    Para el caso del error que sigue presentando "arp: unknown hardware address format (0x4242)" se continua revisando aun sin una respuesta clara de que esta pasando.

    Gracias por su atencion.



  • ¡Hola!

    ¡¡¡¡ Gracias a ti por tu aportación !!!!

    ¡¡¡¡ A esto se le llama hacer comunidad !!!!

    Saludos,

    Josep Pujadas



  • Saludos,
    para el caso del error que continua dando el servidor pfsense en cuanto a las Ip v6 he estado revisando y encontre que en los equipos AP de la red wi fi conectados en la red lan del sistema tienen deshabilitado el soporte IP v6, para habilitarlo se necesitan algunas configuraciones que por ahora no entiendo, voy a realizar modificaciones en estos AP y les cuento luego los resultados…

    :)


Log in to reply