Double NATing has it's uses. Using it to avoid IP conflicts like this is not fun in any way shape or form.
-
-
Replying to @DrScriptt
I actually double NAT for my home internet. But the first layer is 1:1, even pings get NATed. Except one TCP port.
2 replies 0 retweets 0 likes -
Replying to @marcan42
Are you doing double NAT by choice? If so, why? I'm curious.
1 reply 0 retweets 0 likes -
Replying to @DrScriptt
I moved most of my routing duties to an x86 box, but I still terminate the PPPoE connection in my OpenWRT Netgear.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @DrScriptt
The reason is remote unlock, so I don't have to stick a PPPoE client in my initramfs. Also I have remote access to a serial console via SSH.
1 reply 0 retweets 0 likes -
Replying to @marcan42 @DrScriptt
Actually I run two PPPoE sessions, and only one (v4) terminates in the Netgear. The other passes through (no NAT or extra routing hop on v6)
1 reply 0 retweets 0 likes -
Replying to @marcan42
Okay. I don't think I would have chosen that. To each his own. You have logical reasons, so no complaint here.
1 reply 0 retweets 0 likes -
Replying to @DrScriptt
I mean, my only other option was to stick a PPPoE client in my initramfs. Keeping all routing duties on the Netgear wasn't an option (perf).
2 replies 0 retweets 1 like -
Replying to @marcan42 @DrScriptt
There's no real downside to the double-NAT here, since all protocols are forwarded. And some minor upsides (e.g. insulation from IP changes)
1 reply 0 retweets 0 likes -
Replying to @marcan42
I'm not sure I understand, much less agree. Please elaborate on the upsides.
1 reply 0 retweets 0 likes
I can have a static network configuration in the main router host, with no dynamic reconfig, since the dyn IP is NATed to a static address.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.