Tag: IPv6

Low prices for /22, /23, /24 from RIPE IPv4 and IPv6 lease. ASN registration also possible!


Hi there,

we have IPv4 addresses /22, /23, /24 and IPv6 addresses for lease. An ASN Registration is also possible.

We are a solid German business with offices in Stuttgart and Munich.

The Prices are:

IPv4:

/24 = 65€ per month

/23 = 125€ per month

/22 = 240€ per month

IPv6:

/48 = 20€ per Month

bigger than /48 = Ask us

ASN registration:

20€ per Month

We are looking especially for long-term agreements.

You can find more information at https://develapp.me/en/rent-ip-address/.

Feel free to contact us directly via ip@develapp.me or via the contact form at our website!

Business Contact:

Mo’s Operations GmbH

Konrad-Zuse-Straße 12

D-70134 Böblingen

and

Franz-Joseph-Str. 11

D-80801 Munich

hello@develapp.me
develapp.me

Can GSA use IPv6 proxies?

I searched and the last questionanswers about this was 2 years ago. Any updates? Is the current GSA compatible with IPv6 proxies? 
Thanks in advance.

The reason behind IPv6 adoption rate dramatical drop in China according to Google measurements?

Google has an IPv6 measurement page that reports that their numbers report on the percentage of users that access Google over IPv6.

According to the report by Jan 2020 0.3% of users in China used IPv6 to access Google

However, looking at this metric in dynamic we see the substantial drop starting from June 2019.
enter image description here

I failed to find any solid news that may cause such behavior. I have two hypotheses in mind.

  1. Also as it is a percentage metric, they can adjust their calculation on the total internet penetration rate in China.
  2. Previously open discussions between netizens took place on Google Plus groups. In April 2019,
    Google shut down Google Plus. Technical discussions continue on
    Chinese-language blogs, forums, and groups. For obvious reasons,
    discussions must be hosted outside China, and posters must register under pseudonyms. So probably that caused the shift from Google services but I hardly believe that it may cause such plummet.

when will ipv6 replace ipv4 entirely ?

Hi,

some people begin use ipv6,

do you think when will ipv6 replace ipv4 entirely ?… | Read the rest of https://www.webhostingtalk.com/showthread.php?t=1808923&goto=newpost

windows – Why can I ping an ipv6 but not an ipv4 and vice versa? (Hamachi)

I’m using Hamachi LogMe-In to connect a laptop (A with Win8.1) to a work computer (B with Win10) for SSH, both running Windows Firewall allowing SSH port 22, and the PING.EXE.

Somehow I got that to work. Then I tried to open a port for another python app on a different port trying to communicate for a remote computation setup, and it’s not working as expected. Trying to debug I was pinging (after allowing ping.exe on both machines through FW) the different machines from each side, and to my surprise I found this happening.

# On: machine A
ping -4 <ipv4-B> 
# results in timeout!

# On: machine A
ping -6 <ipv6-B>
# OK

Then doing the opposite:

# On: machine B
ping -4 <ipv4-A> 
# OK

# On: machine B
ping -6 <ipv6-A>
# results in timeout!

What is going on?

My Hamachi machines are green on both sides so that connection seem ok.
So I guess it must be some FW thing going on in windows.
How can I debug and understand this?

Possibly related questions (but not helpful to my case):

network – ipv6 and dnsmasq on lan. Macs have no route to host, Windows and Linux work

I have a small mixed network of ubuntu linux (20.04) windows 10 and three macs. My ISP is starting to assign IPv6 (not yet in my area), and wanted to try on my network.
I manage the network using dnsmasq (running on the Ubuntu server) and it allocates the IP address and works as a caching DNS server.
I have disabled all IPv6 options on my router (other than the firewall)

To start testing IPv6, I added the following lines to dnsmasq.conf:

dhcp-range=fd52:a81c:df85::02,fd52:a81c:df85::ff,12h
enable-ra
ra-param=net1,0,0

and sympathetically, it works for Windows and Linux machines. for example

nick@serv2:~$ ping6 htpc
PING htpc(htpc.njj.chickenkiller.com (fd52:a81c:df85::85)) 56 data bytes
64 bytes from htpc.njj.chickenkiller.com (fd52:a81c:df85::85): icmp_seq=1 ttl=64 time=0.573 ms

However, all macs seem unhappy with the configuration, for example:

nick@deathrow ~ % ping6 serv2
ping6: UDP connect: No route to host

In the background, the ifconfig on my mac is as follows:

nick@deathrow ~ % ifconfig en0
en0: flags=8863 mtu 1500
    options=400
    ether 34:36:3b:78:15:54 
    inet6 fe80::64:48f:2265:db5%en0 prefixlen 64 secured scopeid 0x5 
    inet 192.168.2.49 netmask 0xffffff00 broadcast 192.168.2.255
    inet6 fd52:a81c:df85::2c prefixlen 64 dynamic 
    nd6 options=201
    media: autoselect
    status: active

The other oddity is when I look at the leases issued by dnsmasq I get the following:

nick@serv2:~$ cat /var/lib/misc/dnsmasq.leases
1589092434 34:36:3b:78:15:54 192.168.2.49 deathrow 01:34:36:3b:78:15:54
1589085665 b4:2e:99:41:5d:bc 192.168.2.11 kenickie 01:b4:2e:99:41:5d:bc
1589081204 38:f9:d3:90:fd:dd 192.168.2.50 richard 01:38:f9:d3:90:fd:dd
1589084172 8c:85:90:56:bc:bf 192.168.2.48 Hal 01:8c:85:90:56:bc:bf
1589093362 70:85:c2:7d:06:f7 192.168.2.91 htpc ff:48:6b:fd:2c:00:02:00:00:ab:11:ae:2f:a0:8e:34:1e:dd:53
1589093437 b4:2e:99:02:99:47 192.168.2.89 DESKTOP-N5V06NB 01:b4:2e:99:02:99:47
duid 00:01:00:01:26:49:5c:40:18:31:bf:6a:35:bc
1589085667 611457736 fd52:a81c:df85::b3 kenickie 00:04:ae:f8:4e:bd:71:95:c3:42:1b:ef:bd:3b:8f:e6:1a:86
1589093364 1215036716 fd52:a81c:df85::85 htpc 00:02:00:00:ab:11:ae:2f:a0:8e:34:1e:dd:53
1589093429 112471705 fd52:a81c:df85::11 DESKTOP-N5V06NB 00:01:00:01:25:90:f0:6c:b4:2e:99:02:99:47
1589080658 0 fd52:a81c:df85::42 * 00:01:00:01:25:b1:94:dc:38:f9:d3:90:fd:dd
1589084172 0 fd52:a81c:df85::f * 00:01:00:01:22:48:2d:b0:8c:85:90:56:bc:bf
1589092435 0 fd52:a81c:df85::2c * 00:01:00:01:24:86:78:14:34:36:3b:78:15:54

You can see that the three Macs (deathrow, Hal and Richard) all get their IPv4 names listed ok, but for IPv6 you can see (lest three lines) their names are replaced by * (ubuntu hosts – kenickie and htpc, and the Windows machine DESKTOP-N5V06NB) are listed with an IPv6 address by name. (serv2 is not listed – it has a static address)

