Always Wan-ip but gateway is 100% packet loss

AcidSleeper

Diagnostics -> Routes
The ISP assigned IP and gateway listed?
generally does it show all the IP addresses you expect ?

AcidSleeper

Here I did a Status - Interfaces: Release Wan and the checkbox with Relinquish Lease Checked.
Then I in Command Promt I wrote: "ifconfig igc0 down" waited lets say 20seconds and then typed "ifconfig igc0 up"

I had internet, gateway was online. But when I rebooted the result was 100% packet loss.

Dec 1 14:42:21	php-fpm	399	/status_interfaces.php: The command '/usr/local/sbin/dhclient {$ipv} -d -r -lf '/var/db/dhclient.leases.igc0' -cf '/var/etc/dhclient_wan.conf' -sf '/usr/local/sbin/pfSense-dhclient-script'' returned exit code '1', the output was 'Internet Systems Consortium DHCP Client 4.4.3-P1 Copyright 2004-2022 Internet Systems Consortium. All rights reserved. For info, please visit https://www.isc.org/software/dhcp/ /var/db/dhclient.leases.igc0 line 4: expecting lease declaration. next-server ^ /var/db/dhclient.leases.igc0 line 5: expecting semicolon. option ^ /var/db/dhclient.leases.igc0 line 18: expecting lease declaration. next-server ^ /var/db/dhclient.leases.igc0 line 19: expecting semicolon. option ^ Listening on BPF/igc0/60:be:b4:02:e3:42 Sending on BPF/igc0/60:be:b4:02:e3:42 Can't attach interface {} to bpf device /dev/bpf0: Device not configured If you think you have received this message due to a bug rather than a configuration issue please read the section on submitting bugs on either our web page at www.isc.org or in the README file before submitting a bug. These pages explain the proper process and the information we find helpful for debugging. exiting.'
Dec 1 14:42:24	php-fpm	399	/status_interfaces.php: Resyncing OpenVPN instances for interface WAN.
Dec 1 14:42:24	check_reload_status	439	Reloading filter
Dec 1 14:42:24	php-fpm	399	/status_interfaces.php: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Dec 1 14:42:24	php-fpm	399	/status_interfaces.php: The command '/sbin/route -n6 get 'default' 2>/dev/null | /usr/bin/egrep 'flags: <.*PROTO.*>'' returned exit code '1', the output was ''
Dec 1 14:42:24	check_reload_status	439	Starting packages
Dec 1 14:42:25	php-fpm	43555	/rc.start_packages: Restarting/Starting all packages.
Dec 1 14:43:43	kernel		igc0: link state changed to DOWN
Dec 1 14:43:43	check_reload_status	439	Linkup starting igc0
Dec 1 14:43:44	php-fpm	43555	/rc.linkup: Hotplug event detected for WAN(wan) dynamic IP address (4: dhcp)
Dec 1 14:43:44	php-fpm	43555	/rc.linkup: DEVD Ethernet detached event for wan
Dec 1 14:43:44	check_reload_status	439	Reloading filter
Dec 1 14:43:44	rc.gateway_alarm	6428	>>> Gateway alarm: WAN_DHCP (Addr:192.121.XXX.1 Alarm:down RTT:0ms RTTsd:0ms Loss:100%)
Dec 1 14:43:44	check_reload_status	439	updating dyndns WAN_DHCP
Dec 1 14:43:44	check_reload_status	439	Restarting IPsec tunnels
Dec 1 14:43:44	check_reload_status	439	Restarting OpenVPN tunnels/interfaces
Dec 1 14:43:44	check_reload_status	439	Reloading filter
Dec 1 14:43:45	php-fpm	400	/rc.openvpn: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Dec 1 14:43:45	php-fpm	400	/rc.openvpn: The command '/sbin/route -n6 get 'default' 2>/dev/null | /usr/bin/egrep 'flags: <.*PROTO.*>'' returned exit code '1', the output was ''
Dec 1 14:43:47	check_reload_status	439	Linkup starting igc0
Dec 1 14:43:47	kernel		igc0: link state changed to UP
Dec 1 14:43:48	php-fpm	400	/rc.linkup: Hotplug event detected for WAN(wan) dynamic IP address (4: dhcp)
Dec 1 14:43:48	php-fpm	400	/rc.linkup: DEVD Ethernet attached event for wan
Dec 1 14:43:48	php-fpm	400	/rc.linkup: HOTPLUG: Configuring interface wan
Dec 1 14:43:48	check_reload_status	439	rc.newwanip starting igc0
Dec 1 14:43:48	php-fpm	400	/rc.linkup: Gateway, none 'available' for inet, use the first one configured. 'WAN_DHCP'
Dec 1 14:43:48	php-fpm	400	/rc.linkup: The command '/sbin/route -n6 get 'default' 2>/dev/null | /usr/bin/egrep 'flags: <.*PROTO.*>'' returned exit code '1', the output was ''
Dec 1 14:43:48	check_reload_status	439	Restarting IPsec tunnels
Dec 1 14:43:48	check_reload_status	439	updating dyndns wan
Dec 1 14:43:48	check_reload_status	439	Reloading filter
Dec 1 14:43:49	php-fpm	399	/rc.newwanip: rc.newwanip: Info: starting on igc0.
Dec 1 14:43:49	php-fpm	399	/rc.newwanip: rc.newwanip: on (IP address: 192.121.XXX.95) (interface: WAN[wan]) (real interface: igc0).
Dec 1 14:43:50	php-fpm	399	/rc.newwanip: Removing static route for monitor 8.8.8.8 and adding a new route through 192.121.XXX.1
Dec 1 14:43:50	php-fpm	399	/rc.newwanip: Gateway, NONE AVAILABLE
Dec 1 14:43:50	php-fpm	399	/rc.newwanip: The command '/sbin/route -n6 get 'default' 2>/dev/null | /usr/bin/egrep 'flags: <.*PROTO.*>'' returned exit code '1', the output was ''
Dec 1 14:43:50	php-fpm	399	/rc.newwanip: IP Address has changed, killing states on former IP Address 0.0.0.0.
Dec 1 14:43:50	php-fpm	399	/rc.newwanip: Resyncing OpenVPN instances for interface WAN.
Dec 1 14:43:50	php-fpm	399	/rc.newwanip: Creating rrd update script
Dec 1 14:43:52	php-fpm	399	/rc.newwanip: pfSense package system has detected an IP change or dynamic WAN reconnection - 0.0.0.0 -> 192.121.XXX.95 - Restarting packages.
Dec 1 14:43:52	check_reload_status	439	Starting packages
Dec 1 14:43:52	check_reload_status	439	Reloading filter
Dec 1 14:43:54	php-fpm	400	/rc.start_packages: Restarting/Starting all packages.
Dec 1 14:44:48	php-fpm	43555	/diag_reboot.php: Stopping all packages.
Dec 1 14:44:51	reboot	10265	rebooted by root
Dec 1 14:44:51	syslogd		exiting on signal 15
Dec 1 14:45:34	syslogd		kernel boot file is /boot/kernel/kernel
Dec 1 14:45:34	kernel		---<<BOOT>>---
Dec 1 14:45:34	kernel		igc0: <Intel(R) Ethernet Controller I225-V> mem 0x50a00000-0x50afffff,0x50b00000-0x50b03fff at device 0.0 on pci2
Dec 1 14:45:34	kernel		igc0: Using 1024 TX descriptors and 1024 RX descriptors
Dec 1 14:45:34	kernel		igc0: Using 2 RX queues 2 TX queues
Dec 1 14:45:34	kernel		igc0: Using MSI-X interrupts with 3 vectors
Dec 1 14:45:34	kernel		igc0: Ethernet address: 60:be:b4:02:e3:42
Dec 1 14:45:34	kernel		igc0: netmap queues/slots: TX 2/1024, RX 2/1024
Dec 1 14:45:34	kernel		igc1: <Intel(R) Ethernet Controller I225-V> mem 0x50800000-0x508fffff,0x50900000-0x50903fff at device 0.0 on pci3
Dec 1 14:45:34	kernel		igc1: Using 1024 TX descriptors and 1024 RX descriptors
Dec 1 14:45:34	kernel		igc1: Using 2 RX queues 2 TX queues
Dec 1 14:45:34	kernel		igc1: Using MSI-X interrupts with 3 vectors
Dec 1 14:45:34	kernel		igc1: Ethernet address: 60:be:b4:02:e3:43
Dec 1 14:45:34	kernel		igc1: netmap queues/slots: TX 2/1024, RX 2/1024
Dec 1 14:45:34	kernel		igc2: <Intel(R) Ethernet Controller I225-V> mem 0x50600000-0x506fffff,0x50700000-0x50703fff at device 0.0 on pci4
Dec 1 14:45:34	kernel		igc2: Using 1024 TX descriptors and 1024 RX descriptors
Dec 1 14:45:34	kernel		igc2: Using 2 RX queues 2 TX queues
Dec 1 14:45:34	kernel		igc2: Using MSI-X interrupts with 3 vectors
Dec 1 14:45:34	kernel		igc2: Ethernet address: 60:be:b4:02:e3:44
Dec 1 14:45:34	kernel		igc2: netmap queues/slots: TX 2/1024, RX 2/1024
Dec 1 14:45:34	kernel		igc3: <Intel(R) Ethernet Controller I225-V> mem 0x50400000-0x504fffff,0x50500000-0x50503fff at device 0.0 on pci5
Dec 1 14:45:34	kernel		igc3: Using 1024 TX descriptors and 1024 RX descriptors
Dec 1 14:45:34	kernel		igc3: Using 2 RX queues 2 TX queues
Dec 1 14:45:34	kernel		igc3: Using MSI-X interrupts with 3 vectors
Dec 1 14:45:34	kernel		igc3: Ethernet address: 60:be:b4:02:e3:45
Dec 1 14:45:34	kernel		igc3: netmap queues/slots: TX 2/1024, RX 2/1024
Dec 1 14:45:34	kernel		lo0: link state changed to UP
Dec 1 14:45:38	check_reload_status	439	Linkup starting igc0
Dec 1 14:45:38	kernel		igc0: link state changed to UP
Dec 1 14:45:38	check_reload_status	439	rc.newwanip starting igc0
Dec 1 14:45:38	php-cgi	474	rc.bootup: Resyncing OpenVPN instances.
Dec 1 14:45:39	kernel		pflog0: promiscuous mode enabled
Dec 1 14:45:39	php-cgi	474	rc.bootup: Removing static route for monitor 8.8.8.8 and adding a new route through 192.121.XXX.1
Dec 1 14:45:39	kernel		.done.
Dec 1 14:45:39	kernel		done.
Dec 1 14:45:39	php-cgi	474	rc.bootup: Gateway, NONE AVAILABLE
Dec 1 14:45:39	php-cgi	474	rc.bootup: Default gateway setting Interface WAN_DHCP Gateway as default.
Dec 1 14:45:39	php-cgi	474	rc.bootup: The command '/sbin/route -n6 get 'default' 2>/dev/null | /usr/bin/egrep 'flags: <.*PROTO.*>'' returned exit code '1', the output was ''
Dec 1 14:45:39	php-fpm	399	/rc.newwanip: rc.newwanip: Info: starting on igc0.
Dec 1 14:45:39	kernel		done.
Dec 1 14:45:39	php-fpm	399	/rc.newwanip: rc.newwanip: on (IP address: 192.121.XXX.95) (interface: WAN[wan]) (real interface: igc0).
Dec 1 14:45:39	php-fpm	399	/rc.newwanip: Removing static route for monitor 8.8.8.8 and adding a new route through 192.121.XXX.1
Dec 1 14:45:39	php-cgi	474	rc.bootup: sync unbound done.
Dec 1 14:45:39	kernel		done.
Dec 1 14:45:39	kernel		done.
Dec 1 14:45:42	rc.gateway_alarm	86534	>>> Gateway alarm: WAN_DHCP (Addr:8.8.8.8 Alarm:1 RTT:7.380ms RTTsd:0ms Loss:50%)
Dec 1 14:45:42	check_reload_status	439	updating dyndns WAN_DHCP
Dec 1 14:45:42	check_reload_status	439	Restarting IPsec tunnels
Dec 1 14:45:42	check_reload_status	439	Restarting OpenVPN tunnels/interfaces
Dec 1 14:45:42	check_reload_status	439	Reloading filter
Dec 1 14:45:43	check_reload_status	439	Linkup starting igc1
Dec 1 14:45:43	kernel		igc1: link state changed to UP
Dec 1 14:45:44	php-fpm	400	/rc.linkup: Ignoring link event during boot sequence.
Dec 1 14:46:10	php-cgi	474	rc.bootup: NTPD is starting up.
Dec 1 14:46:10	kernel		done.
Dec 1 14:46:11	kernel		done.
Dec 1 14:46:11	check_reload_status	439	Updating all dyndns
Dec 1 14:46:11	php-cgi	474	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).'
Dec 1 14:46:11	kernel		.done.
Dec 1 14:46:17	php-fpm	400	/rc.start_packages: Restarting/Starting all packages.
Dec 1 14:46:17	root	96391	Bootup complete

