Howdy, Stranger!

It looks like you're new here. If you want to get involved, click one of these buttons!

Sign In Register

Quick Links


Categories

In this Discussion

› › OpenVZ IPv6 venet = Destination unreachable: Administratively prohibited
New on LowEndTalk? Please Register and read our Community Rules.

All new Registrations are manually reviewed and approved, so a short delay after registration may occur before your account becomes active.

OpenVZ IPv6 venet = Destination unreachable: Administratively prohibited

jmginerjmginer Member, Patron Provider
edited December 2013 in Help

Hello, we are configuring IPv6 to use inside our containers, in the host node, IPv6 run Ok, but we get error inside the container:

2a03:c7c0:1::1/48 - IPv6 gateway

2a03:c7c0:1::2/48 - IPv6 HostNode

2a03:c7c0:1::1:1/128 - IPv6 assigned to the container

CONFIG IN THE HOST NODE:

[root@ovz1-mad ~]# ifconfig
eth0      Link encap:Ethernet  HWaddr 00:25:90:C9:27:5E
          inet addr:5.134.116.11  Bcast:5.134.117.255  Mask:255.255.254.0
          inet6 addr: 2a03:c7c0:1::2/48 Scope:Global
          inet6 addr: fe80::225:90ff:fec9:275e/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:405324 errors:0 dropped:0 overruns:0 frame:0
          TX packets:342071 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:51938608 (49.5 MiB)  TX bytes:149320728 (142.4 MiB)
          Memory:f7180000-f7200000

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:2978 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2978 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:544356 (531.5 KiB)  TX bytes:544356 (531.5 KiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet6 addr: fe80::1/128 Scope:Link
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:162732 errors:0 dropped:0 overruns:0 frame:0
          TX packets:150083 errors:0 dropped:8 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:66672828 (63.5 MiB)  TX bytes:15845157 (15.1 MiB)



[root@ovz1-mad ~]# cat /etc/sysctl.conf
net.nf_conntrack_max = 500000
net.ipv4.ip_forward = 1
net.ipv4.ip_forward = 1
net.ipv6.conf.default.forwarding = 1
net.ipv6.conf.all.forwarding = 1
net.ipv6.conf.all.proxy_ndp = 1
net.ipv6.bindv6only = 1
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.conf.all.rp_filter = 1
kernel.sysrq = 1
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.all.send_redirects = 0    


[root@ovz1-mad ~]# ip -6 route show
unreachable ::/96 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable ::ffff:0.0.0.0/96 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:a00::/24 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:7f00::/24 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:a9fe::/32 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:ac10::/28 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:c0a8::/32 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:e000::/19 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
2a03:c7c0:1::1:1 dev venet0  metric 1024  mtu 1500 advmss 1440 hoplimit 4294967295
2a03:c7c0:1::/48 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
unreachable 3ffe:ffff::/32 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
fe80::1 dev venet0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev eth0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
fe80::/64 dev venet0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
default via 2a03:c7c0:1::1 dev eth0  metric 1  mtu 1500 advmss 1440 hoplimit 4294967295    


[root@ovz1-mad ~]# ping6 ipv6.google.com
PING ipv6.google.com(mil01s16-in-x10.1e100.net) 56 data bytes
64 bytes from mil01s16-in-x10.1e100.net: icmp_seq=1 ttl=57 time=24.0 ms
64 bytes from mil01s16-in-x10.1e100.net: icmp_seq=2 ttl=57 time=24.0 ms
64 bytes from mil01s16-in-x10.1e100.net: icmp_seq=3 ttl=57 time=24.1 ms
^C
--- ipv6.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2234ms
rtt min/avg/max/mdev = 24.022/24.086/24.160/0.187 ms

INSIDE THE CONTAINER:

[root@ovz1-mad ~]# vzctl enter 2009
entered into CT 2009
[root@mad /]#
[root@mad /]#
[root@mad /]# ifconfig
lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:24 errors:0 dropped:0 overruns:0 frame:0
          TX packets:24 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:2226 (2.1 KiB)  TX bytes:2226 (2.1 KiB)

venet0    Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:127.0.0.1  P-t-P:127.0.0.1  Bcast:0.0.0.0  Mask:255.255.255.255
          inet6 addr: 2a03:c7c0:1::1:1/128 Scope:Global
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1
          RX packets:148 errors:0 dropped:0 overruns:0 frame:0
          TX packets:146 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:13239 (12.9 KiB)  TX bytes:13162 (12.8 KiB)

venet0:0  Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
          inet addr:5.134.117.74  P-t-P:5.134.117.74  Bcast:5.134.117.74  Mask:255.255.255.255
          UP BROADCAST POINTOPOINT RUNNING NOARP  MTU:1500  Metric:1



[root@mad /]# ip -6 route show
unreachable ::/96 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable ::ffff:0.0.0.0/96 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:a00::/24 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:7f00::/24 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:a9fe::/32 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:ac10::/28 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:c0a8::/32 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
unreachable 2002:e000::/19 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
2a03:c7c0:1::1:1 dev venet0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
unreachable 3ffe:ffff::/32 dev lo  metric 1024  error -101 mtu 16436 advmss 16376 hoplimit 4294967295
fe80::/64 dev venet0  proto kernel  metric 256  mtu 1500 advmss 1440 hoplimit 4294967295
default dev venet0  metric 1  mtu 1500 advmss 1440 hoplimit 4294967295    


[root@mad /]# ping6 ipv6.google.com
PING ipv6.google.com(mil01s16-in-x10.1e100.net) 56 data bytes
From 2a03:c7c0:1::2 icmp_seq=1 Destination unreachable: Administratively prohibited
From 2a03:c7c0:1::2 icmp_seq=2 Destination unreachable: Administratively prohibited
From 2a03:c7c0:1::2 icmp_seq=3 Destination unreachable: Administratively prohibited
^C
--- ipv6.google.com ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 2348ms

THIS IS THE IPV6 CONFIG IN SOLUSVM

http://prntscr.com/2caqux

Any idea about the problem?

Thanks.

Thanked by 18QE

Comments

  • rds100rds100 Member

    Check ip6tables on the host node. CentOS has some stupid defaults.

    Thanked by 2jmginer 8QE
  • SpeedBusSpeedBus Member, Host Rep

    Yep exactly what @rds100 said, turn off ip6tables for a sec to check and it'll most likely be that.

    Thanked by 1jmginer
  • jmginerjmginer Member, Patron Provider

    @rds100 said:
    Check ip6tables on the host node. CentOS has some stupid defaults.

    OOOhhhh!!! thanks!! is solved now!

    [root@ovz1-mad ~]# ip6tables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
ACCEPT     all      anywhere             anywhere            state RELATED,ESTABLISHED
ACCEPT     ipv6-icmp    anywhere             anywhere
ACCEPT     all      anywhere             anywhere
ACCEPT     tcp      anywhere             anywhere            state NEW tcp dpt:ssh
REJECT     all      anywhere             anywhere            reject-with icmp6-adm-prohibited

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
SOLUSVM_TRAFFIC_IN  all      anywhere             anywhere
SOLUSVM_TRAFFIC_OUT  all      anywhere             anywhere
REJECT     all      anywhere             anywhere            reject-with icmp6-adm-prohibited

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain SOLUSVM_TRAFFIC_IN (1 references)
target     prot opt source               destination

Chain SOLUSVM_TRAFFIC_OUT (1 references)
target     prot opt source               destination
[root@ovz1-mad ~]#
[root@ovz1-mad ~]#
[root@ovz1-mad ~]# ip6tables -F
[root@ovz1-mad ~]#
[root@ovz1-mad ~]#
[root@ovz1-mad ~]# ip6tables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain SOLUSVM_TRAFFIC_IN (0 references)
target     prot opt source               destination

Chain SOLUSVM_TRAFFIC_OUT (0 references)
target     prot opt source               destination
[root@ovz1-mad ~]#
[root@ovz1-mad ~]#
[root@ovz1-mad ~]# vzctl enter 2009
entered into CT 2009
[root@mad /]#
[root@mad /]# ping ipv6.google.com
ping: unknown host ipv6.google.com
[root@mad /]#
[root@mad /]# ping6 ipv6.google.com
PING ipv6.google.com(mil01s16-in-x12.1e100.net) 56 data bytes
64 bytes from mil01s16-in-x12.1e100.net: icmp_seq=1 ttl=56 time=24.1 ms
64 bytes from mil01s16-in-x12.1e100.net: icmp_seq=2 ttl=56 time=24.0 ms
64 bytes from mil01s16-in-x12.1e100.net: icmp_seq=3 ttl=56 time=24.1 ms
^C
--- ipv6.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2047ms
rtt min/avg/max/mdev = 24.060/24.129/24.196/0.055 ms
[root@mad /]#
[root@mad /]#
[root@mad /]# Thanks @rds100 & LET community!!!!
Thanks @rds100 & LET communityping6 ipv6.google.comping6 ipv6.google.com
[1] 664
-bash: LET: command not found
[root@mad /]# -bash: Thanks: command not found

[1]+  Exit 127                Thanks @rds100
[root@mad /]#
  • jmginerjmginer Member, Patron Provider

    So, IPv6 is ready on GINERNET Madrid location :)

    Thanked by 1linuxthefish
  • rds100rds100 Member

    You don't want to entirely clear the ip6tables on the hostnode, at least set filter for ssh over ipv6 (INPUT chain), or people will fill the logs on the node with bruteforce ssh attemts.

    Thanked by 1jmginer
  • jmginerjmginer Member, Patron Provider
    edited December 2013

    @rds100 said:
    You don't want to entirely clear the ip6tables on the hostnode, at least set filter for ssh over ipv6 (INPUT chain), or people will fill the logs on the node with bruteforce ssh attemts.

    :S Never heard about this...
    Same on IPv4?
    What logs?
    Any example?

    What do you think about this?

    iptables -A INPUT -p tcp --dport 22 --syn -m limit --limit 1/m --limit-burst 10 -j ACCEPT
