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

    WAN seems to go dead

    Scheduled Pinned Locked Moved General pfSense Questions
    15 Posts 3 Posters 1.0k 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.
    • W
      wc2l
      last edited by

      Hi Folks,
      I'm very new to the Netgate/pfSense world. I have a SG-3100 running 21.02. Packages that are installed are: aws-wizard 0.9, ipsec-profilewizard 1.0_2, and pfBlockerNG-devel 3.0.0_15. Couple of days ago we had a power outage and when the router came back up there was no internet. I just used the serial connection and rebooted the router.

      Today I am working from home and the internet dropped again. I went through the reboot process to get the internet back up..

      Both times the dashboard says the WAN Is up. I don't see any down services. The traffic graphs does appear to have some traffic, but nothing is routing traffic. Can't ping, browse, and etc..

      Is there a way to figure out why it is crashing/dying?
      What causes it?
      Easier way to get it all working again?
      Or better yet keep it up?
      Any help would be appreciated.

      TNX Will

      V 1 Reply Last reply Reply Quote 0
      • V
        viragomann @wc2l
        last edited by

        @wc2l
        Some hints in the system log?

        W 1 Reply Last reply Reply Quote 0
        • W
          wc2l @viragomann
          last edited by

          @viragomann Thank you! Still learning about the router. I have not used the logs before..

          There are two error messages coming from the Status /System Logs/ System Gateways:
          dpinger sendto error: 65

          send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm dest_addr xx.xxx.xxx.x: bind_addr xx.xxx.xxx.xx identifier "WAN_DHCP "

          From what I read, part if it maybe the ISP and part of it may be way pfSense is handling it..

          The only other error I see is under Status /System Logs/ System/General:

          kernel arp: 172.25.25.210 moved from 00:26:32:f0:7c:cf to 00:26:32:f0:ff:cf on mvneta1
          This may be device issue..

          V 1 Reply Last reply Reply Quote 0
          • V
            viragomann @wc2l
            last edited by

            @wc2l said in WAN seems to go dead:

            The only other error I see is under Status /System Logs/ System/General:
            kernel arp: 172.25.25.210 moved from 00:26:32:f0:7c:cf to 00:26:32:f0:ff:cf on mvneta1
            This may be device issue..

            This indicates that this IP is used on two different devices.

            W 1 Reply Last reply Reply Quote 0
            • W
              wc2l @viragomann
              last edited by

              @viragomann
              Actually the same device with two different names I think. They are both Red Pitaya SDR devices. Now to figure out how to address it..

              What about the first half.. Did I have it correct.. And is there a fix?

              V 1 Reply Last reply Reply Quote 0
              • V
                viragomann @wc2l
                last edited by

                @wc2l said in WAN seems to go dead:

                Actually the same device with two different names I think. They are both Red Pitaya SDR devices.

                The log show two different MAC addresses connected to mvneta1. That means, at least two different network interfaces. Since the left part of both in identical, I assume both device are from the same manufacturer.

                @wc2l said in WAN seems to go dead:

                What about the first half.

                Do you mean the gateway log? That shows a WAN gateway outage, but I think that there is a hint in the system log if the failure occur in pfSense. And duplicate IPs should necessarily be eliminated first.

                W 2 Replies Last reply Reply Quote 0
                • W
                  wc2l @viragomann
                  last edited by

                  @viragomann

                  I know that the Red Pitaya has two ways to address the unit.
                  So it is getting two IP v4 addresses from the DHCP server
                  172.25.25.210 00-26-32-f0-ff-cf rp-f07ccf
                  172.25.25.241 00-26-32-f0-7c:cf rp-f07ccf, I believe this is the alias
                  So maybe the IP v6 side doesn't like the alias

                  Are you talking in the Status/System Logs/System/General logs?
                  So I see a license file or something..
                  I see some other stuff, but not sure what some of it means..

                  Mar 17 09:00:00 php 1037 [pfBlockerNG] Starting cron process.
                  Mar 17 09:02:00 php 1037 [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload
                  Mar 17 09:09:18 pkg-static 15960 pfSense-repo upgraded: 21.02 -> 21.02_1
                  Mar 17 09:19:56 kernel arp: 172.25.25.210 moved from 00:26:32:f0:7c:cf to 00:26:32:f0:ff:cf on mvneta1
                  Mar 17 10:00:00 php 47290 [pfBlockerNG] Starting cron process.
                  Mar 17 10:02:22 php 47290 [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload
                  Mar 17 10:19:56 kernel arp: 172.25.25.210 moved from 00:26:32:f0:7c:cf to 00:26:32:f0:ff:cf on mvneta1
                  Mar 17 11:00:00 php 49209 [pfBlockerNG] Starting cron process.
                  Mar 17 11:02:05 php 49209 [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload
                  Mar 17 11:19:56 kernel arp: 172.25.25.210 moved from 00:26:32:f0:7c:cf to 00:26:32:f0:ff:cf on mvneta1
                  Mar 17 12:00:00 php 26973 [pfBlockerNG] Starting cron process.
                  Mar 17 12:02:30 php 26973 [pfBlockerNG] No changes to Firewall rules, skipping Filter Reload
                  Mar 17 12:19:56 kernel arp: 172.25.25.210 moved from 00:26:32:f0:7c:cf to 00:26:32:f0:ff:cf on mvneta1
                  Mar 17 12:30:00 php 29184 rc.update_urltables: /etc/rc.update_urltables: Starting up.
                  Mar 17 12:30:00 php 29184 rc.update_urltables: /etc/rc.update_urltables: Sleeping for 5 seconds.
                  Mar 17 12:30:05 php 29184 rc.update_urltables: /etc/rc.update_urltables: Starting URL table alias updates
                  Mar 17 12:30:05 php 29184 rc.update_urltables: /etc/rc.update_urltables: pfB_PRI1_v4 does not need updating.
                  Mar 17 13:00:00 php 13797 [pfBlockerNG] Starting cron process.
                  Mar 17 13:14:15 php-fpm 357 /index.php: Successful login for user 'admin' from: 172.25.25.219 (Local Database)
                  Mar 17 13:17:30 login 59955 login on ttyu0 as root
                  Mar 17 13:17:51 php 5865 rc.initial.reboot: Stopping all packages.
                  Mar 17 13:17:51 lighttpd_pfb 37717 [pfBlockerNG] DNSBL Webserver stopped
                  Mar 17 13:17:51 tail_pfb 39198 [pfBlockerNG] Firewall Filter Service stopped
                  Mar 17 13:17:51 php_pfb 39216 [pfBlockerNG] filterlog daemon stopped
                  Mar 17 13:17:53 reboot 43464 rebooted by root
                  Mar 17 13:17:53 syslogd exiting on signal 15
                  Mar 17 13:18:48 syslogd kernel boot file is /boot/kernel/kernel
                  Mar 17 13:18:48 kernel ---<<BOOT>>---
                  Mar 17 13:18:48 kernel Copyright (c) 1992-2020 The FreeBSD Project.
                  Mar 17 13:18:48 kernel Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
                  Mar 17 13:18:48 kernel The Regents of the University of California. All rights reserved.
                  Mar 17 13:18:48 kernel FreeBSD is a registered trademark of The FreeBSD Foundation.
                  Mar 17 13:18:48 kernel FreeBSD 12.2-STABLE 0e42b7d7eac(HEAD) pfSense-SG-3100 arm
                  Mar 17 13:18:48 kernel FreeBSD clang version 10.0.1 (git@github.com:llvm/llvm-project.git llvmorg-10.0.1-0-gef32c611aa2)
                  Mar 17 13:18:48 kernel CPU: ARM Cortex-A9 r4p1 (ECO: 0x00000000)
                  Mar 17 13:18:48 kernel CPU Features:
                  Mar 17 13:18:48 kernel Multiprocessing, Thumb2, Security, VMSAv7, Coherent Walk
                  Mar 17 13:18:48 kernel Optional instructions:
                  Mar 17 13:18:48 kernel UMULL, SMULL, SIMD(ext)
                  Mar 17 13:18:48 kernel LoUU:2 LoC:2 LoUIS:2
                  Mar 17 13:18:48 kernel Cache level 1:
                  Mar 17 13:18:48 kernel 32KB/32B 4-way data cache WB Read-Alloc Write-Alloc
                  Mar 17 13:18:48 kernel 32KB/32B 4-way instruction cache Read-Alloc
                  Mar 17 13:18:48 kernel real memory = 2147479552 (2047 MB)
                  Mar 17 13:18:48 kernel avail memory = 2071031808 (1975 MB)
                  Mar 17 13:18:48 kernel FreeBSD/SMP: Multiprocessor System Detected: 2 CPUs
                  Mar 17 13:18:48 kernel arc4random: no preloaded entropy cache
                  Mar 17 13:18:48 kernel ipw_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
                  Mar 17 13:18:48 kernel ipw_ibss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                  Mar 17 13:18:48 kernel module_register_init: MOD_LOAD (ipw_ibss_fw, 0xc014deb0, 0) error 1
                  Mar 17 13:18:48 kernel ipw_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
                  Mar 17 13:18:48 kernel ipw_monitor: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                  Mar 17 13:18:48 kernel module_register_init: MOD_LOAD (ipw_monitor_fw, 0xc014df60, 0) error 1
                  Mar 17 13:18:48 kernel iwi_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
                  Mar 17 13:18:48 kernel iwi_bss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                  Mar 17 13:18:48 kernel module_register_init: MOD_LOAD (iwi_bss_fw, 0xc0156f50, 0) error 1
                  Mar 17 13:18:48 kernel iwi_ibss: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
                  Mar 17 13:18:48 kernel iwi_ibss: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                  Mar 17 13:18:48 kernel module_register_init: MOD_LOAD (iwi_ibss_fw, 0xc0157000, 0) error 1
                  Mar 17 13:18:48 kernel iwi_monitor: You need to read the LICENSE file in /usr/share/doc/legal/intel_iwi.LICENSE.
                  Mar 17 13:18:48 kernel iwi_monitor: If you agree with the license, set legal.intel_iwi.license_ack=1 in /boot/loader.conf.
                  Mar 17 13:18:48 kernel module_register_init: MOD_LOAD (iwi_monitor_fw, 0xc01570b0, 0) error 1
                  Mar 17 13:18:48 kernel ipw_bss: You need to read the LICENSE file in /usr/share/doc/legal/intel_ipw.LICENSE.
                  Mar 17 13:18:48 kernel ipw_bss: If you agree with the license, set legal.intel_ipw.license_ack=1 in /boot/loader.conf.
                  Mar 17 13:18:48 kernel module_register_init: MOD_LOAD (ipw_bss_fw, 0xc014de00, 0) error 1
                  Mar 17 13:18:48 kernel wlan: mac acl policy registered
                  Mar 17 13:18:48 kernel random: entropy device external interface
                  Mar 17 13:18:48 kernel [ath_hal] loaded
                  Mar 17 13:18:48 kernel ofwbus0: <Open Firmware Device Tree>
                  Mar 17 13:18:48 kernel simplebus0: <Flattened device tree simple bus> on ofwbus0
                  Mar 17 13:18:48 kernel simplebus1: <Flattened device tree simple bus> on simplebus0
                  Mar 17 13:18:48 kernel l2cache0: <PL310 L2 cache controller> mem 0x8000-0x8fff on simplebus1
                  Mar 17 13:18:48 kernel l2cache0: cannot allocate IRQ, not using interrupt
                  Mar 17 13:18:48 kernel l2cache0: Part number: 0x3, release: 0x9
                  Mar 17 13:18:48 kernel l2cache0: L2 Cache enabled: 1024KB/32B 16 ways
                  Mar 17 13:18:48 kernel gic0: <ARM Generic Interrupt Controller> mem 0xd000-0xdfff,0xc100-0xc1ff on simplebus1
                  Mar 17 13:18:48 kernel gic0: pn 0x39, arch 0x1, rev 0x2, implementer 0x43b irqs 192
                  Mar 17 13:18:48 kernel mpic0: <Marvell Integrated Interrupt Controller> mem 0x20a00-0x20ccf,0x21070-0x210c7 irq 17 on simplebus1
                  Mar 17 13:18:48 kernel gpio0: <Marvell Integrated GPIO Controller> mem 0x18100-0x1813f,0x181c0-0x181c7 irq 9,10,11,12 on simplebus1
                  Mar 17 13:18:48 kernel gpio0: 4 IRQs available
                  Mar 17 13:18:48 kernel gpio0: Disable interrupts (offset = 0 + EDGE(0x18)
                  Mar 17 13:18:48 kernel gpio0: Disable interrupts (offset = 0 + LEV(0x1C))
                  Mar 17 13:18:48 kernel gpio0: Setup intr 0
                  Mar 17 13:18:48 kernel gpio0: Setup intr 1
                  Mar 17 13:18:48 kernel gpio0: Setup intr 2
                  Mar 17 13:18:48 kernel gpio0: Setup intr 3
                  Mar 17 13:18:48 kernel gpio0: Clear int status (offset = 0)
                  Mar 17 13:18:48 kernel gpiobus0: <GPIO bus> on gpio0
                  Mar 17 13:18:48 kernel gpio1: <Marvell Integrated GPIO Controller> mem 0x18140-0x1817f,0x181c8-0x181cf irq 13,14,15,16 on simplebus1
                  Mar 17 13:18:48 kernel gpio1: 4 IRQs available
                  Mar 17 13:18:48 kernel gpio1: Disable interrupts (offset = 0 + EDGE(0x18)
                  Mar 17 13:18:48 kernel gpio1: Disable interrupts (offset = 0 + LEV(0x1C))
                  Mar 17 13:18:48 kernel gpio1: Setup intr 0
                  Mar 17 13:18:48 kernel gpio1: Setup intr 1
                  Mar 17 13:18:48 kernel gpio1: Setup intr 2
                  Mar 17 13:18:48 kernel gpio1: Setup intr 3
                  Mar 17 13:18:48 kernel gpio1: Clear int status (offset = 0)
                  Mar 17 13:18:48 kernel gpiobus1: <GPIO bus> on gpio1
                  Mar 17 13:18:48 kernel mp_tmr0: <ARM MPCore Timers> mem 0xc200-0xc21f irq 3 on simplebus1
                  Mar 17 13:18:48 kernel Timecounter "MPCore" frequency 800000000 Hz quality 800
                  Mar 17 13:18:48 kernel mp_tmr1: <ARM MPCore Timers> mem 0xc600-0xc61f irq 4 on simplebus1
                  Mar 17 13:18:48 kernel Event timer "MPCore" frequency 800000000 Hz quality 1000
                  Mar 17 13:18:48 kernel twsi0: <Marvell Integrated I2C Bus Controller> mem 0x11000-0x1101f irq 5 on simplebus1
                  Mar 17 13:18:48 kernel iicbus0: <OFW I2C bus> on twsi0
                  Mar 17 13:18:48 kernel iic0: <I2C generic I/O> on iicbus0
                  Mar 17 13:18:48 kernel gpio2: <NXP PCA9552 LED driver> at addr 0xc0 on iicbus0
                  Mar 17 13:18:48 kernel device_attach: gpio2 attach returned 6
                  Mar 17 13:18:48 kernel gpio2: <ISSI IS31FL3199 9 channel light effect LED driver> at addr 0xce on iicbus0
                  Mar 17 13:18:48 kernel gpiobus2: <OFW GPIO bus> on gpio2
                  Mar 17 13:18:48 kernel gpioc2: <GPIO controller> on gpio2
                  Mar 17 13:18:48 kernel uart0: <16550 or compatible> mem 0x12000-0x120ff irq 7 on simplebus1
                  Mar 17 13:18:48 kernel uart0: console (-1,n,8,1)
                  Mar 17 13:18:48 kernel uart1: <16550 or compatible> mem 0x12100-0x121ff irq 8 on simplebus1
                  Mar 17 13:18:48 kernel gpioc0: <GPIO controller> on gpio0
                  Mar 17 13:18:48 kernel gpioc1: <GPIO controller> on gpio1
                  Mar 17 13:18:48 kernel wdt0: <Marvell Watchdog Timer> mem 0x20300-0x20333,0x20704-0x20707,0x18260-0x18263 irq 24,25 on simplebus1
                  Mar 17 13:18:48 kernel pmsu0: <Power Management Service Unit> mem 0x22000-0x22fff on simplebus1
                  Mar 17 13:18:48 kernel mvneta0: <NETA controller> mem 0x30000-0x33fff irq 26 on simplebus1
                  Mar 17 13:18:48 kernel mvneta0: version is 10
                  Mar 17 13:18:48 kernel mvneta0: Ethernet address: 00:08:a2:0d:f8:62
                  Mar 17 13:18:48 kernel miibus0: <MII bus> on mvneta0
                  Mar 17 13:18:48 kernel mv88e151x0: <Marvell 88E1512 Gigabit PHY> PHY 1 on miibus0
                  Mar 17 13:18:48 kernel mv88e151x0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseSX, 1000baseSX-FDX, auto
                  Mar 17 13:18:48 kernel mvneta1: <NETA controller> mem 0x34000-0x37fff irq 27 on simplebus1
                  Mar 17 13:18:48 kernel mvneta1: version is 10
                  Mar 17 13:18:48 kernel mvneta1: Ethernet address: 00:08:a2:0d:f8:63
                  Mar 17 13:18:48 kernel mdio0: <MDIO> on mvneta1
                  Mar 17 13:18:48 kernel e6000sw0: <Marvell 88E6141> on mdio0
                  Mar 17 13:18:48 kernel e6000sw0: single-chip addressing mode
                  Mar 17 13:18:48 kernel e6000sw0: PHY at port 1
                  Mar 17 13:18:48 kernel miibus1: <MII bus> on e6000sw0
                  Mar 17 13:18:48 kernel e1000phy0: <Marvell 88E1000 Gigabit PHY> PHY 17 on miibus1
                  Mar 17 13:18:48 kernel e1000phy0: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
                  Mar 17 13:18:48 kernel e6000sw0: PHY at port 2
                  Mar 17 13:18:48 kernel miibus2: <MII bus> on e6000sw0
                  Mar 17 13:18:48 kernel e1000phy1: <Marvell 88E1000 Gigabit PHY> PHY 18 on miibus2
                  Mar 17 13:18:48 kernel e1000phy1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
                  Mar 17 13:18:48 kernel e6000sw0: PHY at port 3
                  Mar 17 13:18:48 kernel miibus3: <MII bus> on e6000sw0
                  Mar 17 13:18:48 kernel e1000phy2: <Marvell 88E1000 Gigabit PHY> PHY 19 on miibus3
                  Mar 17 13:18:48 kernel e1000phy2: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
                  Mar 17 13:18:48 kernel e6000sw0: PHY at port 4
                  Mar 17 13:18:48 kernel miibus4: <MII bus> on e6000sw0
                  Mar 17 13:18:48 kernel e1000phy3: <Marvell 88E1000 Gigabit PHY> PHY 20 on miibus4
                  Mar 17 13:18:48 kernel e1000phy3: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, auto
                  Mar 17 13:18:48 kernel e6000sw0: CPU port at 5
                  Mar 17 13:18:48 kernel e6000sw0: fixed port at 5
                  Mar 17 13:18:48 kernel e6000sw0: switch is ready.
                  Mar 17 13:18:48 kernel etherswitch0: <Switch controller> on e6000sw0
                  Mar 17 13:18:48 kernel mvneta2: <NETA controller> mem 0x70000-0x73fff irq 28 on simplebus1
                  Mar 17 13:18:48 kernel mvneta2: version is 10
                  Mar 17 13:18:48 kernel mvneta2: Ethernet address: 00:08:a2:0d:f8:64
                  Mar 17 13:18:48 kernel miibus5: <MII bus> on mvneta2
                  Mar 17 13:18:48 kernel mv88e151x1: <Marvell 88E1512 Gigabit PHY> PHY 0 on miibus5
                  Mar 17 13:18:48 kernel mv88e151x1: none, 10baseT, 10baseT-FDX, 100baseTX, 100baseTX-FDX, 1000baseT, 1000baseT-master, 1000baseT-FDX, 1000baseT-FDX-master, 1000baseSX, 1000baseSX-FDX, auto
                  Mar 17 13:18:48 kernel ehci0: <Marvell Integrated USB 2.0 controller> mem 0x58000-0x584ff irq 29 on simplebus1
                  Mar 17 13:18:48 kernel usbus0: EHCI version 1.0
                  Mar 17 13:18:48 kernel usbus0 on ehci0
                  Mar 17 13:18:48 kernel cesa0: <Marvell Cryptographic Engine and Security Accelerator> mem 0x90000-0x9ffff irq 30,31 on simplebus1
                  Mar 17 13:18:48 kernel rtc0: <Marvell Integrated RTC> mem 0xa3800-0xa381f,0x184a0-0x184ab irq 32 on simplebus1
                  Mar 17 13:18:48 kernel rtc0: registered as a time-of-day clock, resolution 1.000000s
                  Mar 17 13:18:48 kernel ahci0: <Marvell AHCI Controller> mem 0xa8000-0xa9fff irq 33 on simplebus1
                  Mar 17 13:18:48 kernel ahci0: AHCI v1.00 with 2 6Gbps ports, Port Multiplier supported with FBS
                  Mar 17 13:18:48 kernel ahci0: quirks=0x200010<2CH,MRVL_SR_DEL>
                  Mar 17 13:18:48 kernel ahcich0: <AHCI channel> at channel 0 on ahci0
                  Mar 17 13:18:48 kernel ahcich1: <AHCI channel> at channel 1 on ahci0
                  Mar 17 13:18:48 kernel armada_thermal0: <Armada380 Thermal Control> mem 0xe4078-0xe407b,0xe4070-0xe4077 on simplebus1
                  Mar 17 13:18:48 kernel sdhci_fdt0: <ARMADA38X SDHCI controller> mem 0xd8000-0xd8fff,0xdc000-0xdc0ff,0x18454-0x18457 irq 36 on simplebus1
                  Mar 17 13:18:48 kernel sdhci_fdt0: 1 slot(s) allocated
                  Mar 17 13:18:48 kernel xhci0: <Marvell Integrated USB 3.0 controller> mem 0xf8000-0xfbfff,0xfc000-0xfffff irq 38 on simplebus1
                  Mar 17 13:18:48 kernel xhci0: 32 bytes context size, 32-bit DMA
                  Mar 17 13:18:48 kernel usbus1 on xhci0
                  Mar 17 13:18:48 kernel cesa1: <Marvell Cryptographic Engine and Security Accelerator> mem 0x90000-0x9ffff irq 39,40 on simplebus1
                  Mar 17 13:18:48 kernel spi0: <Marvell SPI controller> mem 0xf001000000010600-0xf00100000001064f irq 1 on simplebus0
                  Mar 17 13:18:48 kernel cpulist0: <Open Firmware CPU Group> on ofwbus0
                  Mar 17 13:18:48 kernel cpu0: <Open Firmware CPU> on cpulist0
                  Mar 17 13:18:48 kernel cpu1: <Open Firmware CPU> on cpulist0
                  Mar 17 13:18:48 kernel cryptosoft0: <software crypto>
                  Mar 17 13:18:48 kernel Timecounters tick every 1.000 msec
                  Mar 17 13:18:48 kernel mvneta1: link state changed to UP
                  Mar 17 13:18:48 kernel spibus0: <OFW SPI bus> on spi0
                  Mar 17 13:18:48 kernel mx25l0: <M25Pxx Flash Family> at cs 0 mode 0 on spibus0
                  Mar 17 13:18:48 kernel mx25l0: device type w25q32jv, size 4096K in 64 sectors of 64K, erase size 4K
                  Mar 17 13:18:48 kernel Release APs
                  Mar 17 13:18:48 kernel e6000sw0port1: link state changed to DOWN
                  Mar 17 13:18:48 kernel usbus0:
                  Mar 17 13:18:48 kernel e6000sw0port2: link state changed to DOWN
                  Mar 17 13:18:48 kernel 480Mbps High Speed USB v2.0
                  Mar 17 13:18:48 kernel e6000sw0port3: link state changed to DOWN
                  Mar 17 13:18:48 kernel usbus1:
                  Mar 17 13:18:48 kernel e6000sw0port4: link state changed to DOWN
                  Mar 17 13:18:48 kernel 5.0Gbps Super Speed USB v3.0
                  Mar 17 13:18:48 kernel ugen0.1: <Marvell EHCI root HUB> at usbus0
                  Mar 17 13:18:48 kernel uhub0: <Marvell EHCI root HUB, class 9/0, rev 2.00/1.00, addr 1> on usbus0
                  Mar 17 13:18:48 kernel ugen1.1: <Marvell XHCI root HUB> at usbus1
                  Mar 17 13:18:48 kernel uhub1: Trying to mount root from ufs:/dev/diskid/DISK-DEF032184200371s2a [rw,noatime]...
                  Mar 17 13:18:48 kernel <Marvell XHCI root HUB, class 9/0, rev 3.00/1.00, addr 1> on usbus1
                  Mar 17 13:18:48 kernel Root mount waiting for: usbus0 CAM usbus1
                  Mar 17 13:18:48 kernel uhub1: 2 ports with 2 removable, self powered
                  Mar 17 13:18:48 kernel mmc0: <MMC/SD bus> on sdhci_fdt0
                  Mar 17 13:18:48 kernel mmcsd0: 8GB <MMCHC M32508 0.1 SN 1B0C645E MFG 08/2018 by 112 0x0000> at mmc0 50.0MHz/8bit/65535-block
                  Mar 17 13:18:48 kernel mmcsd0boot0: 4MB partition 1 at mmcsd0
                  Mar 17 13:18:48 kernel mmcsd0boot1: 4MB partition 2 at mmcsd0
                  Mar 17 13:18:48 kernel mmcsd0rpmb: 4MB partition 3 at mmcsd0
                  Mar 17 13:18:48 kernel uhub0: 1 port with 1 removable, self powered
                  Mar 17 13:18:48 kernel Root mount waiting for: CAM
                  Mar 17 13:18:48 kernel Root mount waiting for: CAM
                  Mar 17 13:18:48 kernel e6000sw0port3: link state changed to UP
                  Mar 17 13:18:48 kernel Root mount waiting for: CAM
                  Mar 17 13:18:48 kernel e6000sw0port1: link state changed to UP
                  Mar 17 13:18:48 kernel e6000sw0port2: link state changed to UP
                  Mar 17 13:18:48 kernel Root mount waiting for: CAM
                  Mar 17 13:18:48 kernel Root mount waiting for: CAM
                  Mar 17 13:18:48 kernel Root mount waiting for: CAM
                  Mar 17 13:18:48 kernel Root mount waiting for: CAM
                  Mar 17 13:18:48 kernel Root mount waiting for: CAM
                  Mar 17 13:18:48 kernel ada0 at ahcich1 bus 0 scbus1 target 0 lun 0
                  Mar 17 13:18:48 kernel ada0: <NT-32 Q0927A> ACS-2 ATA SATA 3.x device
                  Mar 17 13:18:48 kernel ada0: Serial Number DEF032184200371
                  Mar 17 13:18:48 kernel ada0: 600.000MB/s transfers (SATA 3.x, UDMA6, PIO 512bytes)
                  Mar 17 13:18:48 kernel ada0: Command Queueing enabled
                  Mar 17 13:18:48 kernel ada0: 30029MB (61500000 512 byte sectors)
                  Mar 17 13:18:48 kernel mountroot: waiting for device /dev/diskid/DISK-DEF032184200371s2a...
                  Mar 17 13:18:48 kernel random: unblocking device.
                  Mar 17 13:18:48 kernel arc4random: no preloaded entropy cache
                  Mar 17 13:18:48 kernel lo0: link state changed to UP
                  Mar 17 13:18:48 check_reload_status 396 Linkup starting $e6000sw0port1
                  Mar 17 13:18:48 kernel e6000sw0port1: link state changed to DOWN
                  Mar 17 13:18:48 check_reload_status 396 Linkup starting $e6000sw0port2
                  Mar 17 13:18:48 kernel e6000sw0port2: link state changed to DOWN
                  Mar 17 13:18:48 check_reload_status 396 Linkup starting $e6000sw0port3
                  Mar 17 13:18:48 kernel e6000sw0port3: link state changed to DOWN
                  Mar 17 13:18:49 kernel vlan0: changing name to 'mvneta1.3'
                  Mar 17 13:18:49 check_reload_status 396 Linkup starting mvneta2
                  Mar 17 13:18:49 kernel mvneta2: link state changed to UP
                  Mar 17 13:18:50 sshd 16342 Server listening on :: port 22.
                  Mar 17 13:18:50 sshd 16342 Server listening on 0.0.0.0 port 22.
                  Mar 17 13:18:50 check_reload_status 396 rc.newwanip starting mvneta2
                  Mar 17 13:18:50 php 400 rc.bootup: Resyncing OpenVPN instances.
                  Mar 17 13:18:50 kernel pflog0: promiscuous mode enabled
                  Mar 17 13:18:50 kernel ....
                  Mar 17 13:18:51 php-fpm 357 /rc.newwanip: rc.newwanip: Info: starting on mvneta2.
                  Mar 17 13:18:51 php-fpm 357 /rc.newwanip: rc.newwanip: on (IP address: 67.248.235.52) (interface: WAN[wan]) (real interface: mvneta2).
                  Mar 17 13:18:51 kernel .done.
                  Mar 17 13:18:52 php 400 rc.bootup: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
                  Mar 17 13:18:52 php 400 rc.bootup: Default gateway setting Interface WAN_DHCP Gateway as default.
                  Mar 17 13:18:52 php 400 rc.bootup: Gateway, none 'available' for inet6, use the first one configured. ''
                  Mar 17 13:18:52 kernel done.
                  Mar 17 13:18:53 check_reload_status 396 Linkup starting $e6000sw0port1
                  Mar 17 13:18:53 kernel e6000sw0port1: link state changed to UP
                  Mar 17 13:18:53 kernel e6000sw0port2: link state changed to UP
                  Mar 17 13:18:53 kernel e6000sw0port3: link state changed to UP
                  Mar 17 13:18:53 check_reload_status 396 Linkup starting $e6000sw0port2
                  Mar 17 13:18:53 check_reload_status 396 Linkup starting $e6000sw0port3
                  Mar 17 13:18:55 php 400 rc.bootup: sync unbound done.
                  Mar 17 13:18:56 kernel done.
                  Mar 17 13:18:57 kernel done.
                  Mar 17 13:18:57 kernel done.
                  Mar 17 13:18:57 php 400 rc.bootup: NTPD is starting up.
                  Mar 17 13:18:57 kernel done.
                  Mar 17 13:18:57 kernel done.
                  Mar 17 13:18:57 check_reload_status 396 Updating all dyndns
                  Mar 17 13:18:57 kernel ....
                  Mar 17 13:18:58 php 400 rc.bootup: The command '/usr/local/sbin/strongswanrc stop' returned exit code '1', the output was 'strongswan not running? (check /var/run/daemon-charon.pid).'
                  Mar 17 13:18:58 kernel .done.
                  Mar 17 13:19:03 php 400 rc.bootup: Creating rrd update script
                  Mar 17 13:19:03 kernel done.
                  Mar 17 13:19:03 kernel done.
                  Mar 17 13:19:04 root 90263 /etc/rc.d/hostid: WARNING: hostid: unable to figure out a UUID from DMI data, generating a new one
                  Mar 17 13:19:06 syslogd exiting on signal 15
                  Mar 17 13:19:06 syslogd kernel boot file is /boot/kernel/kernel
                  Mar 17 13:19:06 kernel done.
                  Mar 17 13:19:07 php-fpm 357 /rc.start_packages: Restarting/Starting all packages.
                  Mar 17 13:19:08 lighttpd_pfb 26000 [pfBlockerNG] DNSBL Webserver stopped
                  Mar 17 13:19:08 lighttpd_pfb 27571 [pfBlockerNG] DNSBL Webserver started
                  Mar 17 13:19:09 php-fpm 357 [pfBlockerNG] Starting firewall filter daemon
                  Mar 17 13:19:09 lighttpd_pfb 51085 [pfBlockerNG] DNSBL Webserver stopped
                  Mar 17 13:19:09 tail_pfb 50547 [pfBlockerNG] Firewall Filter Service stopped
                  Mar 17 13:19:09 php_pfb 52220 [pfBlockerNG] filterlog daemon stopped
                  Mar 17 13:19:09 lighttpd_pfb 54599 [pfBlockerNG] DNSBL Webserver started
                  Mar 17 13:19:09 tail_pfb 55017 [pfBlockerNG] Firewall Filter Service stopped
                  Mar 17 13:19:09 php_pfb 55757 [pfBlockerNG] filterlog daemon stopped
                  Mar 17 13:19:09 root 55381 Bootup complete
                  Mar 17 13:19:10 tail_pfb 58947 [pfBlockerNG] Firewall Filter Service started
                  Mar 17 13:19:10 tail_pfb 60178 [pfBlockerNG] Firewall Filter Service started
                  Mar 17 13:19:11 php 59349 [pfBlockerNG] filterlog daemon started
                  Mar 17 13:19:11 php 60430 [pfBlockerNG] filterlog daemon started
                  Mar 17 13:19:11 login 67067 login on ttyu0 as root
                  Mar 17 13:19:26 php 92685 [pfBlockerNG] DNSBL parser daemon started
                  Mar 17 13:19:39 php-fpm 357 /index.php: Successful login for user 'admin' from: 172.25.25.219 (Local Database)

                  V 1 Reply Last reply Reply Quote 0
                  • V
                    viragomann @wc2l
                    last edited by

                    @wc2l said in WAN seems to go dead:

                    @viragomann
                    I know that the Red Pitaya has two ways to address the unit.
                    So it is getting two IP v4 addresses from the DHCP server
                    172.25.25.210 00-26-32-f0-ff-cf rp-f07ccf
                    172.25.25.241 00-26-32-f0-7c:cf rp-f07ccf, I believe this is the alias

                    Accordingly to the system log, the IP 172.25.25.210 is assigned to both interfaces. No properly working DHCP server assings an IP twice. It assings one IP to one MAC. So if the device has two MAC addresses, it may get two different IPs, but not a single IP for both MACs.

                    W 1 Reply Last reply Reply Quote 0
                    • W
                      wc2l @viragomann
                      last edited by

                      @viragomann
                      Since my ISP doesn't do IPv6, can/should I disable IPv6 on the Netgate? I don't use it anywhere else that know of. Other option, is there a similar setup for the IPv6 configuration. Maybe I will reach out to the person that did the setup.. If I can figure that out..

                      So from the device, it is running Alpine Linux and this is part of the startup.sh

                      address=`awk -F : '$5="FF"' OFS=: /sys/class/net/eth0/address`
ip link add mvl0 link eth0 address $address type macvlan mode passthru
echo 1 > /proc/sys/net/ipv4/conf/all/arp_filter
echo 2 > /proc/sys/net/ipv4/conf/all/rp_filter

$apps_dir/sdr_receiver_hpsdr_122_88/sdr-receiver-hpsdr eth0 1 1 1 1 1 1 1 1 &
$apps_dir/sdr_receiver_hpsdr_122_88/sdr-receiver-hpsdr mvl0 1 1 1 1 1 1 1 1 &

                      It does nothing for the IPv6 side which thinks it has two devices..
                      Using SSH I can get to the same device. Below is the ifconfig results

                      172.25.25.210

                      eth0      Link encap:Ethernet  HWaddr 00:26:32:F0:7C:CF
          inet addr:172.25.25.241  Bcast:172.25.25.255  Mask:255.255.255.0
          inet6 addr: fe80::226:32ff:fef0:7ccf/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:47359 errors:0 dropped:5213 overruns:0 frame:0
          TX packets:147227075 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6103252 (5.8 MiB)  TX bytes:3502126207 (3.2 GiB)
          Interrupt:30 Base address:0xb000

                      172.25.25.241

                      eth0      Link encap:Ethernet  HWaddr 00:26:32:F0:7C:CF
          inet addr:172.25.25.241  Bcast:172.25.25.255  Mask:255.255.255.0
          inet6 addr: fe80::226:32ff:fef0:7ccf/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:48213 errors:0 dropped:5280 overruns:0 frame:0
          TX packets:149232728 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:6192308 (5.9 MiB)  TX bytes:1360727636 (1.2 GiB)
          Interrupt:30 Base address:0xb000
                      D 1 Reply Last reply Reply Quote 0
                      • D
                        DLFerguRD @wc2l
                        last edited by

                        @wc2l
                        I had this happed as well. After a power failure the pfsense box would boot up before the modem had time to initialize completely, as a result the modem would supply a temporary ip address to the wan interface. After the modem synced up, the wan ip would change to the correct external ip but for some reason pfsense would not route any traffic.

                        In Interfaces->WAN check this setting
                        Reject leases from 192.168.100.1 <-example address

                         To have the DHCP client reject offers from specific DHCP servers, enter their IP 
 addresses here (separate multiple entries with a comma). This is useful for rejecting leases from cable modems that offer private IP addresses when they lose upstream sync.

                        This worked for me.

                        W 1 Reply Last reply Reply Quote 0
                        • W
                          wc2l @DLFerguRD
                          last edited by

                          @dlfergurd
                          I didn't see any of those in the logs, how do I know what to add?

                          D 1 Reply Last reply Reply Quote 0
                          • D
                            DLFerguRD @wc2l
                            last edited by

                            @wc2l
                            It has bee a while since i had this problem.
                            I think the way I did it was:
                            Shut down pfsense.
                            Unplug modem.
                            Disconnect cable feed from modem.
                            Plug in modem.
                            Start pfsense.

                            Watch the console screen as pfsense boots up and note wan ip address.
                            If your wan address is a private address such as 192.168.1.xxx then you are getting it from the modem. I just guessed my modems ip was 192.168.1.1 and entered that. You can check to see what pfsense shows as the default gateway address.

                            Attach the cable feed to the modem, your wan IP may change to the external ip provided by your isp after the modem syncs.

                            1 Reply Last reply Reply Quote 1
                            • W
                              wc2l @viragomann
                              last edited by

                              @viragomann
                              OK, I'm learning.. you get two ports.. from the interface
                              eth0

                              eth0      Link encap:Ethernet  HWaddr 00:26:32:F0:7C:CF
          inet addr:172.25.25.241  Bcast:172.25.25.255  Mask:255.255.255.0
          inet6 addr: fe80::226:32ff:fef0:7ccf/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:68645 errors:0 dropped:7789 overruns:0 frame:0
          TX packets:224135243 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:8813788 (8.4 MiB)  TX bytes:200723098 (191.4 MiB)
          Interrupt:30 Base address:0xb000

                              Then you get mvl0

                              
mvl0      Link encap:Ethernet  HWaddr 00:26:32:F0:FF:CF
          inet addr:172.25.25.210  Bcast:172.25.25.255  Mask:255.255.255.0
          inet6 addr: fe80::226:32ff:fef0:ffcf/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:51817 errors:0 dropped:23 overruns:0 frame:0
          TX packets:102896469 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:7491125 (7.1 MiB)  TX bytes:110510333807 (102.9 GiB)
                              V 1 Reply Last reply Reply Quote 0
                              • V
                                viragomann @wc2l
                                last edited by

                                @wc2l
                                So each IP is assigned to a unique hardware address in the interface settings, but as the pfSense log shows, 172.25.25.210 is switching from one to the other. That's a misconduct of the device.
                                You may assign multiple IPs to a singel MAC, but it cannot be the other way round. An IP has to be assinged to only one MAC.

                                W 1 Reply Last reply Reply Quote 0
                                • W
                                  wc2l @viragomann
                                  last edited by wc2l

                                  @viragomann
                                  I think this is what is happening.
                                  https://docs.netgate.com/pfsense/en/latest/troubleshooting/logs-arp-moved.html

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