#4335 Apache does not configure correctly on dual stack IPV4/6

0.82
open
IPV6 (3)
5
2013-12-25
2013-12-17
No

I have comcast dual stack 4/6. Windows 7 Firefox browser defaults to IPV6. Apache Webmin creates listener on IPV6, won't on IPV4. I know how to set the apache config up at the command line. It would seem that there is some problem with Webmin if the browser defaults to V6 and the connection to the VPS is on V6.

Discussion

  • Jamie Cameron

    Jamie Cameron - 2013-12-17

    So is the problem just that Apache is only listening on an IPv4 address and not IPv6?

     
    • Mike Maurice

      Mike Maurice - 2013-12-18

      On 12/17/2013 12:43 PM, Jamie Cameron wrote:

      So is the problem just that Apache is only listening on an IPv4 address
      and not IPv6?


      [bugs:#4335] http://sourceforge.net/p/webadmin/bugs/4335/ Apache does
      not configure correctly on dual stack IPV4/6

      Status: open
      Labels: IPV6
      Created: Tue Dec 17, 2013 05:58 PM UTC by Mike Maurice
      Last Updated: Tue Dec 17, 2013 05:58 PM UTC
      Owner: Jamie Cameron

      I have comcast dual stack 4/6. Windows 7 Firefox browser defaults to
      IPV6. Apache Webmin creates listener on IPV6, won't on IPV4. I know how
      to set the apache config up at the command line. It would seem that
      there is some problem with Webmin if the browser defaults to V6 and the
      connection to the VPS is on V6.


      No, it only listens on IPV6.

       
  • Jamie Cameron

    Jamie Cameron - 2013-12-18

    Make sure that at Servers -> Apache Webserver -> Networking and Addresses -> Listen on addresses and ports, you have a row that has "All" or your IPv4 address in the "Address" column.

     
    • Mike Maurice

      Mike Maurice - 2013-12-18

      On 12/17/2013 8:35 PM, Jamie Cameron wrote:

      Make sure that at Servers -> Apache Webserver -> Networking and
      Addresses -> Listen on addresses and ports, you have a row that has
      "All" or your IPv4 address in the "Address" column.
      Jamie,
      I tried setting it up such that the IPV4 address was the ONLY address to
      listen to. Apache still put out a listen ALL on IPV6, only.

      I will check this again.

      But, I would not have reported this if I wasn't fairly sure. After all,
      this is very strange.

      Mike

       
    • Mike Maurice

      Mike Maurice - 2013-12-18

      On 12/17/2013 8:35 PM, Jamie Cameron wrote:

      Make sure that at Servers -> Apache Webserver -> Networking and
      Addresses -> Listen on addresses and ports, you have a row that has
      "All" or your IPv4 address in the "Address" column.


      There is no: "All" or your IPv4 address in the "Address" column"

      In the: Servers -> Apache Webserver -> Networking and

      Addresses -> Listen on addresses and ports,

      There is a Networking and Address, but no: "Listen on..."

      Mike

       
    • Mike Maurice

      Mike Maurice - 2013-12-18

      On 12/17/2013 8:35 PM, Jamie Cameron wrote:

      Make sure that at Servers -> Apache Webserver -> Networking and
      Addresses -> Listen on addresses and ports, you have a row that has
      "All" or your IPv4 address in the "Address" column.


      By the way, I have the latest WebMin 1.666...

      Mike

       
      • Mike Maurice

        Mike Maurice - 2013-12-18

        Virtual Server Details
        Address Default server Any
        Port Default Any

        Inserting a ipv4 address with this address option, does NOT create a
        listener on the IPV4 address, but I do get :::80 on tcp6.

        Even thou I put in a full IPV6 address.

        What?

        Mike

         
  • Jamie Cameron

    Jamie Cameron - 2013-12-18

    Did you click the "Global" tab before the "Networking and Addresses" icon?

     
    • Mike Maurice

      Mike Maurice - 2013-12-18

      On 12/17/2013 9:57 PM, Jamie Cameron wrote:

      Did you click the "Global" tab before the "Networking and Addresses" icon?
      Probably not. Will check.

       
    • Mike Maurice

      Mike Maurice - 2013-12-18

      On 12/17/2013 9:57 PM, Jamie Cameron wrote:

      Did you click the "Global" tab before the "Networking and Addresses" icon?
      Yes, I think so. But, there does not seem to be anything there in global
      that would affect this issue.

      Mike

       
      • Mike Maurice

        Mike Maurice - 2013-12-18

        This issue is not a critical one for me. I don't have to have the V4
        working, right now. And I could hand edit the config files to get what I
        want. But, you are going to have many other users with similar setups to
        mine and I would think you want to get this figured out.

        I will be up for a while longer, but I don't expect this fixed tonight.
        I will try to help you ferret this out, even if it takes all week.
        No hurry. Send your questions and I will get you answers.

        Mike

         
  • Jamie Cameron

    Jamie Cameron - 2013-12-18

    Sorry, what I meant was to click on Networking and Addresses under the Global tab. There is another icon with the same name under Default Server that has different network settings.

     
    • Mike Maurice

      Mike Maurice - 2013-12-19

      Sorry, I did not get back to you yesterday. I babysat the grand kids and
      they keep me busy.

      More later.

      Mike

       
    • Mike Maurice

      Mike Maurice - 2013-12-19

      Networking and Addresses
      Multiple requests per connection None Default Keep-alive timeout Default
      Request timeout Default

      Jamie,
      There is NO address line on the page you are referring to. What is above
      is all there is.

      Under the circumstances I have no idea what you are talking about.

      The virtual server options is the only place I can find a place to
      insert an address.

      Virtual Server Details
      Address Default server Any
      Port Default Any
      Document Root Default
      Server Name Default

      What I may do is insert the correct configuration items and see where
      they end up when Webmin displays them.

      Mike

       
  • Jamie Cameron

    Jamie Cameron - 2013-12-19

    Yes, I'd be interested to see what changes you make to httpd.conf manually that fix this. I'm pretty surprised that Apache doesn't listen on an IPv4 address by default.

     
    • Mike Maurice

      Mike Maurice - 2013-12-19

      On 12/19/2013 1:43 PM, Jamie Cameron wrote:

      Yes, I'd be interested to see what changes you make to httpd.conf
      manually that fix this. I'm pretty surprised that Apache doesn't listen
      on an IPv4 address by default.


      Jamie,
      The situation is more complicated than I thought.
      It turns out that neither of the v4 or v6 virtual server addresses are
      being listened to. Only the default sever, which is on :::80, in effect:
      "all on v6 port 80".
      And ignoring the virtual server additions that I made.

      I know roughly what would be the cause, but not precisely.

      By the way, Webmin itself won't work on a V6 address. Perl is not
      listening to any v6 address.
      Also, if I change the Webimin port address to something like 11111, or
      whatever, perl keeps listening on 10000.

      Mike

       
  • Jamie Cameron

    Jamie Cameron - 2013-12-19

    I wonder if perhaps this happens because the IPv4 address wasn't active on your system when Webmin and Apache were started? If you restart Webmin or Apache does it start listening on IPv4 ?

     
    • Mike Maurice

      Mike Maurice - 2013-12-20

      On 12/19/2013 3:39 PM, Jamie Cameron wrote:

      I wonder if perhaps this happens because the IPv4 address wasn't active
      on your system when Webmin and Apache were started? If you restart
      Webmin or Apache does it start listening on IPv4 ?

      NO.

       
  • Jamie Cameron

    Jamie Cameron - 2013-12-20

    Ok .. what does the command "ifconfig -a" output on your system?

     
    • Mike Maurice

      Mike Maurice - 2013-12-25

      The issue that I was having appears to be as follows.

      The Ports.conf file contained a Listen directive: Listen :80

      My VPS has IPV6 as well as my internet connection.

      Apache was listening only on :::80 (IPV6), but never on IPV4.

      I solved the problem by having apache listen on a specific IPV4 and
      another IPV6 address like so. Required hand editing the Ports.conf file.

      Listen 2601:xxxxx 80
      Listen 23.123.123.2 80

      What do you make of this.

      Mike

       
  • Jamie Cameron

    Jamie Cameron - 2013-12-25

    That is surprising. What if you removed the : so it was just

    Listen 80

    I'd expect that to listen on all protocol types.

     
    • Mike Maurice

      Mike Maurice - 2013-12-26

      On 12/25/2013 3:43 PM, Jamie Cameron wrote:

      That is surprising. What if you removed the : so it was just

      Listen 80

      I'd expect that to listen on all protocol types.

      Don't know. But, all protocol types is not the same as IPV4 and 6.

      Will try that when I get a chance.

      Mike

       

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks