Post 9kLwqn81aqwF13zGWO by kiito@niu.moe
(DIR) More posts by kiito@niu.moe
(DIR) Post #9kLtgNm0hyy7cX2F7I by crlf@niu.moe
2019-06-29T22:02:00Z
0 likes, 0 repeats
dumb question: why would a home PC not be able to reach the home server through the external ip? external clients can reach it fine. it's like the isp or router isn't forwarding requests that come from the same network.obviously I can still reach the server through its local ip.
(DIR) Post #9kLuXICKAWw5fyZZVg by crlf@niu.moe
2019-06-29T22:11:33Z
0 likes, 0 repeats
@_p_ yeah. I seem to be able to reach it fine from the outside (testing from a tilde.town session), but when I try from my desktop it times out. I noticed the same thing when I forwarded ssh a few weeks ago.Interestingly enough, pinging is the opposite: I can ping the internet ip from my desktop and get a reply, but I get nothing when pinging from outside.
(DIR) Post #9kLumePhqxImvA9hXU by kiito@niu.moe
2019-06-29T22:14:20Z
0 likes, 0 repeats
@crlf I don't know where you live, but (I think) most countries outside the US have only a limited amount of IPv4 addresses. Due to that providers are stretching them out using dual stack lite.This means that you are able to access both v4 and v6 addresses but your device is only reachable through your IPv6 address...
(DIR) Post #9kLuonjUAz9MP1QsKm by crlf@niu.moe
2019-06-29T22:14:43Z
0 likes, 0 repeats
@_p_ What even is handling the ping in this case? Would that be my router or the isp/modem?
(DIR) Post #9kLwToKqwLUQ6C1tB2 by crlf@niu.moe
2019-06-29T22:33:21Z
0 likes, 0 repeats
@kiito I'm in the US. Online tests couldn't detect an IPv6 address. Could be related to the fact my router is too old to support IPv6 (wrt54gl with latest official firmware).
(DIR) Post #9kLwqn81aqwF13zGWO by kiito@niu.moe
2019-06-29T22:37:27Z
0 likes, 0 repeats
@crlf alright, yeah, I did read that IPv6 isn't as prevalent in the US cause you have all the good IPv4 IPs so carriers aren't all that motivated >.< Well, I don't think I can help further...
(DIR) Post #9kLyRq1HuFQMeV466a by crlf@niu.moe
2019-06-29T22:55:23Z
0 likes, 0 repeats
@kiito thanks anyway. sorry for hogging the IPs.
(DIR) Post #9kNERHscd7DZC6jNzc by crlf@niu.moe
2019-06-30T13:29:17Z
0 likes, 0 repeats
@_p_ Does this help? I am good drawer. In summary:- desktop CAN do 'ssh 192.168.0.3'- tilde.town CAN do 'ssh 99.99.99.9'- desktop CAN'T do 'ssh 99.99.99.9'Also this example is for ssh but http requests look the same.
(DIR) Post #9kNG8gZQo5qkB10prk by crlf@niu.moe
2019-06-30T13:48:17Z
0 likes, 0 repeats
@_p_ not an expert at reading traceroutes but looks like it's just my router and modem, both numbered 1.I'm going to guess it's just this modem being dumb. If that's the case there's not much I can do other than buy a new one, since this one is provided by asshole Charter and they decided to make the modem UI completely inaccessible.
(DIR) Post #9kNGgXyVGu5tMbszrM by crlf@niu.moe
2019-06-30T13:54:27Z
0 likes, 0 repeats
@_p_ It really doesn't. I just tried it to test the port forwarding and was curious when it didn't work. Not something to bother doing extensive troubleshooting over.
(DIR) Post #9kNHbNciQkZ5lWnM9Y by crlf@niu.moe
2019-06-30T14:04:43Z
0 likes, 0 repeats
@_p_ It's probably their fault in one way or another.The other curiosity here is that pinging the outside IP works the opposite: my desktop gets replies but tilde doesn't. Maybe that's standard setup, I don't know.Thanks for humoring me.