does ipv6 prevent registration? [fixed in v1.100]

jksjks
edited July 2017 in Problems Now Fixed
[ Hi RJ. The way you pasted the log in your original question really messed up the forum software. So I had to delete the question and re-post it myself. This forum software is not the best unfortunately 8-| ]

hi, 
does having an ipv6 address prevent from registration?

Sat Jul  1 19:06:58 2017 0:00:35 ....      DDNS: private IPv4 <192.168.178.20> 0xc0a8b214 /24 0xffffff00
Sat Jul  1 19:06:58 2017 0:00:35 ....      DDNS: private IPv6 <2003:80:ad1e:1900:b2d5:ccff:fe57:189a> /64 ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:
Sat Jul  1 19:06:58 2017 0:00:35 ....      DDNS: private IPv6 LINK-LOCAL <fe80::b2d5:ccff:fe57:189a%eth0> /64 ff:ff:ff:ff:ff:ff:ff:ff:00:00:00:00:00:00:00:00:
Sat Jul  1 19:06:58 2017 0:00:35 ....      UPDATE: version 1.99 is current
Sat Jul  1 19:06:58 2017 0:00:35 ....      task update_task:P2:T22 exited by returning
Sat Jul  1 19:06:58 2017 0:00:35 ....      DDNS: public ip 91.41.116.40
Sat Jul  1 19:06:58 2017 0:00:35 ....      auto NAT is set false
Sat Jul  1 19:06:58 2017 0:00:35 ....      task dyn_DNS:P2:T02 exited by returning
Sat Jul  1 19:06:59 2017 0:00:37 ....      sdr.hu registration: "ERROR (your IP does not match URL, 91.41.116.40 != 2003:80:ad1e:1900:b2d5:ccff:fe57:189a)"
Sat Jul  1 19:07:07 2017 0:00:44 ....      TIMEZONE: lat/lon from sdr.hu config: (51.161236, 6.996694)
Sat Jul  1 19:07:07 2017 0:00:45 ....      TIMEZONE: for (51.161236, 6.996694): utc_offset=3600/1.0 dst_offset=3600/1.0
Sat Jul  1 19:07:07 2017 0:00:45 ....      TIMEZONE: "Europe/Berlin", "Central European Summer Time"
Sat Jul  1 19:07:07 2017 0:00:45 ....      task get_TZ:P2:T03 exited by returning
Sat Jul  1 19:07:13 2017 0:00:50 .... [00] isLocal_IP: flg=0x18 fam=10 socktype=1 proto=6 addrlen=28 2003:80:ad1e:1900:1cd0:6ed8:3b26:466d
Sat Jul  1 19:07:13 2017 0:00:50 .... [00] isLocal_IP TRUE IPv6 remote_ip 2003:80:ad1e:1900:1cd0:6ed8:3b26:466d ip_client 2003:80:ad1e:1900:1cd0:6ed8:3b26:466d ip_server[IPv6] 2003:80:ad1e:1900:b2d5:ccff:fe57:189a nm /64
Sat Jul  1 19:07:13 2017 0:00:50 .... [00] PWD admin: config pwd set TRUE, auto-login TRUE
Sat Jul  1 19:07:13 2017 0:00:50 .... [00] PWD admin: config pwd set, but is_local and auto-login set
Sat Jul  1 19:07:13 2017 0:00:50 .... [00] PWD admin allow override: sent from 2003:80:ad1e:1900:1cd0:6ed8:3b26:466d
Sat Jul  1 19:07:39 2017 0:01:17 .... [00] ADMIN connection closed
Sat Jul  1 19:08:05 2017 0:01:42 .... [00] isLocal_IP: flg=0x18 fam=10 socktype=1 proto=6 addrlen=28 2003:80:ad1e:1900:1cd0:6ed8:3b26:466d
Sat Jul  1 19:08:05 2017 0:01:42 .... [00] isLocal_IP TRUE IPv6 remote_ip 2003:80:ad1e:1900:1cd0:6ed8:3b26:466d ip_client 2003:80:ad1e:1900:1cd0:6ed8:3b26:466d ip_server[IPv6] 2003:80:ad1e:1900:b2d5:ccff:fe57:189a nm /64
Sat Jul  1 19:08:05 2017 0:01:42 .... [00] PWD admin: config pwd set TRUE, auto-login TRUE
Sat Jul  1 19:08:05 2017 0:01:42 .... [00] PWD admin: config pwd set, but is_local and auto-login set
Sat Jul  1 19:08:05 2017 0:01:42 .... [00] PWD admin allow override: sent from 2003:80:ad1e:1900:1cd0:6ed8:3b26:466d
Sat Jul  1 19:09:02 2017 0:02:40 ....      sdr.hu registration: "ERROR (your IP does not match URL, 91.41.116.40 != 2003:80:ad1e:1900:b2d5:ccff:fe57:189a)"
Sat Jul  1 19:11:05 2017 0:04:43 ....      sdr.hu registration: "ERROR (your IP does not match URL, 91.41.116.40 != 2003:80:ad1e:1900:b2d5:ccff:fe57:189a)"

