Yes, that's an RFC1918 IP (not in a range I use (!)) logging in to a server as root, with password. And there was no wtmp entry or history.
-
-
Replying to @marcan42
Conclusion: the people nominally managing this server (who still use passwords) SFTPed in from the *same* ISP and they fail at CgNAT.
2 replies 0 retweets 8 likes -
Replying to @marcan42
Apparently they're using RFC1918 space for CgNAT (which is stupid, they should use RFC6598) and it leaks into their colo servers sans NAT.
1 reply 0 retweets 16 likes -
Replying to @marcan42
Remember that all IPv4 address space is routable. RFC 1918 is usually not routed. (127/8 is debatable.)
1 reply 0 retweets 1 like -
Replying to @DrScriptt @marcan42
I’d argue for bogon filters on internet interface to ISP’s CGNAT space.
1 reply 0 retweets 0 likes -
Replying to @DrScriptt
Thing is RFC1918 is usually reserved for end-user usage. I happen to have a dangerously close 172.17.0.0/16 net on this server internally.
3 replies 0 retweets 1 like -
Replying to @marcan42 @DrScriptt
Had they picked that for their shitty CGNAT, it wouldn't be able to hit my server (result: their customers can't access, everyone else can!)
1 reply 0 retweets 1 like -
Replying to @marcan42
That's where double NATing comes into play. *SHUDDER*
1 reply 0 retweets 0 likes -
Replying to @DrScriptt @marcan42
Double NATing has it's uses. Using it to avoid IP conflicts like this is not fun in any way shape or form.
1 reply 0 retweets 0 likes -
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
But yeah, I'm sure some combination of hacks could've made that mess work but... not fun. Maybe playing with netns and two layers of nginx.
-
-
Replying to @marcan42
Ya, I've done it before. Traditionally it's done with multiple routes. Network namespaces would make it easier.
0 replies 0 retweets 0 likesThanks. Twitter will use this to make your timeline better. UndoUndo
-
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.