jrey

@AcidSleeper

The answer has to be right there, but I'm not spotting it.

Reviewing everything you have provided, and just noticed another rule, that is not out of box on the LAN tab. for the IPv4 you have * (any) for source, out of box this would be "LAN subnets" like the IPv6 rule below it. Should not make a difference (but I didn't test it) so more just an observation at this point.

as it sits right now, your WAN IP is 192.121.xx.95 and the gateway should be 192.121.x.1

from the Diagnostics / Ping page can you ping both of those and get a response?

AcidSleeper

@jrey I change the rule as you requested.

I will try and ping theese ip tomorrow. The whole family is using the Internet as the Asus-router is plugged in the Wan-port of the mediaconverter right now.

I will return tomorrow! Thanks for all the troubleshooting so far!

jrey

@AcidSleeper

Of course - no problem.

What other packages if any do you have installed and running?

After a reboot any services showing as not running?

jrey

@AcidSleeper

My test machine is a virtual, so I can virtually mess with it.

so the system is currently running and an I disconnect the WAN Cable.
Screen Shot 2023-12-01 at 2.42.44 PM.png

Note the system does not say OffLine -- the gateway just goes Pending and Unknown -what I'd expect ..

The interface is autoselect. (should be)

virtually plug it back in and it instantly negotiates the connection.

Screen Shot 2023-12-01 at 2.43.42 PM.png

are you using the same cable when going from
mc <-> asus
as you do when going from
mc <-> pf
if it is the same cable that's fine, but if different (and even if not) are you getting the same negotiated speed/duplex on both devices (asus and pf)
do you need to restart the MC (or should you?) or just swapping the cable?

curiosity questions

AcidSleeper

First answear your questions:

its the same cabel and Im getting 1000baseT from Wan. My laptop is old so it only got 100baseTX. I also have changed tha cabel from Cat5, Cat5e and Cat6 and different lengths.
When I remove the cabel the gateway goes to Pending and Unknown. Like yours.
I got no installed packages except Watchdog.

My morning work:
I couldnt sleep so at 06:00 I had an idea.

What if the mediaconverter (Inteno) cant handle more than a couple of mac-adresses, and its locked at my Asus and my computer that has been connected recently to the mediaconverter before my pfsense-box.

Cant hurt to try: So I connected my computer, got an IP and with commandpromt I wrote "ipconfig /release". No ip and removed the Wan-cabel from my computer.

Started up my pfsense without wan-cabel and had it running when I put the wan-cabel in the pfsense-box. Voila! Gateway Online.
But have to try a reboot. No problems there.
But have to try and removed the wan-cabel and place it back in. No problems here either.

Is it this that have been the problem the whole time. Some kind of macadress-lock? What do you think?

BUT I called to soon, there is still some problem. Had 4hours to play around. I remove the cabel and then I dont get gateway online again when I place it back in. I do it again and Gateway says Online.
But I cant browse the internet.
From pfsense I can ping and do traceroutes from ip-adresses and www-adresses. But if I try to browse the internet it wont work. I reboot, gateway Online but no internet. Remove the cabel again and plug in back in. Gateway is Online but no Internet. Can ping etc. DO a reboot again, no change except gateway offline. Another reboot and gateway online and I can browse the Internet.

Something is very strange.

AcidSleeper

@jrey forgot to reply to you in my above post.

When I reboot without Wan-cable in the pfsense it boots up without running the dpinger in services, it is "stopped".

So when I plug in my wan-cable everything works. Is dpinger the fault?

jrey

@AcidSleeper

2 items, MAC and Watchdog. (try watchdog change first)

MAC
so then (are they requiring a specific MAC address?)

rephrase that to be ia the MediaConverter requiring a specific MAC.
just so there is no confusion about which device possibly requiring it.

of course you can just tell pfSense to use the same MAC as the asus. if you want.

record the MAC addy the asus is using to connect to the MC.
enter that on the WAN screen. (sorry screen capture is from my production so forget that it says Static IP, (leave yours at DHCP)
Screen Shot 2023-12-02 at 6.11.24 AM.png

Watchdog. "Service_Watchdog"? it will conflict with dpinger that monitors the connection. if that is the only package/service you have installed just remove WD. I have a few packages/Services running on Prod, and have never found the need to run WD, so not even installed here.

AcidSleeper

@jrey

WatchDog removed and rebooted twice. No change.

I have tried the Mac-spoofing before. Didnt make a change either. Tried it again. Rebooted. Nope.

jrey

@AcidSleeper said in Always Wan-ip but gateway is 100% packet loss:

rebooted twice.

rebooted what? possible both devices need a power cycle.

MC first, give it time to start up, then pfSense

from your "can't sleep" post above it appears it was working? (or am I in need of more coffee and reading that wrong)

then let's look at a current set of logs from that sequence.

what's the make/model of the network card in the pfSense box?

AcidSleeper

@jrey said in Always Wan-ip but gateway is 100% packet loss:

rebooted what? possible both devices need a power cycle.

MC first, give it time to start up, then pfSense

Done that. Still no change.

from your "can't sleep" post above it appears it was working? (or am I in need of more coffee and reading that wrong)

Yes it was working and have been working but a reboot can make it go away any second.

then let's look at a current set of logs from that sequence.

To bad the logs from that time is long gone. Only 500 rows in log. =/

what's the make/model of the network card in the pfSense box?

Its 4x Intel i225-V 2.5Gbs

AcidSleeper

@jrey I have now attached my asus router to MC and pfsense to asus.

MC --> Asus --> Pfsense.

It seems like it can handle everything I do to it. Reboots, remove wan-cable (pfsense/asus), reboot without wan-cable and attach it when pfsense is up and running.

Every time the gateway goes online and I can browse the internet.

Talked to my ISP and they say the only setting I need to do is DHCP. Nothing else and I even mentioned that Im using pfsense but no settings for pfsense either.

jrey

@AcidSleeper

Interesting
so this the summary

MC - Asus works
MC - pfSense fails
MC - Asus - pfSense works

it's almost like the network card in the pfSense is not compatible with the MC (similar cases have been noted)

do you have a small hub/switch that you can put between the MC and pfSense to test?

AcidSleeper

@jrey Yes I have a dumb switch that I can place in between. Will try that as soon as family leaves me alone with the internet! =)

Thanks yet again.

AcidSleeper

@jrey Hey, tried with a dumb switch (TP-Link SG105) between pfsense and Inteno (MC) but no change. Same behavior. Its like the hardware inside Pfsense cant tolerate (I know, I cant tolerate some people sometimes either) the Inteno relaying DHCP OR my ISP dhcp to Pfsense. I dont know, just throwing out ideas.

Here are som logs anyways:

Logs from General and DHCP - pfsense-random logs.txt
Log from General, show booting, no Internet, pull wan-cabel, plug it back in and got Internet (full functionality - pfsense-Boot-NoInternet-Internet.txt

jrey

@AcidSleeper

So there have been a bunch of previous discussions about the I225-V
needing certain hardware revisions (you can search the forum for those)

setting parameters (
Disable hardware checksum offload
Disable hardware TCP segmentation offload
Disable hardware large receive offload
)

patches etc (all patches I would have thought are in 2.7.1 )

I don't have one and isn't an option for me to emulate, so..

you might want to run this on a command prompt

pciconf -vl

I'm not seeing an error on the icg loads however.
The boot sequence does imply you are getting an IP (.21) in that sequence and gateway (.1)

the .2 and .3 DHCP sequence seems odd, (the sequence at 7:43 is one example)
although it appears you get a OFFER from .2 and .3 after several DHCPNAK from .3 - .2 is always giving you the IP.

AcidSleeper

@jrey said in Always Wan-ip but gateway is 100% packet loss:

@AcidSleeper

So there have been a bunch of previous discussions about the I225-V
needing certain hardware revisions (you can search the forum for those)

setting parameters (
Disable hardware checksum offload
Disable hardware TCP segmentation offload
Disable hardware large receive offload
)

Didnt have "Disable hardware checksum offload" crossed. A friend also said that and I have tried that before but not with a dumb switch. Now it is CHECKED. Will try again with a dumb switch in between Inteno and Pfsense.

patches etc (all patches I would have thought are in 2.7.1 )

I don't have one and isn't an option for me to emulate, so..

I have read much of it too but it seems like the Intel i225-V is working with pfsense 2.7.1, according to what I read. But maybe I am the exception!

you might want to run this on a command prompt
pciconf -vl

hostb0@pci0:0:0:0:	class=0x060000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x9a04 subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    class      = bridge
    subclass   = HOST-PCI
vgapci0@pci0:0:2:0:	class=0x030000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x9a78 subvendor=0x8086 subdevice=0x2212
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP GT2 [UHD Graphics G4]'
    class      = display
    subclass   = VGA
none0@pci0:0:4:0:	class=0x118000 rev=0x01 hdr=0x00 vendor=0x8086 device=0x9a03 subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'TigerLake-LP Dynamic Tuning Processor Participant'
    class      = dasp
pcib1@pci0:0:6:0:	class=0x060400 rev=0x01 hdr=0x01 vendor=0x8086 device=0x9a09 subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = '11th Gen Core Processor PCIe Controller'
    class      = bridge
    subclass   = PCI-PCI
xhci0@pci0:0:13:0:	class=0x0c0330 rev=0x01 hdr=0x00 vendor=0x8086 device=0x9a13 subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP Thunderbolt 4 USB Controller'
    class      = serial bus
    subclass   = USB
xhci1@pci0:0:20:0:	class=0x0c0330 rev=0x20 hdr=0x00 vendor=0x8086 device=0xa0ed subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP USB 3.2 Gen 2x1 xHCI Host Controller'
    class      = serial bus
    subclass   = USB
none1@pci0:0:20:2:	class=0x050000 rev=0x20 hdr=0x00 vendor=0x8086 device=0xa0ef subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP Shared SRAM'
    class      = memory
    subclass   = RAM
none2@pci0:0:22:0:	class=0x078000 rev=0x20 hdr=0x00 vendor=0x8086 device=0xa0e0 subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP Management Engine Interface'
    class      = simple comms
ahci0@pci0:0:23:0:	class=0x010601 rev=0x20 hdr=0x00 vendor=0x8086 device=0xa0d3 subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP SATA Controller'
    class      = mass storage
    subclass   = SATA
pcib2@pci0:0:28:0:	class=0x060400 rev=0x20 hdr=0x01 vendor=0x8086 device=0xa0bc subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP PCI Express Root Port'
    class      = bridge
    subclass   = PCI-PCI
pcib3@pci0:0:28:5:	class=0x060400 rev=0x20 hdr=0x01 vendor=0x8086 device=0xa0bd subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'Tigerlake PCH-LP PCI Express Root Port'
    class      = bridge
    subclass   = PCI-PCI
pcib4@pci0:0:28:6:	class=0x060400 rev=0x20 hdr=0x01 vendor=0x8086 device=0xa0be subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP PCI Express Root Port'
    class      = bridge
    subclass   = PCI-PCI
pcib5@pci0:0:28:7:	class=0x060400 rev=0x20 hdr=0x01 vendor=0x8086 device=0xa0bf subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP PCI Express Root Port'
    class      = bridge
    subclass   = PCI-PCI
isab0@pci0:0:31:0:	class=0x060100 rev=0x20 hdr=0x00 vendor=0x8086 device=0xa082 subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP LPC Controller'
    class      = bridge
    subclass   = PCI-ISA
hdac0@pci0:0:31:3:	class=0x040300 rev=0x20 hdr=0x00 vendor=0x8086 device=0xa0c8 subvendor=0x10ec subdevice=0x3000
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP Smart Sound Technology Audio Controller'
    class      = multimedia
    subclass   = HDA
ichsmb0@pci0:0:31:4:	class=0x0c0500 rev=0x20 hdr=0x00 vendor=0x8086 device=0xa0a3 subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP SMBus Controller'
    class      = serial bus
    subclass   = SMBus
none3@pci0:0:31:5:	class=0x0c8000 rev=0x20 hdr=0x00 vendor=0x8086 device=0xa0a4 subvendor=0x8086 subdevice=0x7270
    vendor     = 'Intel Corporation'
    device     = 'Tiger Lake-LP SPI Controller'
    class      = serial bus
nvme0@pci0:1:0:0:	class=0x010802 rev=0x03 hdr=0x00 vendor=0x126f device=0x2263 subvendor=0x126f subdevice=0x2263
    vendor     = 'Silicon Motion, Inc.'
    device     = 'SM2263EN/SM2263XT SSD Controller'
    class      = mass storage
    subclass   = NVM
igc0@pci0:2:0:0:	class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x15f3 subvendor=0x8086 subdevice=0x0000
    vendor     = 'Intel Corporation'
    device     = 'Ethernet Controller I225-V'
    class      = network
    subclass   = ethernet
igc1@pci0:3:0:0:	class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x15f3 subvendor=0x8086 subdevice=0x0000
    vendor     = 'Intel Corporation'
    device     = 'Ethernet Controller I225-V'
    class      = network
    subclass   = ethernet
igc2@pci0:4:0:0:	class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x15f3 subvendor=0x8086 subdevice=0x0000
    vendor     = 'Intel Corporation'
    device     = 'Ethernet Controller I225-V'
    class      = network
    subclass   = ethernet
igc3@pci0:5:0:0:	class=0x020000 rev=0x03 hdr=0x00 vendor=0x8086 device=0x15f3 subvendor=0x8086 subdevice=0x0000
    vendor     = 'Intel Corporation'
    device     = 'Ethernet Controller I225-V'
    class      = network
    subclass   = ethernet

I'm not seeing an error on the icg loads however.
The boot sequence does imply you are getting an IP (.21) in that sequence and gateway (.1)

the .2 and .3 DHCP sequence seems odd, (the sequence at 7:43 is one example)
although it appears you get a OFFER from .2 and .3 after several DHCPNAK from .3 - .2 is always giving you the IP.

Did find out the my Asus is using dnsmasq and Pfsense if using Unbound. Just a thought. Can DNS Resolver (Unbound) be the problem that its no configured right or must I use DNS Forwarder?

AcidSleeper

@jrey

jrey

@AcidSleeper

Do you have a DNS Server set on the System -> General Settings page ?
what is it?

as for DNS Resolver it will resolve directly out of the box. No changes required. unbound is great.

Not being able to Resolve would not bring the gateway down. would just mean when the gateway is up you wouldn't be able to find sites by name --- a direct ping to an IP should go through.

The rev=0x03 on the network cards from what I understand regarding that card is a good thing.

I sent you an IM on another item (unrelated to this) earlier - did you see that?