Comments

  • I was looking at this a few days ago for another user. Although in that case the circumstances were a little bit different.

    Does the domain name for your Kiwi have an ipv6 DNS record ("AAAA") of 2003:80:ad1e:1900:b2d5:ccff:fe57:189a ?
    I think what's happening is that the sdr.hu lookup of your domain is using the ipv6 when both ipv4 and ipv6 exist. But I am only sending ipv4 in the request when both exist. So I may need to try sending both if one fails.

  • hi jks,
    sorry for the inconveniences.

    nslookup -query=AAAA  kiwisdr.shjn224ludslv1s5.myfritz.net

    Non-authoritative answer:
    kiwisdr.shjn224ludslv1s5.myfritz.net    has AAAA address 2003:80:ad1e:1900:b2d5:ccff:fe57:189a

    best regards
    robert (db1jj)
  • Okay, let me add retrying with ipv6 (if available) when an ipv4 registration fails. I'll try and get this in today's update.
    My ISP doesn't offer ipv6 connections, so I can't easily test from here.

  • Okay, if you're listed on rx.linkfanel.net that means it could be another problem with sdr.hu. Let me do some checking..

  • jksjks
    edited July 2017
    Could you please restart your Kiwi? (pull and replug the power, or login and type "cdp", "ku").
    I used the wrong command to restart the server after making a change and now I can't get back in.. Thanks.

    rjschneider
  • Alright, v1.100 should fix this problem. Thanks for giving me the info about the failure. That was a big help.

    rjschneider
  • i restarted the kiwi.
    If you need a ipv6 connection there are ways to get one via a tunnel: https://en.wikipedia.org/wiki/List_of_IPv6_tunnel_brokers


  • to explain my setup a little further:
    on ipv4 i have here the normal nat setup. with port forwarding of port 8073/tcp to 192 168 178.20 on the internal net.
    on ipv6 i get in the moment the 2003:80:ad1e:1900::/56 net (56 is netmask) from my provider and the kiwi is on
    2003:80:ad1e:1900:b2d5:ccff:fe57:189a in the moment.
  • Looks like my fix in v1.100 worked. You're now listed on sdr.hu
    I added the "--inet4-only" option to the wget that sends the registration info to sdr.hu  That way it won't get an ipv6 packet and fail to match with the domain ip.

    Thanks, I didn't realize there were such things as ipv6 tunnels. I'll give it a try.

    rjschneider
  • The actual problem is with sdr.hu  If it receives a registration from an ipv6 packet, and the domain name in the packet has both ipv4 ("A") and ipv6 ("AAAA") DNS records then it always tries to match with the ipv4 and not the ipv6 like it should. The other problem I discovered is that sdr.hu doesn't seem to accept ipv6 addresses as a valid domain name as it does for ipv4. That would have been the other way to solve the problem.

    rjschneider
  • thanks John for your quick help.
Sign In or Register to comment.