Do I need to do something more in dnsmasq for Mac (or did I do something fundamentally and it's just that Macs are less tolerant)?

network – How to activate IPv6 in Docker?

I use docker on an IPv6 host only.

I did it as a document

/etc/docker/daemon.json
{
  "ipv6": true,
  "fixed-cidr-v6": "xxxx:xxxx:xxxx:xxxx::/64"
}

Restart docker.

Create a new network

docker network create --ipv6 --subnet=xxxx:xxxx:xxxx::/64 awx

Connect a running app in Docker to the new network

docker network connect awx awx_web

From there I know I should do these two things

  • / usr / sbin / sysctl net.ipv6.conf.interface_name.proxy_ndp = 1
  • / usr / bin / ip -6 neigh add proxy $ (docker inspect –format {{.NetworkSettings.GlobalIPv6Address}} container_name) dev interface_name "

Iran ip -6 route had

unreachable ::/96 dev lo metric 1024 error -113 pref medium
unreachable ::ffff:0.0.0.0/96 dev lo metric 1024 error -113 pref medium
unreachable 2002:xxxx::/24 dev lo metric 1024 error -113 pref medium
unreachable 2002:xxxx::/24 dev lo metric 1024 error -113 pref medium
unreachable 2002:xxxx::/32 dev lo metric 1024 error -113 pref medium
unreachable 2002:xxxx::/28 dev lo metric 1024 error -113 pref medium
unreachable 2002:xxxx::/32 dev lo metric 1024 error -113 pref medium
unreachable 2002:xxxx::/19 dev lo metric 1024 error -113 pref medium
xxxx:xxxx:xxxx::/64 dev br-xxxxxxxx proto kernel metric 256 pref medium
xxxx:xxxx:xxxx::/64 dev br-xxxxxxxx metric 1024 pref medium
xxxx:xxxx:xxxx:xxxx::/64 dev lan0 proto kernel metric 256 pref medium
xxxx:xxxx:xxxx:xxxx::/64 dev docker0 proto kernel metric 256 pref medium
xxxx:xxxx:xxxx:xxxx::/64 dev docker0 metric 1024 pref medium
unreachable xxxx:xxxx::/32 dev lo metric 1024 error -113 pref medium
fb80::/64 dev lan0 proto kernel metric 256 pref medium
fb80::/64 dev docker0 proto kernel metric 256 pref medium
fb80::/64 dev br-xxxxxxxx proto kernel metric 256 pref medium
fb80::/64 dev br-xxxxxxxx proto kernel metric 256 pref medium
fb80::/64 dev br-xxxxxxxx proto kernel metric 256 pref medium
fb80::/64 dev br-xxxxxxxx proto kernel metric 256 pref medium
fb80::/64 dev br-xxxxxxxx proto kernel metric 256 pref medium
fb80::/64 dev xxxxxxxxxxx proto kernel metric 256 pref medium
fb80::/64 dev xxxxxxxxxxx proto kernel metric 256 pref medium
fb80::/64 dev xxxxxxxxxxx proto kernel metric 256 pref medium
fb80::/64 dev xxxxxxxxxxx proto kernel metric 256 pref medium
fb80::/64 dev xxxxxxxxxxx proto kernel metric 256 pref medium
fb80::/64 dev br-xxxxxxxx proto kernel metric 256 pref medium
fb80::/64 dev xxxxxxxxxxx proto kernel metric 256 pref medium
default via xxxx:xxxx:xxxx:xxxx::ffff dev lan0 metric 1 pref medium

Then ran

# /usr/sbin/sysctl net.ipv6.conf.lan0.proxy_ndp=1
(sccessed)

# ip -6 neigh add proxy $(docker inspect --format {{.NetworkSettings.Networks.awx.GlobalIPv6Address}} awx_web) dev lan0
(sccessed)

I check the IPv6Address value in the awx_web container

# docker inspect --format {{.NetworkSettings.Networks.awx.GlobalIPv6Address}} awx_web
xxxx:xxxx:xxxx::2

Log into web container verification ip a can also find this IP (xxxx: xxxx: xxxx :: 2). But unable to ping the remote server via IPv6 in the container.

Is the dev lan0 in full ip -6 neigh add proxy order?

Why have the networks not linked?

I read this article. This is a good explanation but all the networks are in the containers. I want to connect from the container to the external remote physical host with the same IPv6 segment.

tcp – Connection to some IPv6 stops working

Sometimes (as at present), I can no longer connect from my Fedora laptop to many servers via TCP over IPv6 (initially via Wifi).

Symptoms

❯ sudo traceroute6 www.wikipedia.org --port=443 --tcp
traceroute to www.wikipedia.org (2620:0:862:ed1a::1), 30 hops max, 80 byte packets
 1  * * *
...
30  * * *

# To some other hosts, the connection works
❯ sudo traceroute6 www.google.com --port=443 --tcp  
traceroute to www.google.com (2a00:1450:4001:809::2004), 30 hops max, 80 byte packets
 1  p200300F8DBC27036763170FFFE1F601C.dip0.t-ipconnect.de (2003:f8:dbc2:7036:7631:70ff:fe1f:601c)  1.316 ms  2.984 ms  2.885 ms
...
 7  fra16s42-in-x04.1e100.net (2a00:1450:4001:809::2004)  18.971 ms  18.846 ms  19.418 ms

# UDP works
❯ sudo traceroute6 www.wikipedia.org --port=443      
traceroute to www.wikipedia.org (2620:0:862:ed1a::1), 30 hops max, 80 byte packets
 1  p200300F8DBC27036763170FFFE1F601C.dip0.t-ipconnect.de (2003:f8:dbc2:7036:7631:70ff:fe1f:601c)  5.281 ms  5.178 ms  5.118 ms
...
 8  adm-b3-v6.telia.net (2001:2000:3018:67::1)  39.710 ms  41.436 ms  40.402 ms
 9  * * *
...

# IPv4 works
❯ sudo traceroute www.wikipedia.org --port=443 --tcp 
traceroute to www.wikipedia.org (91.198.174.192), 30 hops max, 60 byte packets
 1  _gateway (192.168.2.1)  3.211 ms  3.571 ms  3.882 ms
...
 6  text-lb.esams.wikimedia.org (91.198.174.192)  34.740 ms  27.594 ms  27.800 ms

# ICMPv6 method does not work at all (ICMPv4 works)
❯ sudo traceroute6 www.google.com --icmp           
traceroute to www.google.com (2a00:1450:4001:809::2004), 30 hops max, 80 byte packets
 1  * * *
...
30  * * *
  • https://ipv6-test.com/ shows that IPv6 is not supported after an expiration time.
  • I can loop a web page on IPv6, another web page in the same subnet 2a03:4000 do not.
  • Wireshark shows that TCP retransmission packages are sent after SYN and that some ICMPv6 "Destination unreachable" packages arrive at runtime traceroute6 with UDP.

Countermeasures (not 100% sure)

  • Rebooting often solves the problem.
  • Restarting Wifi rarely solves the problem.

domain name system – In the / etc / hosts file, why should IPv4 hosts be different from IPv6 hosts?

Context: CentOS 8, digital ocean droplet.

Question 1) I just looked at my hosts file in / etc / hosts and noticed that the host names listed under IPv4 and IPv6 are different. IPv4 lists example, example.com and mail.example.com while IPv6 only lists example example. Is it correct? Intuitively, it makes sense to me that they should be the same for IPv4 and IPv6.

