@Ghost said in Ares in Mexico:
The IPv6 thing is weird. I'd suspect that first and if it still fails I would suspect a telnet block.
Telnet wouldn't block the websites though. Many firewalls will block the websockets connection on the web portal and prevent it from getting live updates, but you can still at least get there and read stuff.
@faraday Yeah to be more clear I meant for the MU client connections. The web portal connection would make port22 a less likely culprit, but if MU client fails to connect, as well, it could be related to a block.
Still find it weird that no IPv4 exists. Forgive me I'm sitting in bed pretty tired here, but could the router be providing all internal devices an IPv6 address and then trying to use some sort of NATing that's confusing the whole thing? Definitely sounds like whoever set up that router/network tightened up security a bit.
Delete the Hog Pit. It'll be fun.
I really don't understand He-Man
@Ghost said in Ares in Mexico:
Definitely sounds like whoever set up that router/network tightened up security a bit.
Yeah could be - though not setting up V4 isn't really a security thing, is it? Just seems bizarre. (Disabling telnet though - you're absolutely right about that being a vulnerability.)
@faraday No I'm just tired and theorizing.
It sounds feasible to only apply IPv6 to internal devices and then use NAT to route to them? I dunno. I'm tired and possibly over complicating things.
The router itself would have an external IP address as the focal point of connections exiting the network. Each device on the network typically would have a device on it assigned one of the typical internal IP addresses 192.168.x.x, but I was trying to brainstorm why a connection would believe it didnt have an ipv4 address and here is where my brain went...
I dunno. Like I said I'm tired and was wondering why a device wouldn't have any sort of ipv4 recognized address (if even to route to) because a hard locked IPv6 config seems like a nightmare. There are typical simple home networking configs, then there are "dickin around with the network" configs.
Keep in mind that IPv4 addresses are essentially all taken/spoken-for, there are several ISPs in the world that only have IPv6 address space available to them (without spending huge amounts of money to obtain a public IP4 address block). You'll be seeing this more and more for the rest of time. I've heard that Asia in specific has been forced over to IPv6-only setups for the past couple years now. It wouldn't be too surprising if there are similar situations in other areas that were "late" to the IPv4 party.
What I suggest would be to setup an IPv6-to-4 proxy using an AWS-based haproxy instance to bounce the traffic through. I'm actually setting one up now just to try it out, since I haven't had much chance to play with IPv6 addresses.
Maybe you could get around it with a VPN as well? Not sure. Beyond my meager networking fu here.
http://www.cheesesoftware.com/MUCon/# Can you use that one?
I'm also seconding a VPN connection.
In a former job, I traveled to Singapore and Malaysia 1-2x a year and my ability to connect to games while using wifi networks was pretty hit or miss due to security configurations. I also couldn't log into my US-based Netflix and Hulu accounts.
So, I started engaging with a VPN service and that solved pretty much all of it.
@krmbm If by "use that one" you mean I click on it and it takes me to something that looks like a mush login screen, then yes.
@GangOfDolls Will definitely try a VPN. We were planning on testing that out here anyway for our cable streaming needs (which won't normally allow viewing outside of the US).
@Brunocerous said in Ares in Mexico:
@krmbm If by "use that one" you mean I click on it and it takes me to something that looks like a mush login screen, then yes.
It's a functional, free client that should let you connect to whatever MUSH you want. I use it all the time when I get firewalled.
@krmbm Oh! Thank you. Works like a charm.
This is a bit out of place, but I'm working on a relative's computer remotely that rebooted for the last big Windows update (20H2 I think?) and can't seem to pick up an IPv4 address from the router, but IPv6 works. I wonder if whatever's going on here is actually what's happened with @Brunocerous 's situation.
@Ghost said in Ares in Mexico:
Definitely sounds like whoever set up that router/network tightened up security a bit.
Yeah could be - though not setting up V4 isn't really a security thing, is it? Just seems bizarre. (Disabling telnet though - you're absolutely right about that being a vulnerability.)
