Yes, I'm talking about link-local ipv6.
The main case is to use link-local addresses for administration, but
without need to install and configure a dhcp server or work in parallel
with the current dhcp.
1) Provide openwisp hostname with avahi.
2) Resolve hostname on target devices
3) Register automatically using resolved hostname.
Without --interface option curl fails with error code 7. That's i found
through logread.
Strace shows error more clearly:
connect(3, {sa_family=AF_INET6, sin6_port=htons(443), inet_pton(AF_INET6,
"fe80::d1d3:caec:592f:5cf2", &sin6_addr), sin6_flowinfo=htonl(0),
sin6_scope_id=0}, 28) = -1 EINVAL (Invalid argument)
close(3)
среда, 5 апреля 2017 г., 13:40:12 UTC+5 пользователь Federico Capoano
написал:
>
> Hi Krew,
>
> I've read the curl docs regarding the --interface argument but I'm
> confused by the aim of the pull request: it mentions adding support for
> ipv6, but I have done some tests right now with tcpdump and verified that
> curl already supports ipv6, I even had an instance of openwisp2 deployed on
> a server with ipv6 address which would show ipv6 addresses in the "last ip"
> field of configuration objects (which means curl downloaded configurations
> via ipv6).
>
> It seems to me that you want to add support for sending http requests to
> ipv6 link local addresses, which is a slightly different thing, but I need
> to know more about your use case in order to understand what is that you
> are not able to do right now and what's the best way to add support for it.
>
> Could you also paste your /etc/config/openwisp configuration (anonymizing
> any sensitive information like uuid, keys or shared secret)?
>
> Could you tell me the error your are getting by trying that configuration
> with the current unmodified openwisp-config version?
> You can see such an error with:
>
> logread | grep openwisp
>
> Federico
>
> On Wed, Apr 5, 2017 at 8:20 AM Кирилл Луконин <[email protected]
> <javascript:>> wrote:
>
>> Sure.
>>
>> Here some tips about --interface option
>>
>> https://sites.google.com/site/xiangyangsite/home/technical-tips/linux-unix/common-tips/manual----curl-usage-explained-with-examples
>>
>> And explanation why it should be specified.
>>
>> https://blogs.gentoo.org/eva/2010/12/17/things-you-didnt-known-about-ipv6-link-local-address/
>>
>>
>>
>> вторник, 4 апреля 2017 г., 23:56:15 UTC+5 пользователь Federico Capoano
>> написал:
>>
>>> Hi Krew,
>>>
>>> welcome and thank you for contributing actively.
>>>
>>> any good resource you suggest to read about this issue?
>>>
>>> Federico
>>>
>>>
>>> On Tuesday, April 4, 2017 at 8:34:14 PM UTC+2, Кирилл Луконин wrote:
>>>>
>>>> Hello, friends.
>>>>
>>>> I tried to migrate from ipv4 and faced the issue with curl. It does not
>>>> normally work with ipv6 addresses and hostnames, resolved to ipv6 without
>>>> --interface option. It' a known bug, so i decided to make a pull request.
>>>>
>>>> https://github.com/openwisp/openwisp-config/pull/30
>>>> Is it a solution, what do you think?
>>>>
>>>>
>>>> Best regards,
>>>> Krew.
>>>>
>>>> --
>> You received this message because you are subscribed to the Google Groups
>> "OpenWISP" group.
>> To unsubscribe from this group and stop receiving emails from it, send an
>> email to [email protected] <javascript:>.
>> For more options, visit https://groups.google.com/d/optout.
>>
>
--
You received this message because you are subscribed to the Google Groups
"OpenWISP" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/d/optout.
