payload: {"action":"created","issue":{"url":"https://api.github.com/repos/siacs/Conversations/issues/3543","repository_url":"https://api.github.com/repos/siacs/Conversations","labels_url":"https://api.github.com/repos/siacs/Conversations/issues/3543/labels{/name}","comments_url":"https://api.github.com/repos/siacs/Conversations/issues/3543/comments","events_url":"https://api.github.com/repos/siacs/Conversations/issues/3543/events","html_url":"https://github.com/siacs/Conversations/issues/3543","id":497021658,"node_id":"MDU6SXNzdWU0OTcwMjE2NTg=","number":3543,"title":"Conversations.im IPv6 support","user":{"login":"oksjd","id":54463160,"node_id":"MDQ6VXNlcjU0NDYzMTYw","avatar_url":"https://avatars0.githubusercontent.com/u/54463160?v=4","gravatar_id":"","url":"https://api.github.com/users/oksjd","html_url":"https://github.com/oksjd","followers_url":"https://api.github.com/users/oksjd/followers","following_url":"https://api.github.com/users/oksjd/following{/other_user}","gists_url":"https://api.github.com/users/oksjd/gists{/gist_id}","starred_url":"https://api.github.com/users/oksjd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oksjd/subscriptions","organizations_url":"https://api.github.com/users/oksjd/orgs","repos_url":"https://api.github.com/users/oksjd/repos","events_url":"https://api.github.com/users/oksjd/events{/privacy}","received_events_url":"https://api.github.com/users/oksjd/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":10,"created_at":"2019-09-23T10:43:27Z","updated_at":"2019-09-25T02:56:40Z","closed_at":"2019-09-24T06:54:59Z","author_association":"NONE","body":"This issue is concerned about the IPv6 support status of Conversations.im Jabber service, not the app itself.\r\nSince in the latter half of #3542 I've messed up the issue description quite a bit, I will try to summarize it here.\r\n## Background\r\nThe problem is discovered when I was trying to join conversations@conference.siacs.eu using my private account on my home server, which only supports IPv6 connection.\r\n#### Mobile connection\r\nChina Mobile cellular network, which supports native IPv6 connection and carrier grade NAT IPv4 connection (address begin with 10.xx.xx.xx)\r\n#### Server connection\r\n100 Mbps/20 Mbps fiber (!) connection provided by China Mobile, supports native IPv6 connection and carrier grade NAT IPv4 connection (address begin with 10.xx.xx.xx). Using PPPoE\r\n#### Server configuration\r\nHome server is running Proxmox, running ejabberd in a LXC container. Home router is an EA6350v3 with OpenWrt snapshot.\r\n#### DNS\r\nThe DNS service is provided by Cloudflare. I wrote a script to update the records periodically (DDNS) and update the firewall configuration in the router accordingly.\r\n#### Important notes\r\n**All internet connection to servers outside China is really slow and with unacceptable packet loss rate via IPv4. IPv6 connection isn't exhibiting this problem as of now.**\r\n#### IPv6 in VR China\r\nIn December 2018 the all 3 major ISPs in China massively deployed native IPv6 under government request. The main purpose is to solve the lack of IPv4 address and prepare for IoT applications. All phones supporting VoLTE support IPv6. Even WiFi hot-spot function can delegate IPv6 address to the client.\r\n#### Firewall\r\n![pve](https://user-images.githubusercontent.com/54463160/65422044-efd82c00-de37-11e9-999d-3a59c2229619.JPG)\r\n![ow](https://user-images.githubusercontent.com/54463160/65422047-f2d31c80-de37-11e9-8521-082accf3c7b9.JPG)\r\n\r\n## Account registration\r\nClient | Conversations.im | 404.city\r\n------------ | ------------- | -------------\r\nConversations | Succeeded | Failed\r\nConversations with IPv6 | didn't test | succeeded\r\n## Test results\r\nAll conducted with the same Android 9 phone\r\n\r\nClient | Account | Send message to gyc@jr.alpenveilchen.xyz\r\n------------ | ------------- | -------------\r\nPix-Art | gyc@jr.alpenveilchen.xyz | \\ \r\nConversations | w4tpo@conversations.im | failed, with DNS lookup error \r\nConversations with IPv6 | w4tpo@404.city | succeeded, with OMEMO blind trust \r\n## Join public channels from gyc@jr.alpenveilchen.xyz\r\n\r\n1. prosody@conference.prosody.im Succeeded\r\n2. news@chat.404.city Succeeded\r\n3. conversations@conference.siacs.eu Failed (remote server timed out)\r\n## Port \"filtered\"\r\n> nmap -6 -p 5269 jr.alpenveilchen.xyz -Pn\r\n> Starting Nmap 7.70 ( https://nmap.org ) at 2019-09-22 15:43 CEST\r\n> Nmap scan report for jr.alpenveilchen.xyz (2409:8a14:a012:4320::16d)\r\n> Host is up.\r\n> \r\n> PORT     STATE    SERVICE\r\n> 5269/tcp filtered xmpp-server\r\n> \r\n> Nmap done: 1 IP address (1 host up) scanned in 2.26 seconds\r\nAccording to Nmap docs\r\n\r\n> filtered\r\n> Nmap cannot determine whether the port is open because packet filtering prevents its probes from reaching the port. The filtering could be from a dedicated firewall device, router rules, or host-based firewall software. These ports frustrate attackers because they provide so little information.\r\n\r\nIn my understanding this status is more or less an alias for \"unknown\"."},"comment":{"url":"https://api.github.com/repos/siacs/Conversations/issues/comments/534829532","html_url":"https://github.com/siacs/Conversations/issues/3543#issuecomment-534829532","issue_url":"https://api.github.com/repos/siacs/Conversations/issues/3543","id":534829532,"node_id":"MDEyOklzc3VlQ29tbWVudDUzNDgyOTUzMg==","user":{"login":"oksjd","id":54463160,"node_id":"MDQ6VXNlcjU0NDYzMTYw","avatar_url":"https://avatars0.githubusercontent.com/u/54463160?v=4","gravatar_id":"","url":"https://api.github.com/users/oksjd","html_url":"https://github.com/oksjd","followers_url":"https://api.github.com/users/oksjd/followers","following_url":"https://api.github.com/users/oksjd/following{/other_user}","gists_url":"https://api.github.com/users/oksjd/gists{/gist_id}","starred_url":"https://api.github.com/users/oksjd/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/oksjd/subscriptions","organizations_url":"https://api.github.com/users/oksjd/orgs","repos_url":"https://api.github.com/users/oksjd/repos","events_url":"https://api.github.com/users/oksjd/events{/privacy}","received_events_url":"https://api.github.com/users/oksjd/received_events","type":"User","site_admin":false},"created_at":"2019-09-25T02:56:40Z","updated_at":"2019-09-25T02:56:40Z","author_association":"NONE","body":"Didn't last long. The connection is lost, again.\r\n18:  be2813.ccr41.fra03.atlas.cogentco.com               572.750ms\r\n19:  be2846.rcr22.fra06.atlas.cogentco.com               421.143ms\r\n20:  no reply\r\n21:  no reply\r\n22:  no reply\r\n23:  no reply\r\n24:  no reply\r\n25:  no reply\r\n26:  no reply\r\n27:  no reply\r\n28:  no reply\r\n29:  no reply\r\n30:  no reply\r\n     Too many hops: pmtu 1500\r\n     Resume: pmtu 1500"}}
other: {"actor":{"display_login":"oksjd"}}