iptables -A INPUT -p tcp --dport 22 --syn -j DROP
ip6tables -A INPUT -p tcp --dport 22 --syn -m limit --limit 1/m --limit-burst 10 -j ACCEPT
ip6tables -A INPUT -p tcp --dport 22 --syn -j DROP

    Thanks very much!!

  • rds100rds100 Member

    If you don't intend to login via ssh to the node over ipv6, you can just add the DROP, without the ACCEPT before it.

  • jmginerjmginer Member, Patron Provider

    @rds100 said:
    If you don't intend to login via ssh to the node over ipv6, you can just add the DROP, without the ACCEPT before it.

    Thanks!
    Can you provide me more info about the hack? What logs you say?

  • rds100rds100 Member

    It's just the standard ssh bruteforcers that try to login with different passwords. They can do it over ipv4 and ipv6. Most people know to put filter on ipv4, but never bother to put filters on ipv6, and think they are secure.

    Thanked by 1jmginer
  • WintereiseWintereise Member

    ip6tables is needed for v6 bw accounting, as per Solus.

    You just need to remove the two reject-with adm rules in the ip6tables startup file in sysconfig/, and then flush ip6tables and re-init it.

    Thanked by 1jmginer
  • jmginerjmginer Member, Patron Provider

    So, I have restored the previous ip6tables files,
    removed both reject-with lines,
    and added a new line to dont permit SSH via ipv6 on HN,

    this is the result:

    [root@ovz1-mad ~]# cat /etc/sysconfig/ip6tables
