You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@httpd.apache.org by Jeff Trawick <tr...@bellsouth.net> on 2001/01/20 03:58:14 UTC
Re: [horape: Re: general/7099: ipv6 support]
horape@tinuviel.compendium.net.ar writes:
> I was directed by Tony Finch to ask here.
>
> BTW 2, is there some list for the people working with apache and ipv6?
> new-httpd seems to have too much traffic for me...
This is the main list for mainstream apache and IPv6. Some of the
issues are handled in APR (Apache Portable Runtime), which is
discussed on dev@apr.apache.org.
If you can't get the server to get an AF_INET6 listening socket:
1) does APR think it supports IPv6?
check for the value of APR_HAVE_IPV6 in srclib/include/apr.h
if 0 (i.e., no support), look at output of APR configure for ideas why
2) if APR supports IPv6 but Apache doesn't get an IPv6 socket...
what are your listen statements?
what network interfaces are active?
Thanks for your interest,
Jeff
--
Jeff Trawick | trawickj@bellsouth.net | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
Re: [horape: Re: general/7099: ipv6 support]
Posted by ho...@tinuviel.compendium.net.ar.
�Hola!
> > check for the value of APR_HAVE_IPV6 in srclib/include/apr.h
> It's 0.
Sorry, it's 1.
HoraPe
---
Horacio J. Pe�a
horape@compendium.com.ar
horape@uninet.edu
bofh@puntoar.net.ar
horape@hcdn.gov.ar
Re: Expected date for Beta?
Posted by Greg Stein <gs...@lyra.org>.
On Sat, Jan 20, 2001 at 02:42:22AM -0500, David Williams wrote:
> Any consensus on when the first Beta will ship? :-)
When it is ready :-)
I'd guess we should see a beta in a couple weeks.
Cheers,
-g
--
Greg Stein, http://www.lyra.org/
Expected date for Beta?
Posted by David Williams <dw...@cisco.com>.
Any consensus on when the first Beta will ship? :-)
thanks!
-david
Re: ipv6 support
Posted by rb...@covalent.net.
> > > Oops, i think i know what's happening... Looking at the list archive
> > > i see that ipv6 support is very recent. And i'm working with 2.0a9.
> > > Should i try with cvs version?
> > Absolutely! I know for a fact that there were a lot of bugs fixed just
> > after 2.0a9.
>
> Thanks. That solved the problem.
GREAT! Please let us know if you have any other problems.
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
ipv6 support
Posted by ho...@tinuviel.compendium.net.ar.
�Hola!
> > Oops, i think i know what's happening... Looking at the list archive
> > i see that ipv6 support is very recent. And i'm working with 2.0a9.
> > Should i try with cvs version?
> Absolutely! I know for a fact that there were a lot of bugs fixed just
> after 2.0a9.
Thanks. That solved the problem.
> Ryan
> _______________________________________________________________________________
> Ryan Bloom rbb@apache.org
> 406 29th St.
> San Francisco, CA 94131
> -------------------------------------------------------------------------------
--
HoraPe
---
Horacio J. Pe�a
horape@compendium.com.ar
horape@uninet.edu
bofh@puntoar.net.ar
horape@hcdn.gov.ar
Re: [horape: Re: general/7099: ipv6 support]
Posted by rb...@covalent.net.
> Oops, i think i know what's happening... Looking at the list archive
> i see that ipv6 support is very recent. And i'm working with 2.0a9.
> Should i try with cvs version?
Absolutely! I know for a fact that there were a lot of bugs fixed just
after 2.0a9.
Ryan
_______________________________________________________________________________
Ryan Bloom rbb@apache.org
406 29th St.
San Francisco, CA 94131
-------------------------------------------------------------------------------
Re: [horape: Re: general/7099: ipv6 support]
Posted by ho...@tinuviel.compendium.net.ar.
�Hola!
> > > 2) if APR supports IPv6 but Apache doesn't get an IPv6 socket...
> > > what are your listen statements?
> > I've tried: (using "Port 8000" so it doesn't bother my ipv4-only apache)
> > - none (it binds 0.0.0.0:8000)
> > - Listen 3ffe:2900:b00d:0:200:21ff:fe47:2d95 (it binds 0.0.0.0:2900)
> > - Listen ip6.compendium.net.ar:8000 (it binds 0.0.0.0:8000)
> > - Listen [3ffe:2900:b00d:0:200:21ff:fe47:2d95]:8000 (it binds
> > 0.0.0.0:2900)
> I have
> Listen [fe80::whatever]:8080
> as my only listen statement and it works for me.
Why do you listen on a link-local address? It shouldn't work.
BTW, if i set:
Listen [fe80::200:21ff:fe47:2d95]:8000
i get:
Syntax error on line 7 of /usr/local/apache/conf/httpd.conf:
Port must be numeric
Oops, i think i know what's happening... Looking at the list archive
i see that ipv6 support is very recent. And i'm working with 2.0a9.
Should i try with cvs version?
> I have no idea where that bind to port 2900 could be coming from.
> Does 2900 appear anywhere in your config file?
Listen 3ffe:2900:b00d:0:200:21ff:fe47:2d95
^^^^
It seems to be parsing it as Listen 0.0.0.3:2900 and maybe (wild guess!) 0.0.0.0/8
means IN_ADDR_ANY or something like that...
> If it still is a mystery, perhaps you could put a breakpoint in
> apr_bind() and when it binds to port 2900 a backtrace would help
> figure out how we were getting there.
>
> Use -DONE_PROCESS to use only a single server process:
>
> gdb ./httpd
> r -DONE_PROCESS
It doesn't work:
tinuviel:/home/horape/apache_2.0a9# gdb ./httpd
GNU gdb 5.0
(gdb) b apr_bind
Breakpoint 1 at 0x808b98a: file sockets.c, line 167.
(gdb) r -DONE_PROCESS
Starting program: /usr/home/horape/apache_2.0a9/./httpd -DONE_PROCESS
[New Thread 1024 (LWP 28849)]
Program exited normally.
(gdb)
Thanks,
HoraPe
---
Horacio J. Pe�a
horape@compendium.com.ar
horape@uninet.edu
bofh@puntoar.net.ar
horape@hcdn.gov.ar
Re: [horape: Re: general/7099: ipv6 support]
Posted by Jeff Trawick <tr...@bellsouth.net>.
horape@tinuviel.compendium.net.ar writes:
> > 2) if APR supports IPv6 but Apache doesn't get an IPv6 socket...
>
> > what are your listen statements?
>
> I've tried: (using "Port 8000" so it doesn't bother my ipv4-only apache)
>
> - none (it binds 0.0.0.0:8000)
> - Listen 3ffe:2900:b00d:0:200:21ff:fe47:2d95 (it binds 0.0.0.0:2900)
> - Listen ip6.compendium.net.ar:8000 (it binds 0.0.0.0:8000)
> - Listen [3ffe:2900:b00d:0:200:21ff:fe47:2d95]:8000 (it binds
> 0.0.0.0:2900)
I have
Listen [fe80::whatever]:8080
as my only listen statement and it works for me.
I have no idea where that bind to port 2900 could be coming from.
Does 2900 appear anywhere in your config file?
If it still is a mystery, perhaps you could put a breakpoint in
apr_bind() and when it binds to port 2900 a backtrace would help
figure out how we were getting there.
Use -DONE_PROCESS to use only a single server process:
gdb ./httpd
r -DONE_PROCESS
Hrrm... If I have just
Listen 8080
and IPv6 is active, my glibc getaddrinfo() on Linux is taking forever
to look up "::". That needs to be looked into...
--
Jeff Trawick | trawickj@bellsouth.net | PGP public key at web site:
http://www.geocities.com/SiliconValley/Park/9289/
Born in Roswell... married an alien...
Re: [horape: Re: general/7099: ipv6 support]
Posted by ho...@tinuviel.compendium.net.ar.
�Hola!
Wow, what a quick answer!
> If you can't get the server to get an AF_INET6 listening socket:
> 1) does APR think it supports IPv6?
> check for the value of APR_HAVE_IPV6 in srclib/include/apr.h
It's 0.
> if 0 (i.e., no support), look at output of APR configure for ideas why
> 2) if APR supports IPv6 but Apache doesn't get an IPv6 socket...
> what are your listen statements?
I've tried: (using "Port 8000" so it doesn't bother my ipv4-only apache)
- none (it binds 0.0.0.0:8000)
- Listen 3ffe:2900:b00d:0:200:21ff:fe47:2d95 (it binds 0.0.0.0:2900)
- Listen ip6.compendium.net.ar:8000 (it binds 0.0.0.0:8000)
- Listen [3ffe:2900:b00d:0:200:21ff:fe47:2d95]:8000 (it binds 0.0.0.0:2900)
> what network interfaces are active?
tinuviel:/usr/local/apache/conf# ifconfig
eth0 Link encap:Ethernet HWaddr 00:00:21:47:2D:95
inet addr:200.47.36.251 Bcast:0.0.0.0 Mask:255.255.255.128
inet6 addr: fe80::200:21ff:fe47:2d95/10 Scope:Link
inet6 addr: 3ffe:2900:b00d:0:200:21ff:fe47:2d95/64 Scope:Global
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2218553 errors:3 dropped:0 overruns:0 frame:250
TX packets:722453 errors:0 dropped:0 overruns:0 carrier:0
collisions:10742 txqueuelen:100
Interrupt:3 Base address:0x300
(BTW, bind9 and openssh work well listening on ipv6 sockets)
> Thanks for your interest,
> Jeff
HoraPe
---
Horacio J. Pe�a
horape@compendium.com.ar
horape@uninet.edu
bofh@puntoar.net.ar
horape@hcdn.gov.ar