Redflame Posted 7 hours ago Author Posted 7 hours ago 43 minutes ago, Netduma Fraser said: You shouldn't have a double NAT if the R3 is in the EE hub DMZ so I'd suggest checking the WAN IP on the R3 is the same as the IP entered in the DMZ. In that scenario if you need PPPoE for example then yes you can just put those details in and leave everything else the same. You may need to fine tune your Congestion Control settings a little more to get the same results you're used to but otherwise it would be fine. I would look into the DMZ thing though first as you can see reduced speeds and there is also a disconnect issue with PPPoE we're looking into. The R3 won't change any settings unless you change them so no need to screenshot. If you have a double NAT even after connecting to the ONT then you have a CG-NAT in which case you only have these options to resolve it: Get a static public IP from the ISP (usually a charged extra) Use a VPN (using a VPN generally gives you a moderate/strict NAT anyway, also an extra charge) Change ISP to one that doesn't use CG-NAT Hi So I double checked. Wan IP > 192.xx.xx.xx is the same as the static ip that is set on ee hub - the one I used since day one. public ip > is the same one that call of duty, whatismyipaddress dot com and ip info see. I don’t know if this is a sign of double Nat or just the way things work in DMZ. But I noticed in trace routes that after dumaos.lan I hit ee router default gateway. I’ll show a screenshot,
Administrators Netduma Fraser Posted 7 hours ago Administrators Posted 7 hours ago That's normal, follow this guide to see if you have a CG-NAT https://support.netduma.com/docs/dumaos-3/open-nat/#cg-nat
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now