# Generated by ip6tables-save v1.4.7 on Thu Dec 19 15:20:02 2013
*mangle
:PREROUTING ACCEPT [697:92130]
:INPUT ACCEPT [83:5872]
:FORWARD ACCEPT [89:29883]
:OUTPUT ACCEPT [109:10164]
:POSTROUTING ACCEPT [220:41631]
COMMIT
# Completed on Thu Dec 19 15:20:02 2013
# Generated by ip6tables-save v1.4.7 on Thu Dec 19 15:20:02 2013
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:SOLUSVM_TRAFFIC_IN - [0:0]
:SOLUSVM_TRAFFIC_OUT - [0:0]
[0:0] -A INPUT -p tcp -m tcp --dport 22 --tcp-flags FIN,SYN,RST,ACK SYN -j DROP
[0:0] -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT
[0:0] -A INPUT -p ipv6-icmp -j ACCEPT
[0:0] -A INPUT -i lo -j ACCEPT
[0:0] -A FORWARD -j SOLUSVM_TRAFFIC_IN
[0:0] -A FORWARD -j SOLUSVM_TRAFFIC_OUT
COMMIT
# Completed on Thu Dec 19 15:20:02 2013
  • jmginerjmginer Member, Patron Provider 
    [root@ovz1-mad ~]# ip6tables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
