Network partially bad working (inconsitent ping long loading webpages)

Hello,

after just changing the power outlets and powering down the whole Infotainment and network hardware i got some problems after restarting (did it multiple times menawhile).

The problem is, taht i can download without problems and 45 MB/s on a 400 Mbit/s connection. No worries there. Calling webpages on the other hand gives sometimes errors and sometimes takes very long.
I tried pinging google.com and i get 3 pings with 20 to 30 ms, then 3 timeouts, 2 pings again with 20 to 30 ms, then a couple of timeouts again. looks like this (sorry, in german: Zeitüberschreitung der Anforderung=Request Timeout):

Ping wird ausgeführt für google.com [216.58.215.46] mit 32 Bytes Daten:
Antwort von 216.58.215.46: Bytes=32 Zeit=23ms TTL=49
Antwort von 216.58.215.46: Bytes=32 Zeit=23ms TTL=49
Antwort von 216.58.215.46: Bytes=32 Zeit=35ms TTL=49
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Antwort von 216.58.215.46: Bytes=32 Zeit=23ms TTL=49
Antwort von 216.58.215.46: Bytes=32 Zeit=23ms TTL=49
Antwort von 216.58.215.46: Bytes=32 Zeit=24ms TTL=49
Antwort von 216.58.215.46: Bytes=32 Zeit=29ms TTL=49
Antwort von 216.58.215.46: Bytes=32 Zeit=23ms TTL=49
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Zeitüberschreitung der Anforderung.
Antwort von 216.58.215.46: Bytes=32 Zeit=23ms TTL=49
Antwort von 216.58.215.46: Bytes=32 Zeit=26ms TTL=49
Antwort von 216.58.215.46: Bytes=32 Zeit=26ms TTL=49
Antwort von 216.58.215.46: Bytes=32 Zeit=26ms TTL=49
Antwort von 216.58.215.46: Bytes=32 Zeit=41ms TTL=49
Zeitüberschreitung der Anforderung.

Zeitüberschreitung der Anforderung.

Pinging the IP 216.58.215.46 direct instead of the url gives only timeouts.
Pinging the Openwrt router @ 192.168.1.1 works with 1 ms pings
Pinging everything (but the cablemodem) @192.168.1.* connected to the openwrt router gives me 1 ms pings
Pinging the Cablemodem @ 192.168.0.1 gives me 1 to 3 ms pings and timeouts.

The problem seems to be within the connection of cablemodem and openwrt router

Whats going wrong?

The Openwrt router 192.168.1.1 is connected via WAN port to the ISPs cablemodem router (192.168.0.1 unfortunately no way around that),

My network config (ula prefix repalced with xs by me):

config interface 'loopback'
        option ifname 'lo'
        option proto 'static'
        option ipaddr '127.0.0.1'
        option netmask '255.0.0.0'

config globals 'globals'
        option ula_prefix xxxx:xxxx:xxxx::/48'

config interface 'lan'
        option type 'bridge'
        option ifname 'lan1 eth2.101'
        option proto 'static'
        option ipaddr '192.168.1.1'
        option netmask '255.255.255.0'
        option ip6assign '60'

config interface 'wan'
        option type 'bridge'
        option ifname 'wan eth2.102'
        option proto 'dhcp'

config interface 'wan6'
        option ifname 'br-wan'
        option proto 'dhcpv6'

I apreciate any help. thx!

Try a new network cable between modem and LEDE box?

No, different cable, same problem...

I don't see any DNS servers assigned in the WAN interface.

list dns '8.8.8.8'
list dns '8.8.4.4'
added in WAN section, network reloaded, no change...

I also branched the whole network to the ISP cablemodem router and there its working like it should.
Must be a problem between Openwrt router and cablemodem router.

I would suspect configuration.

On the cable modem -

Turn off DHCP, firewall, and wireless
Set the connection to bridge. If it doesn't have bridge, look for IP passthrough.

On the router running OpenWrt/LEDE -

Should be doing DHCP, firewall functionality, and wireless.

Can't configure much on cablemodem. Pretty much restricted.

But what bothers me: The same configuration was working fine before i unpluged power, so it shouldn't be a configuration problem?

I would power off each device, one at a time, for several minutes, then power back on in the same order.

Start with the cable modem, then the router, then each device.

While a device is off, check that all cable connections are tight.

Did that already before but perhaps i didn't wait long enough (only 30 seconds). Did it again and so far it seems to be working again. So just some network hickups...?

I usually wait a few minutes.

Good to hear it's working.