Tag Info

Hot answers tagged

12

If the ISP won't give you more than a /64, then that ISP sucks. If it is any relief I can tell you that I have deal with ISPs that suck even more than that. Around here it is perfectly normal to take public IPv4 addresses away from customers and put them behind a CGN. And if you ask them for IPv6 addresses, they will tell you that they are not offering IPv6 ...


7

Yes, pressuring your ISP to not suck is the preferred option. RIR allocation policies assume that the ISP is giving each customer a /48; there is absolutely zero reason for the ISP to not do that. IPv6 is not a fan of smaller subnets, however the only thing that is supposed to break, that I'm aware of, is SLAAC. You'll have problems with bugs and ...


5

Read the relevant documentation for your product. http://pubs.vmware.com/vsphere-60/index.jsp?topic=%2Fcom.vmware.vsphere.networking.doc%2FGUID-6BC115DF-4EC5-409E-8B74-45525E966F0F.html The documentation clearly states that ipv6 is not supported for ESXi -> Active Directory communication. (as of 6.0.)


4

Shopify doesn't support IPv6 (which may be a big problem for you later) so just remove the old AAAA record. Your DNS records appear to be hosted by "Web-2u Limited".


4

The protocol combination you want to use for that is DNS64/NAT64. The combination of NAT and DNS will make the whole internet look like IPv6 from your local IPv6 LAN. There are also some public services that let you try this out. I know of some in Slovenia run by Go6 / Jan Žorž ...


4

You need to get yourself a better colo provider. They should be giving you much larger allocations than a /64 for a routed infrastructure. That being said, in properly implemented equipment, there's no need to use a full /64 subnet, so in principle what you've described should be workable, modulo your provider being setup correctly, all your equipment ...


3

as noted in the updates to the question, the problem is that after the kernel passes the packet to whatever raw sockets are listening on that protocol, it then hands it off to any kernel modules registered for that same protocol. since I had been using a sit tunnel on my netbook, the tunnel4 module was still loaded even though I had temporarily set up the ...


2

You need IPv6 connectivity from your ISP to be able to use IPv6. AWS is known to not support IPv6 on their instances. You have to make your ISP do the right thing and provide you with IPv6 or you have to get IPv6 using e.g. tunnelbroker.net


1

Sounds like what you need is a 6in4 tunnel. If you have a routed prefix on your dual stack server, then you can set up your own tunnel server. Otherwise you can use one of the many free tunnel providers. Based on my overall experience with various providers, I recommend Hurricane Electric. You could replace the 6in4 tunnel with a site-to-site VPN. The ...


1

I managed to resolve this. It turns out someone else had a similar question: IPv6 with IPv4 over RRAS SSTP VPN from Client that only has IPv4 access Turns out its because the client doesn't have a properly configured route back to the VPN with IPv6, so the traffic has no where to go. I needed to add a static route at the router level. I changed my RRAS ...


1

Your firewall is configured to drop all traffic, even without any rules. This will be the source of your problem. Chain INPUT (policy DROP) Chain OUTPUT (policy DROP) Reset the policies of these tables to ACCEPT to restore connectivity. ip6tables -P INPUT ACCEPT ip6tables -P OUTPUT ACCEPT Then you can get on with constructing a proper firewall.


1

jcomeau@aspire:~/rentacoder/jcomeau/kybyz$ sudo ip route add local ::/104 dev lo jcomeau@aspire:~/rentacoder/jcomeau/kybyz$ ping6 ::2 PING ::2(::2) 56 data bytes 64 bytes from ::2: icmp_seq=1 ttl=64 time=0.083 ms 64 bytes from ::2: icmp_seq=2 ttl=64 time=0.128 ms ^C --- ::2 ping statistics --- 2 packets transmitted, 2 received, 0% packet loss, time 999ms ...


1

I thought I'd provide a more generic Linux router scenario for users not using pfSense but a Linux based router (in my case DD-WRT). ip -6 route add xxxx:xxx:xxxx:xxxx::/64 via xxxx:xxx:xxxx:xx::x dev br0 The configured IPv6 prefix in RRAS IPv6 tab needs to be added after the add The IPv6 LAN IP address of the RRAS box is the via (essentially the ...


1

The problem is that your firewall is not stateful, and it only allowed traffic to pass in one direction. There is nothing here to allow return traffic. So, while a client request is passed through, the response from the server doesn't match any rules and is dropped. Write instead normal stateful rules. For example: -A FORWARD -m conntrack --ctstate ...


1

It looks like tektonic does not have the address 2001:470:1f0e:12a7::2 assigned to its venet0 interface. It is receiving the packets and rejecting them even though they are well-formed. Your next step should be to verify that tektonic can establish TCP connections to IPv6-only hosts such as ipv6.google.com, and that the packets indeed travel to the ...


1

The ICMP errors are send by the kernel because no socket exists to receive protocol 41 packets with that particular combination of source and destination IP address. If a process creates a raw socket with protocol 41, then the kernel will stop producing the ICMP errors. Such a socket by default will receive packets from all source IP send to any destination ...



Only top voted, non community-wiki answers of a minimum length are eligible