DROP       tcp      anywhere             anywhere            tcp dpt:ssh flags:FIN,SYN,RST,ACK/SYN
ACCEPT     all      anywhere             anywhere            state RELATED,ESTABLISHED
ACCEPT     ipv6-icmp    anywhere             anywhere
ACCEPT     all      anywhere             anywhere

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
SOLUSVM_TRAFFIC_IN  all      anywhere             anywhere
SOLUSVM_TRAFFIC_OUT  all      anywhere             anywhere

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

Chain SOLUSVM_TRAFFIC_IN (1 references)
target     prot opt source               destination

Chain SOLUSVM_TRAFFIC_OUT (1 references)
target     prot opt source               destination
  • jmginerjmginer Member, Patron Provider

    IPv6 run ok on containers!
    Thanks very much!!!!

  • conlustroconlustro Member

    I'm having the same exact problem above but changing my tables didn't fix the problem.

    I get the following:

    [root@localhost ~]# cat /etc/sysconfig/ip6tables
# Generated by ip6tables-save v1.4.7 on Thu Jul 24 02:10:01 2014
*filter
:INPUT ACCEPT [0:0]
:FORWARD ACCEPT [0:0]
:OUTPUT ACCEPT [0:0]
:SOLUSVM_TRAFFIC_IN - [0:0]
:SOLUSVM_TRAFFIC_OUT - [0:0]
[0:0] -A FORWARD -j SOLUSVM_TRAFFIC_IN 
[0:0] -A FORWARD -j SOLUSVM_TRAFFIC_OUT 
COMMIT
# Completed on Thu Jul 24 02:10:01 2014
[root@localhost ~]# ip6tables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination         

Chain FORWARD (policy ACCEPT)
target     prot opt source               destination         
SOLUSVM_TRAFFIC_IN  all      anywhere             anywhere            
SOLUSVM_TRAFFIC_OUT  all      anywhere             anywhere            

Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination         

Chain SOLUSVM_TRAFFIC_IN (1 references)
target     prot opt source               destination         

Chain SOLUSVM_TRAFFIC_OUT (1 references)
target     prot opt source               destination

    Upon restart of the Host Node I get:

    [root@localhost ~]# service network restart
