Od1n Posted December 26, 2020 Share Posted December 26, 2020 Hey guys, i noticed that i recently have a port forwarding issue (i assume its a double nat problem?) where my game request ports from the R1 and they also show up in the UPnP of the R1. However the ports are never truly opened as the game continues to show "open port bla bla - strict nat". Now what i noticed is that my R1 shows a completely wrong Device Manager picture and i assume this is part of the issue. For reference, im using a Fritzbox router with DHCP wired to the R1 (latest official DumaOS, not the beta one). The R1 is set to exposed host in the Fritzbox for both IPv4 and IPv6. The PS5 is connected via dLan to the R1, same goes to my PC. ALL other devices except for these two are connected wirelessly to the R1. As you can see below the picture shows an entirely different story. All devices are connected to the Fritzbox (Router) either wired or wireless, and funnily the Fritzbox has its Wifi deactivated. I didnt have these problems when the R1 showed the correct Device Manager picture. Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted December 26, 2020 Administrators Share Posted December 26, 2020 The router in the picture represents the DumaOS router, it isn't a dynamic picture, it always shows a router connected to a modem as a general representation of the network. You can tell the router represents the DumaOS router as the Netduma R1 WiFi branches from it so this has nothing to do with your issue. Most likely what you need to do on the Fritzbox is disable its Firewall and DMZ and then see if you get an open NAT. Link to comment Share on other sites More sharing options...
Od1n Posted December 28, 2020 Author Share Posted December 28, 2020 its impossible to deactivate the firewall of a Fritzbox though, all you can do is open ports and thats it. I can try deactivating the DMZ but i dont think i have set the R1 into the DMZ. Anything else i can do? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted December 28, 2020 Administrators Share Posted December 28, 2020 If you haven't yet put the R1 into the DMZ then do that then reboot the R1. If you have then take it out and make a port forwarding rule 1-65535 TCP/UDP to the R1 and see if you get an Open NAT then. Link to comment Share on other sites More sharing options...
Od1n Posted December 28, 2020 Author Share Posted December 28, 2020 You can only open one port at a time on the Fritzbox, its not possible to declare one rule that opens port 1-65535. Setting up a DMZ with a Fritzbox is also not possible, what you can do however is to set the R1 as the exposed host for IPv4 and IPv6. The Fritzbox will then open all ports plus remove the firewall for that device. I also ticked the box for "allow this device to portforward by itself via PCP or UPnP". This is what i have used so far but it wont work, the UPnP of the R1 shows it requests 3 ports (see below) but the Fritzbox shows 0 requested ports from the R1. There must be a communication missmatch between the two, how can i solve this? Fritzbox and R1 are communicating via DHCP. Requested by R1 in UPnP (with the Fritzbox showing 0 requested ports at the same time and the game showing a Strict Nat PMP error): 192.168.88.243 PlayStation 192.168.88.243 9308 9308 UDP NAT-PMP 4955 udp PlayStation 192.168.88.243 4955 4955 UDP NAT-PMP 4950 udp PlayStation 192.168.88.243 4950 4950 UDP Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted December 28, 2020 Administrators Share Posted December 28, 2020 You can't port forward an entire range? What's the exact model of the Fritzbox? That will help me figure out a better solution perhaps. Did you give the R1 a static/reserved IP on the fritzbox? Is it possible the IP has changed so the exposed host is no longer valid? Link to comment Share on other sites More sharing options...
Od1n Posted December 29, 2020 Author Share Posted December 29, 2020 Yes its really annoying that you cannot do that. But via the exposed host all ports should be open anyway, no? I assigned the R1 a static IP via the Fritzbox (theres an option for that) and the IP hasnt changed since then The model is Fritzbox 7530, thanks for your help Fraser! Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted December 29, 2020 Administrators Share Posted December 29, 2020 It should be yes, so something is definitely amiss! Okay so I just looked it up and it could be that their Firewall is interfering with it, could you disable this fully please (fine to do as the R1 has its own built in Firewall) and see if that works please? Link to comment Share on other sites More sharing options...
THarris23 Posted December 29, 2020 Share Posted December 29, 2020 What’s the difference between the R1& R2 if I have the OS on the R1? Link to comment Share on other sites More sharing options...
Od1n Posted December 29, 2020 Author Share Posted December 29, 2020 4 hours ago, Netduma Fraser said: It should be yes, so something is definitely amiss! Okay so I just looked it up and it could be that their Firewall is interfering with it, could you disable this fully please (fine to do as the R1 has its own built in Firewall) and see if that works please? The problem is that there is no way to deactivate the Firewall, this is explicitly mentioned in the online manual and there are only two workaround options: - use the Firtzbox as a client connected to another router that acts as the main router ---> Fritzbox will automatically completely deactivate the firewall - use the exposed host feature for IPv4 and IPv6 which says in the interface it will deactivate the firewall, but this doesnt seem to be the case as otherwise i wouldnt have these issues Btw im using the latest Non-Beta DumaOS if that is relevant. Im pretty sure im not the only one with this problem, the Fritzbox is Germanys most common router and they basically all share the same interface and features. Anything else i could try? Maybe its a DHCP misscommunication? I mean there must be a reason for why the Fritzbox shows 0 requested ports while the R1 requests 3 different ones Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted December 29, 2020 Administrators Share Posted December 29, 2020 I don't think this is applicable for you but have a look here, may give some more insight on what other options you can do https://en.avm.de/service/fritzbox/fritzbox-7530/knowledge-base/publication/show/106_Setting-up-the-FRITZ-Box-for-use-with-another-router/ Link to comment Share on other sites More sharing options...
Od1n Posted January 16, 2021 Author Share Posted January 16, 2021 Hey Fraser, so i tried a lot of additional stuff over the last weeks but it seems like DHCP with a Fritzbox and Netduma router will always result in a strict NAT. Because of that i wanted to switch back to PPPoE, which is what i used previously with my Fritzbox and the Netduma router. This results in an open NAT, however since i havent done the setup steps for several years now i seem to run into some issues. Maybe you can tell me what i forgot to do, i included a system information output at the bottom. 1) Fritzbox configured to allow PPPoE. This is really easy and can be done with 3 clicks, instruction steps here: https://en.avm.de/service/fritzbox/fritzbox-7530/knowledge-base/publication/show/3232_Configuring-PPPoE-passthrough-in-the-FRITZ-Box/ 2) Go into the DumaOS interface and under LAN deactivate DHCP in the network settings 3) Then go network settings and under WAN you switch from DHCP to PPPoE. The login credentials are 100% correct. The MTU, MAC Cloning and DNS option are unticked there. Am i missing something? I surely must have forgotten something as PPPoE is what i was using for years with the Fritzbox and R1 until i switched to DHCP in hope to reduce the R1 CPU load. System Information output: Spoiler Sat Jan 16 12:36:37 2021 kern.info kernel: [ 3810.640000] recv: nf_ct_get failed Sat Jan 16 12:36:36 2021 kern.info kernel: [ 3809.440000] recv: nf_ct_get failed Sat Jan 16 12:36:35 2021 kern.info kernel: [ 3808.840000] recv: nf_ct_get failed Sat Jan 16 12:36:35 2021 kern.info kernel: [ 3808.540000] recv: nf_ct_get failed Sat Jan 16 12:36:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:36:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:36:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:36:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:36:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:36:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:36:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:36:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:36:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:36:35 2021 kern.info kernel: [ 3808.168000] recv: nf_ct_get failed Sat Jan 16 12:36:32 2021 daemon.notice pppd[9075]: pppd 2.4.6 started by root, uid 0 Sat Jan 16 12:36:32 2021 daemon.info pppd[9075]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.6 Sat Jan 16 12:36:32 2021 daemon.info pppd[9075]: Plugin rp-pppoe.so loaded. Sat Jan 16 12:36:31 2021 daemon.notice netifd: Interface 'wan' has link connectivity Sat Jan 16 12:36:31 2021 daemon.notice netifd: VLAN 'eth0.2' link is up Sat Jan 16 12:36:31 2021 daemon.notice netifd: Interface 'wan' has link connectivity loss Sat Jan 16 12:36:31 2021 daemon.notice netifd: VLAN 'eth0.2' link is down Sat Jan 16 12:36:31 2021 daemon.notice netifd: Interface 'wan' is setting up now Sat Jan 16 12:36:31 2021 daemon.notice netifd: Interface 'wan' is enabled Sat Jan 16 12:36:31 2021 daemon.notice netifd: Interface 'wan' is disabled Sat Jan 16 12:36:31 2021 kern.info kernel: [ 3804.808000] device going down notification eth0.2 Sat Jan 16 12:36:31 2021 kern.info kernel: [ 3804.808000] device going down notification eth0.2 Sat Jan 16 12:36:31 2021 daemon.notice netifd: Interface 'wan' is now down Sat Jan 16 12:36:31 2021 daemon.info pppd[8354]: Exit. Sat Jan 16 12:36:31 2021 daemon.err pppd[8354]: Couldn't rename ppp1 to pppoe-wan Sat Jan 16 12:36:31 2021 daemon.warn pppd[8354]: Connected to dc:39:6f:ee:bc:a3 via interface eth0.2 Sat Jan 16 12:36:31 2021 daemon.info pppd[8354]: PPP session is 263 Sat Jan 16 12:36:31 2021 kern.info kernel: [ 3804.460000] recv: nf_ct_get failed Sat Jan 16 12:36:30 2021 kern.info kernel: [ 3803.696000] send: nf_ct_get failed Sat Jan 16 12:36:30 2021 kern.info kernel: [ 3803.696000] recv: nf_ct_get failed Sat Jan 16 12:36:28 2021 kern.info kernel: [ 3801.844000] send: nf_ct_get failed Sat Jan 16 12:36:28 2021 kern.info kernel: [ 3801.844000] recv: nf_ct_get failed Sat Jan 16 12:36:24 2021 kern.info kernel: [ 3797.640000] send: nf_ct_get failed Sat Jan 16 12:36:24 2021 kern.info kernel: [ 3797.640000] recv: nf_ct_get failed Sat Jan 16 12:36:24 2021 kern.info kernel: [ 3796.880000] send: nf_ct_get failed Sat Jan 16 12:36:24 2021 kern.info kernel: [ 3796.880000] recv: nf_ct_get failed Sat Jan 16 12:36:23 2021 kern.info kernel: [ 3796.788000] send: nf_ct_get failed Sat Jan 16 12:36:23 2021 kern.info kernel: [ 3796.788000] recv: nf_ct_get failed Sat Jan 16 12:36:23 2021 kern.info kernel: [ 3796.080000] recv: nf_ct_get failed Sat Jan 16 12:36:22 2021 kern.info kernel: [ 3795.776000] recv: nf_ct_get failed Sat Jan 16 12:36:22 2021 kern.info kernel: [ 3795.168000] recv: nf_ct_get failed Sat Jan 16 12:36:21 2021 kern.info kernel: [ 3794.812000] recv: nf_ct_get failed Sat Jan 16 12:36:21 2021 kern.info kernel: [ 3794.436000] recv: nf_ct_get failed Sat Jan 16 12:36:20 2021 kern.info kernel: [ 3793.368000] recv: nf_ct_get failed Sat Jan 16 12:36:20 2021 kern.info kernel: [ 3792.856000] recv: nf_ct_get failed Sat Jan 16 12:36:19 2021 daemon.notice pppd[8354]: pppd 2.4.6 started by root, uid 0 Sat Jan 16 12:36:19 2021 daemon.info pppd[8354]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.6 Sat Jan 16 12:36:19 2021 daemon.info pppd[8354]: Plugin rp-pppoe.so loaded. Sat Jan 16 12:36:19 2021 daemon.notice netifd: Interface 'wan' has link connectivity Sat Jan 16 12:36:19 2021 daemon.notice netifd: VLAN 'eth0.2' link is up Sat Jan 16 12:36:19 2021 daemon.notice netifd: Interface 'wan' has link connectivity loss Sat Jan 16 12:36:19 2021 daemon.notice netifd: VLAN 'eth0.2' link is down Sat Jan 16 12:36:19 2021 daemon.notice netifd: Interface 'wan' is setting up now Sat Jan 16 12:36:19 2021 daemon.notice netifd: Interface 'wan' is enabled Sat Jan 16 12:36:19 2021 daemon.notice netifd: Interface 'wan' is disabled Sat Jan 16 12:36:19 2021 kern.info kernel: [ 3792.264000] device going down notification eth0.2 Sat Jan 16 12:36:19 2021 kern.info kernel: [ 3792.264000] device going down notification eth0.2 Sat Jan 16 12:36:19 2021 daemon.notice netifd: Interface 'wan' is now down Sat Jan 16 12:36:19 2021 daemon.info pppd[7062]: Exit. Sat Jan 16 12:36:19 2021 daemon.err pppd[7062]: Unable to complete PPPoE Discovery Sat Jan 16 12:36:19 2021 daemon.warn pppd[7062]: Timeout waiting for PADS packets Sat Jan 16 12:36:19 2021 kern.info kernel: [ 3791.952000] recv: nf_ct_get failed Sat Jan 16 12:36:18 2021 kern.info kernel: [ 3791.216000] send: nf_ct_get failed Sat Jan 16 12:36:18 2021 kern.info kernel: [ 3791.216000] recv: nf_ct_get failed Sat Jan 16 12:36:16 2021 kern.info kernel: [ 3789.144000] recv: nf_ct_get failed Sat Jan 16 12:36:15 2021 kern.info kernel: [ 3788.452000] recv: nf_ct_get failed Sat Jan 16 12:36:13 2021 kern.info kernel: [ 3786.300000] recv: nf_ct_get failed Sat Jan 16 12:36:12 2021 kern.info kernel: [ 3785.436000] recv: nf_ct_get failed Sat Jan 16 12:36:11 2021 kern.info kernel: [ 3784.052000] recv: nf_ct_get failed Sat Jan 16 12:36:10 2021 kern.info kernel: [ 3783.792000] recv: nf_ct_get failed Sat Jan 16 12:36:10 2021 kern.info kernel: [ 3783.420000] recv: nf_ct_get failed Sat Jan 16 12:36:10 2021 kern.info kernel: [ 3783.416000] recv: nf_ct_get failed Sat Jan 16 12:36:10 2021 kern.info kernel: [ 3783.416000] recv: nf_ct_get failed Sat Jan 16 12:36:10 2021 kern.info kernel: [ 3783.412000] recv: nf_ct_get failed Sat Jan 16 12:36:10 2021 kern.info kernel: [ 3783.412000] recv: nf_ct_get failed Sat Jan 16 12:36:10 2021 kern.info kernel: [ 3783.412000] recv: nf_ct_get failed Sat Jan 16 12:36:10 2021 kern.info kernel: [ 3783.412000] recv: nf_ct_get failed Sat Jan 16 12:36:10 2021 kern.info kernel: [ 3783.412000] recv: nf_ct_get failed Sat Jan 16 12:36:09 2021 kern.info kernel: [ 3782.044000] recv: nf_ct_get failed Sat Jan 16 12:36:08 2021 kern.info kernel: [ 3781.708000] recv: nf_ct_get failed Sat Jan 16 12:36:08 2021 kern.info kernel: [ 3781.320000] recv: nf_ct_get failed Sat Jan 16 12:36:08 2021 kern.info kernel: [ 3781.276000] recv: nf_ct_get failed Sat Jan 16 12:36:08 2021 kern.info kernel: [ 3781.228000] send: nf_ct_get failed Sat Jan 16 12:36:08 2021 kern.info kernel: [ 3781.228000] recv: nf_ct_get failed Sat Jan 16 12:36:07 2021 kern.info kernel: [ 3779.916000] recv: nf_ct_get failed Sat Jan 16 12:36:05 2021 kern.info kernel: [ 3778.472000] send: nf_ct_get failed Sat Jan 16 12:36:05 2021 kern.info kernel: [ 3778.472000] recv: nf_ct_get failed Sat Jan 16 12:36:04 2021 kern.info kernel: [ 3777.788000] recv: nf_ct_get failed Sat Jan 16 12:36:02 2021 kern.info kernel: [ 3775.660000] recv: nf_ct_get failed Sat Jan 16 12:36:02 2021 kern.info kernel: [ 3774.968000] recv: nf_ct_get failed Sat Jan 16 12:36:02 2021 kern.info kernel: [ 3774.920000] recv: nf_ct_get failed Sat Jan 16 12:36:01 2021 kern.info kernel: [ 3774.596000] recv: nf_ct_get failed Sat Jan 16 12:36:01 2021 kern.info kernel: [ 3774.024000] recv: nf_ct_get failed Sat Jan 16 12:36:00 2021 kern.info kernel: [ 3773.492000] recv: nf_ct_get failed Sat Jan 16 12:36:00 2021 kern.info kernel: [ 3773.440000] recv: nf_ct_get failed Sat Jan 16 12:36:00 2021 kern.info kernel: [ 3773.348000] recv: nf_ct_get failed Sat Jan 16 12:36:00 2021 kern.info kernel: [ 3772.964000] recv: nf_ct_get failed Sat Jan 16 12:35:59 2021 kern.info kernel: [ 3772.000000] recv: nf_ct_get failed Sat Jan 16 12:35:58 2021 kern.info kernel: [ 3771.600000] recv: nf_ct_get failed Sat Jan 16 12:35:58 2021 kern.info kernel: [ 3771.272000] send: nf_ct_get failed Sat Jan 16 12:35:58 2021 kern.info kernel: [ 3771.272000] recv: nf_ct_get failed Sat Jan 16 12:35:58 2021 kern.info kernel: [ 3771.200000] recv: nf_ct_get failed Sat Jan 16 12:35:58 2021 user.info com.netdumasoftware.qos: applying qos for zone lan Sat Jan 16 12:35:58 2021 user.info com.netdumasoftware.qos: applying qos for zone wan Sat Jan 16 12:35:57 2021 kern.info kernel: [ 3770.320000] recv: nf_ct_get failed Sat Jan 16 12:35:57 2021 daemon.notice pppd[7062]: pppd 2.4.6 started by root, uid 0 Sat Jan 16 12:35:57 2021 daemon.info pppd[7062]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.6 Sat Jan 16 12:35:57 2021 daemon.info pppd[7062]: Plugin rp-pppoe.so loaded. Sat Jan 16 12:35:57 2021 kern.info kernel: [ 3769.892000] recv: nf_ct_get failed Sat Jan 16 12:35:56 2021 kern.info kernel: [ 3769.672000] recv: nf_ct_get failed Sat Jan 16 12:35:56 2021 daemon.notice netifd: Interface 'wan' has link connectivity Sat Jan 16 12:35:56 2021 daemon.notice netifd: VLAN 'eth0.2' link is up Sat Jan 16 12:35:56 2021 daemon.notice netifd: Interface 'wan' has link connectivity loss Sat Jan 16 12:35:56 2021 daemon.notice netifd: VLAN 'eth0.2' link is down Sat Jan 16 12:35:56 2021 daemon.notice netifd: Interface 'wan' is setting up now Sat Jan 16 12:35:56 2021 daemon.notice netifd: Interface 'wan' is enabled Sat Jan 16 12:35:56 2021 daemon.notice netifd: Interface 'wan' is disabled Sat Jan 16 12:35:56 2021 kern.info kernel: [ 3769.484000] device going down notification eth0.2 Sat Jan 16 12:35:56 2021 kern.info kernel: [ 3769.484000] device going down notification eth0.2 Sat Jan 16 12:35:56 2021 daemon.notice netifd: Interface 'wan' is now down Sat Jan 16 12:35:56 2021 kern.info kernel: [ 3769.456000] recv: nf_ct_get failed Sat Jan 16 12:35:56 2021 kern.info kernel: [ 3769.400000] recv: nf_ct_get failed Sat Jan 16 12:35:56 2021 kern.info kernel: [ 3769.308000] recv: nf_ct_get failed Sat Jan 16 12:35:56 2021 daemon.info pppd[6650]: Exit. Sat Jan 16 12:35:56 2021 daemon.err pppd[6650]: Couldn't rename ppp1 to pppoe-wan Sat Jan 16 12:35:56 2021 daemon.warn pppd[6650]: Connected to dc:39:6f:ee:bc:a3 via interface eth0.2 Sat Jan 16 12:35:56 2021 daemon.info pppd[6650]: PPP session is 263 Sat Jan 16 12:35:55 2021 kern.info kernel: [ 3768.664000] recv: nf_ct_get failed Sat Jan 16 12:35:54 2021 kern.info kernel: [ 3767.280000] recv: nf_ct_get failed Sat Jan 16 12:35:54 2021 kern.info kernel: [ 3767.188000] recv: nf_ct_get failed Sat Jan 16 12:35:54 2021 kern.info kernel: [ 3766.896000] recv: nf_ct_get failed Sat Jan 16 12:35:53 2021 kern.info kernel: [ 3766.120000] recv: nf_ct_get failed Sat Jan 16 12:35:53 2021 kern.info kernel: [ 3766.028000] recv: nf_ct_get failed Sat Jan 16 12:35:52 2021 kern.info kernel: [ 3765.688000] recv: nf_ct_get failed Sat Jan 16 12:35:52 2021 kern.info kernel: [ 3765.268000] recv: nf_ct_get failed Sat Jan 16 12:35:52 2021 kern.info kernel: [ 3764.984000] recv: nf_ct_get failed Sat Jan 16 12:35:51 2021 kern.info kernel: [ 3764.808000] recv: nf_ct_get failed Sat Jan 16 12:35:51 2021 kern.info kernel: [ 3764.532000] recv: nf_ct_get failed Sat Jan 16 12:35:51 2021 kern.info kernel: [ 3764.456000] recv: nf_ct_get failed Sat Jan 16 12:35:51 2021 kern.info kernel: [ 3764.448000] recv: nf_ct_get failed Sat Jan 16 12:35:51 2021 daemon.notice pppd[6650]: pppd 2.4.6 started by root, uid 0 Sat Jan 16 12:35:51 2021 daemon.info pppd[6650]: RP-PPPoE plugin version 3.8p compiled against pppd 2.4.6 Sat Jan 16 12:35:51 2021 daemon.info pppd[6650]: Plugin rp-pppoe.so loaded. Sat Jan 16 12:35:51 2021 kern.info kernel: [ 3763.944000] recv: nf_ct_get failed Sat Jan 16 12:35:51 2021 kern.info kernel: [ 3763.944000] recv: nf_ct_get failed Sat Jan 16 12:35:51 2021 kern.info kernel: [ 3763.944000] recv: nf_ct_get failed Sat Jan 16 12:35:50 2021 daemon.notice netifd: Interface 'wan6' is disabled Sat Jan 16 12:35:50 2021 daemon.notice netifd: Interface 'wan6' is now down Sat Jan 16 12:35:50 2021 daemon.notice odhcp6c[26430]: Send RELEASE message (elapsed 0ms, rc 0) Sat Jan 16 12:35:50 2021 daemon.notice odhcp6c[26430]: Starting RELEASE transaction (timeout 4294967295s, max rc 5) Sat Jan 16 12:35:50 2021 daemon.warn miniupnpd[26669]: SendNATPMPPublicAddressChangeNotification: cannot get public IP address, stopping Sat Jan 16 12:35:50 2021 daemon.err miniupnpd[26669]: Failed to get IP for interface eth0.2 Sat Jan 16 12:35:50 2021 daemon.err miniupnpd[26669]: ioctl(s, SIOCGIFADDR, ...): Cannot assign requested address Sat Jan 16 12:35:50 2021 daemon.notice netifd: Interface 'wan' is setting up now Sat Jan 16 12:35:50 2021 daemon.notice netifd: Interface 'wan' has link connectivity Sat Jan 16 12:35:50 2021 daemon.notice netifd: Interface 'wan' has link connectivity loss Sat Jan 16 12:35:50 2021 daemon.notice netifd: Interface 'wan' is now down Sat Jan 16 12:35:50 2021 daemon.notice netifd: wan (26370): Received SIGTERM Sat Jan 16 12:35:50 2021 daemon.warn dnsmasq[5609]: no servers found in /tmp/resolv.conf.auto, will retry Sat Jan 16 12:35:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:35:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:35:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:35:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:35:25 2021 daemon.info dnsmasq[5609]: read /tmp/hosts/odhcpd - 0 addresses Sat Jan 16 12:35:25 2021 daemon.info dnsmasq[5609]: read /tmp/hosts/dhcp - 0 addresses Sat Jan 16 12:35:25 2021 daemon.info dnsmasq[5609]: read /etc/hosts - 2 addresses Sat Jan 16 12:35:25 2021 daemon.info dnsmasq[5609]: using nameserver fd00::dea6:32ff:fec8:9423#53 Sat Jan 16 12:35:25 2021 daemon.info dnsmasq[5609]: using nameserver 192.168.178.27#53 Sat Jan 16 12:35:25 2021 daemon.info dnsmasq[5609]: using local addresses only for domain lan Sat Jan 16 12:35:25 2021 daemon.info dnsmasq[5609]: reading /tmp/resolv.conf.auto Sat Jan 16 12:35:25 2021 daemon.info dnsmasq[5609]: using local addresses only for domain lan Sat Jan 16 12:35:25 2021 daemon.info dnsmasq[5609]: compile time options: IPv6 GNU-getopt no-DBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP conntrack no-ipset no-auth no-DNSSEC Sat Jan 16 12:35:25 2021 daemon.info dnsmasq[5609]: started, version 2.71 cachesize 150 Sat Jan 16 12:35:25 2021 daemon.info dnsmasq[26558]: exiting on receipt of SIGTERM Sat Jan 16 12:35:05 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:35:05 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:35:05 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:35:05 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:35:05 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:34:47 2021 kern.info kernel: [ 3700.172000] recv: nf_ct_get failed Sat Jan 16 12:34:47 2021 kern.info kernel: [ 3700.168000] send: nf_ct_get failed Sat Jan 16 12:34:47 2021 kern.info kernel: [ 3700.168000] recv: nf_ct_get failed Sat Jan 16 12:34:33 2021 user.warn com.netdumasoftware.settings: Error opening wireless-mirror with error wireless-mirror: No such file or directory. Sat Jan 16 12:33:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:33:35 2021 kern.info dpiclass-daemon: Kill flow due to timeout Sat Jan 16 12:33:27 2021 daemon.info hostapd: wlan0: STA 9a:7b:27:5e:f6:70 WPA: group key handshake completed (RSN) Sat Jan 16 12:33:26 2021 daemon.info hostapd: wlan0: STA 58:cb:52:57:4a:1c WPA: group key handshake completed (RSN) Sat Jan 16 12:33:25 2021 daemon.info hostapd: wlan0: STA f0:81:73:53:ad:5c WPA: group key handshake completed (RSN) Sat Jan 16 12:33:25 2021 daemon.info hostapd: wlan0: STA f8:0f:f9:4d:b0:69 WPA: group key handshake completed (RSN) Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 16, 2021 Administrators Share Posted January 16, 2021 Do not deactivate DHCP in LAN Settings, that won't help at all and make it worse. Re-enable that and see if it works then please. Link to comment Share on other sites More sharing options...
Od1n Posted January 17, 2021 Author Share Posted January 17, 2021 With DHCP on in LAN it also wont work, would another system information log with DHCP on help? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 17, 2021 Administrators Share Posted January 17, 2021 What do you mean it won't work? Whats the issue when having the router handle PPPoE? Link to comment Share on other sites More sharing options...
Od1n Posted January 18, 2021 Author Share Posted January 18, 2021 I wont get any connection to the Internet, see my system information output above. PPPoE credentials are correct, i double checked on that. Same Fritzbox, same R1, same provider since the last time i used PPPoE with the R1. Back then i didnt use the DumaOS though but the last R1 firmware. Any ideas of what i might have missued during the setup or why it wont work? Link to comment Share on other sites More sharing options...
Netduma Liam Posted January 18, 2021 Share Posted January 18, 2021 1 hour ago, Od1n said: I wont get any connection to the Internet, see my system information output above. PPPoE credentials are correct, i double checked on that. Same Fritzbox, same R1, same provider since the last time i used PPPoE with the R1. Back then i didnt use the DumaOS though but the last R1 firmware. Any ideas of what i might have missued during the setup or why it wont work? OK, could you please share a screenshot of the PPPoE configuration in Network settings -> WAN? Just the top section is fine, don't include the physical address. Link to comment Share on other sites More sharing options...
Od1n Posted January 19, 2021 Author Share Posted January 19, 2021 Sure, here is the picture. I censored some of the login credentials though. If you need any additional information let me know! Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 19, 2021 Administrators Share Posted January 19, 2021 That all appears to be fine, what is the R1 firmware you're on currently? Link to comment Share on other sites More sharing options...
Od1n Posted January 19, 2021 Author Share Posted January 19, 2021 Firmware version R1 2.1.3.29 The last time i used PPPoE i ran the last official R1 firmware (prior to DumaOS). Could it be my current firmware? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 19, 2021 Administrators Share Posted January 19, 2021 56 minutes ago, Od1n said: Firmware version R1 2.1.3.29 The last time i used PPPoE i ran the last official R1 firmware (prior to DumaOS). Could it be my current firmware? The settings are correct so I couldn't see another cause, I've given you access to the beta, upgrade to that, then reset and enter your PPPoE details and see if it works then https://forum.netduma.com/forum/130-dumaos-30-beta-netduma-r1/ Link to comment Share on other sites More sharing options...
Od1n Posted January 19, 2021 Author Share Posted January 19, 2021 Thanks Fraser, i will do that tomorrow and report back. One question though, when you say update and reset, do you mean i should update the firmware and then restart the router or update and then factory restore so its in a clean state? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 19, 2021 Administrators Share Posted January 19, 2021 21 minutes ago, Od1n said: Thanks Fraser, i will do that tomorrow and report back. One question though, when you say update and reset, do you mean i should update the firmware and then restart the router or update and then factory restore so its in a clean state? Update then do a factory reset please Link to comment Share on other sites More sharing options...
Od1n Posted January 20, 2021 Author Share Posted January 20, 2021 All right i have updated to the latest Beta and also did the factory reset but the R1 still doesnt seem to accept my PPPoE settings. When i type in my PPPoE Username plus Password into the R1 WAN Network settings and press the Save Settings button at the bottom it quickly flashes but nothing happens. When i refresh the R1 interface it defaulted back to DHCP. Am i supposed to fill out the additional information as well? Such as Service, MTU and Mac cloning? Im not sure what Service refers to tbh, i assume i type in the name of my Internet Provider? Link to comment Share on other sites More sharing options...
Administrators Netduma Fraser Posted January 20, 2021 Administrators Share Posted January 20, 2021 12 minutes ago, Od1n said: All right i have updated to the latest Beta and also did the factory reset but the R1 still doesnt seem to accept my PPPoE settings. When i type in my PPPoE Username plus Password into the R1 WAN Network settings and press the Save Settings button at the bottom it quickly flashes but nothing happens. When i refresh the R1 interface it defaulted back to DHCP. Am i supposed to fill out the additional information as well? Such as Service, MTU and Mac cloning? Im not sure what Service refers to tbh, i assume i type in the name of my Internet Provider? You'll need to fill in the MAC address of the router, save then enter PPPoE details and save - we'll fix that for the next version. Link to comment Share on other sites More sharing options...
Recommended Posts
Archived
This topic is now archived and is closed to further replies.