So, got some time for this again.
The good news, the patch will work like expected and even support the
definition of the listening address. Some working examples (changed IPv6
address for reason):
beowulf@:~/fossil$ ./fossil server -P
34cd::ab12:1234:a12b:12ab:1ab2:34cd:3cd4:8889
Andy Bradford amb-sendok-1430621661.lfonacgmnndpbedgo...@bradfords.org
schrieb am Fr., 3. Apr. 2015 um 04:54 Uhr:
Thus said Oliver Friedrich on Thu, 02 Apr 2015 20:56:38 -:
zIpAddr's use isn't very well documented here. Basically, you can
influence which IP address ``fossil
Ok, heres a patch attached.
The patch will use ipv6 socket instead of ipv4. The socketoption
IPV6_V6ONLY is explicitly disabled, allowing incomming ipv4 connections to
be accepted as well.
Caveats:
1. The part on invoking a cgi-server with the zIpAddr parameter specified
is not tested, since I
Thus said Oliver Friedrich on Thu, 02 Apr 2015 20:56:38 -:
1. The part on invoking a cgi-server with the zIpAddr parameter
specified is not tested, since I cannot figure out when this is used.
However, it zIpAddr is an ipv4 string (e.g. 127.0.0.1) it will be
converted to
Thus said Oliver Friedrich on Thu, 02 Apr 2015 20:56:38 -:
As I'm completly new to c programming this is more a draft than
anything I would call a contribution, but for fossil server it works
already and I'll definetly spend more time on that next week.
Is it isn't necessary to
Sorry to bother you again on this, but with the sources of the last release
and default compile options, IPV6 seems not to be active:
beowulf:~/Projekte$ fossil version
This is fossil version 1.32 [6c40678e91] 2015-03-14 13:20:34 UTC
beowulf:~/Projekte$ fossil server -P 8889 ./
[1] 2205
On 4/2/15, Oliver Friedrich redtalonof+mailingl...@gmail.com wrote:
Sorry to bother you again on this, but with the sources of the last release
and default compile options, IPV6 seems not to be active:
The ui and server commands might still only support IPv4. The
sync, push, and pull commands
Ah, ok. Accessing the web interface via ipv6 would be useful now, but what
has to wait, has to wait. Thank you :-)
Richard Hipp d...@sqlite.org schrieb am Do., 2. Apr. 2015 um 14:41 Uhr:
On 4/2/15, Oliver Friedrich redtalonof+mailingl...@gmail.com wrote:
Sorry to bother you again on this,
On 4/2/15, Oliver Friedrich redtalonof+mailingl...@gmail.com wrote:
Ah, ok. Accessing the web interface via ipv6 would be useful now, but what
has to wait, has to wait.
You could work on a patch while you are waiting :-)
--
D. Richard Hipp
d...@sqlite.org
On Mon, Mar 30, 2015 at 6:47 AM, Oliver Friedrich
redtalonof+mailingl...@gmail.com wrote:
Does fossil support ipv6?
If it does, does it need extra compile-settings or is it supportet by
default?
Fossil supports IPv6 in its default configuration.
I have IPv6 at my office. So most of the
Does fossil support ipv6?
If it does, does it need extra compile-settings or is it supportet by
default?
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
The best way to handle this is to use getaddrinfo and getnameinfo,
deal with multiple sockets and be blissfully unaware of the actual
protocol being used in 99% of the code. All the #if stuff is a pain to
deal with.
-- Gé
On Oct 16, 2011, at 18:59, Christopher Vance cjsva...@gmail.com wrote:
I
On Mon, Oct 17, 2011 at 12:59:00PM +1100, Christopher Vance wrote:
To do this properly, you need to be aware that some operating systems
(including OpenBSD, which I'm using) which do not allow IPv4 traffic
on IPv6 sockets, therefore requiring separate sockets for IPv4 and
IPv6. (Specificially,
13 matches
Mail list logo