Shutting down interface eth0:                              [  OK  ]
Shutting down interface venet0:  Shutting down interface venet0: 
                                                           [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface eth0:  Determining if ip address 192.99.208.192 is already in use for device eth0...
Global IPv6 forwarding is disabled in configuration, but not currently disabled in kernel
Please restart network with '/sbin/service network restart'
ndsend: Error in sendto(): Cannot assign requested address
ifup-local WARNING: arpsend -c 1 -w 1 -U -i 2607:5300:60:5ad0:0:0:0:4 -e 2607:5300:60:5ad0:0:0:0:4 eth0 FAILED
                                                           [  OK  ]
Bringing up interface venet0:  Bringing up interface venet0: 
Configuring interface venet0: 
net.ipv4.conf.venet0.send_redirects = 0
Configuring ipv6 venet0: 
ndsend: Error in sendto(): Cannot assign requested address
ifup-venet WARNING: arpsend -c 1 -w 1 -U -i 2607:5300:60:5ad0:0:0:0:4 -e 2607:5300:60:5ad0:0:0:0:4 eth0 FAILED
                                                           [  OK  ]

    IPv6 address: 2607:5300:60:5ad0:0:0:0:4 belongs to the openvz container. I entered it into solusvm and then gave it to the container. I'm using 2607:5300:0060:5eff:00ff:00ff:00ff:00ff as my default gateway for ip address 2607:5300:60:5ad0:: as per OVH.

    When I enter the container I get:

    [root@localhost ~]# vzctl enter 101
entered into CT 101
[root@plesk /]# ping6 ipv6.google.com
PING ipv6.google.com(iad23s05-in-x00.1e100.net) 56 data bytes
^C
--- ipv6.google.com ping statistics ---
8 packets transmitted, 0 received, 100% packet loss, time 7477ms

    Can anyone tell me what I should put in the ip6tables to get this work, or should i check for other things?

  • conlustroconlustro Member

    Here are is my routing table from the Host Node:

    [root@localhost ~]# route -n -A inet6
Kernel IPv6 routing table
Destination                                 Next Hop                                Flags Metric Ref    Use Iface
2607:5300:60:5ad0::4/128                    ::                                      U     1024   0        0 venet0  
2607:5300:60:5ad0::/64                      ::                                      U     256    0        0 eth0    
2607:5300:60:5aff:ff:ff:ff:ff/128           ::                                      U     1024   2        0 eth0    
fe80::1/128                                 ::                                      U     256    0        0 venet0  
fe80::/64                                   ::                                      U     256    0        0 eth0    
fe80::/64                                   ::                                      U     256    0        0 venet0  
::/0                                        2607:5300:60:5aff:ff:ff:ff:ff           UG    1      0        0 eth0    
::/0                                        2607:5300:60:5aff:ff:ff:ff:ff           UG    1024   84       0 eth0    
::1/128                                     ::                                      U     0      20       1 lo      
2607:5300:60:5ad0::/128                     ::                                      U     0      47       1 lo      
fe80::/128                                  ::                                      U     0      0        1 lo      
fe80::1/128                                 ::                                      U     0      0        1 lo      
fe80::ec4:7aff:fe01:f408/128                ::                                      U     0      91       1 lo      
ff00::/8                                    ::                                      U     256    0        0 eth0    
ff00::/8                                    ::                                      U     256    0        0 venet0
  • ErawanArifNugrohoErawanArifNugroho Member

    @conlustro, what's your /etc/ssyctl.conf for the IPv6? And have you try to add it to load the sysctl at boot?

  • conlustroconlustro Member

    /etc/ssyctl.conf file does not exist on my server or my container.

  • wxserverswxservers Member

    its not /etc/ssyctl.conf it is /etc/sysctl.conf

  • Falco33Falco33 Member

    @conlustro said:
    /etc/ssyctl.conf file does not exist on my server or my container.

    Check /etc/sysctl.conf

  • conlustroconlustro Member

    I got:

    net.ipv4.ip_forward = 1
net.ipv4.ip_forward = 1
net.ipv6.conf.default.forwarding = 1
net.ipv6.conf.all.forwarding = 1
net.ipv4.conf.default.proxy_arp = 0
net.ipv4.conf.all.rp_filter = 1
kernel.sysrq = 1
net.ipv4.conf.default.send_redirects = 1
net.ipv4.conf.all.send_redirects = 0
  • ErawanArifNugrohoErawanArifNugroho Member

    Sorry for the typo :D

    If we use Proxmox VE3, it will have a problem with the loading sysctl.conf at boot, so we need to load it in the /etc/network/interfaces.

    After adding

    net.ipv6.conf.all.proxy_ndp = 1

    and running systcl -p, you should try again for the IPv6 connection

  • conlustroconlustro Member
    edited July 2014

    IT WORKS! Thanks everyone!

    Did changing the ipv6 gateway have anything to do with it working, or did I need to not mess with the gateway?

    When I got to http://[2607:5300:60:5ad0::4]/ it doesn't go to the default apache webpage like the ipv4 address does, how do I get the ipv6 address to resolve?

  • SandwichBagGhostSandwichBagGhost Member

    ^

    Is Apache configured to listen on IPv4 and IPv6? If not, configure it to do.

  • wxserverswxservers Member

    how do I get the ipv6 address to resolve? - add them to your powerdns and add AAAA record

  • conlustroconlustro Member

    I have:

    Listen 80

    in the httpd.conf is that enough or what do I need to put in there to make it listen on both ipv6 and ipv4?

  • SandwichBagGhostSandwichBagGhost Member

    conlustro said: I have:

    Read http://httpd.apache.org/docs/2.2/en/bind.html and http://www.tldp.org/HOWTO/Linux+IPv6-HOWTO/hints-daemons-apache2..html

  • conlustroconlustro Member

    I added the ip in plesk 12 and it came up fine and then i gave the ip to a domain in plesk and set my AAAA records but it still isn't showing up. I think I might have my ipv6 gateway address wrong.

  • linuxthefishlinuxthefish Member
    edited July 2014

    My VPS is moved to ali1.ovz1 now! :(

    Any IPv6 in that location soon? Port speed also slower!

Sign In or Register to comment.