# The following lines are desirable for IPv4 capable hosts
127.0.0.1 example example.com mail.example.com
127.0.0.1 localhost.localdomain localhost
127.0.0.1 localhost4.localdomain4 localhost4

# The following lines are desirable for IPv6 capable hosts
::1 example example
::1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

Question 2) I compared this to a second domain hosted on a separate Digital Ocean droplet and the content of this host file was very different. When I sent a test email to verifier-feedback@port25.com this domain failed iprev verification Result: fail (reverse lookup failed (NXDOMAIN)). Could it be because example is listed instead of fqdn example.com?

# The following lines are desirable for IPv4 capable hosts
127.0.0.1 example2 example2
127.0.0.1 localhost.localdomain localhost
127.0.0.1 localhost4.localdomain4 localhost4

# The following lines are desirable for IPv6 capable hosts
::1 example2 example2
::1 localhost.localdomain localhost
::1 localhost6.localdomain6 localhost6

Domain Name System – IPv4 to IPv6 Migration Tips

I am currently working on adding IPv6 capabilities to our network, and I have questions about what is considered best practice in 2020 to convert some of the IPv4 concepts that we are used to in the IPv6 world.

In the current configuration I have, we have allocated a / 64 from the ISP, and the router announces this prefix for clients to configure using SLAAC. It seems to be working fine and as far as I know, everyone has IPv6 internet access.

However, we like being able to query things by name, and I'm not sure what is the best practice for providing AAAA records for clients.

What I did is deploy stateful DHCPv6 on the dnsmasq instance that runs our DHCPv4 and tell it to distribute ULAs from a certain range that naturally provides records AAAA for anyone requesting an address. It also seems to be working fine, but I know there is some dislike for stateful DHCPv6. It also helps me to consolidate the allocation of the servers we have on static IP addresses exactly as I do for DHCPv4, these servers for various reasons should be accessible to a fixed IP address and we would like that continues to be the case for IPv6.

The only other way I can think of to make AAAA recordings is to send the dnsmasq machine the RA prefix of the router via unicast, then use the dnsmasq to advertise the GUA prefix for slaac using the ra-names option. As far as I know, this would not resolve static address assignments and I am not sure of its reliability. Is there a better way to handle internal AAAA records than ULAs with stateful DHCPv6?

Finally, as things start to work, we are now considering migrating our public services to IPv6. I understand that this would require a fixed graphical interface for the servers in order to provide public AAAA records. I don't know how to achieve this using SLAAC from the edge router, unless there is some kind of dynamic-DNS equivalent. Can I again use DHCPv6 or some other manual assignment method to select the IP addresses in our assigned prefix? I was hesitant to do this because I thought it might collide with an SLAAC address and I don't know what happens in the event of a collision. Alternatively, I have the option to ask the ISP for a 48, should i do this and advertise one / 64 for local clients to get connectivity and different / 64 for static servers? It seemed like an exaggeration to me, we will not be close to completing the single / 64 already but it could be my IPv4 state of mind which confuses me.