Crunchbits shiny new router switch

terrorgenterrorgen OG
edited August 2023 in Help

Do anyone have luck switching to @crunchbits' new router, 2606:a8c0:3::1?

I tried switching but no luck. Can't ping the new gateway. My VPS is in the 2606:a8c0:3::/48 range so I tried tweaking the prefix length to no avail.

If you got it working can you post your ip -6 a and ip -6 r?

The all seeing eye sees everything...

Comments

  • dgc1980dgc1980

    how are you configuring your network? ifupdown? or netplan?

  • terrorgenterrorgen OG

    @dgc1980 said:
    how are you configuring your network? ifupdown? or netplan?

    systemd-networkd.

    Regardless, the two commands above should show the configured state.

    The all seeing eye sees everything...

  • dgc1980dgc1980

    your have 2 different IPv6 ranges, first one is a /128 that is your default route, then you have a second one thatis a /64 routed via your /128

    so you need to have your /128 assigned for IPv6 to work

    Thanked by (1)FrankZ
  • terrorgenterrorgen OG
    edited August 2023

    The /128 (2606:a8c0:3::xx) is on link.

    The all seeing eye sees everything...

  • dgc1980dgc1980
    edited August 2023

    just to show the ip responses,

    1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 state UNKNOWN qlen 1000
    inet6 ::1/128 scope host
       valid_lft forever preferred_lft forever
2: enp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 state UP qlen 1000
    inet6 2606:a8c0:3:29::xxxx/64 scope global
       valid_lft forever preferred_lft forever
    inet6 2606:a8c0:xxxx:29::a/64 scope global
       valid_lft forever preferred_lft forever
    inet6 2606:a8c0:3::xx/128 scope global
       valid_lft forever preferred_lft forever

    ::1 dev lo proto kernel metric 256 pref medium
2606:a8c0:3::xxxx dev enp3s0 proto kernel metric 256 pref medium
2606:a8c0:3:xxxx::/64 dev enp3s0 proto kernel metric 256 pref medium
default via 2606:a8c0:3::1 dev enp3s0 proto static metric 1024 onlink pref medium

    traceroute to google.com (2607:f8b0:400e:c03::64), 30 hops max, 80 byte packets
 1  * _gateway (2606:a8c0:3::1)  12.039 ms *
 2  ae0.edge1.lblkwa.crunchbits.net (2606:a8c0:0:2::10:18)  0.228 ms  0.262 ms  0.265 ms
  • terrorgenterrorgen OG
    edited August 2023

    Interesting. You seem to have two /64s and one /128, none of which is in the same /64 as the router. Which is why your default route has a "onlink" notation so that your machine knows where to find the router.

    I tried the "onlink" trick and did a tcpdump and all I can see is that my machine is trying to find the router by sending neighbor solicitation messages but never received any responses.

    Would you mind PM me your actual IP addresses so I can traceroute to them?

    EDIT: he did and I can't ping him. Will try again in the morning.

    The all seeing eye sees everything...

  • GeekWandererGeekWanderer
    edited August 2023

    @terrorgen
    EDIT: he did and I can't ping him. Will try again in the morning.

    Get things working? I have a Debian and OpenBSD working, would be glad to help.

    Thanked by (2)FrankZ terrorgen
  • terrorgenterrorgen OG

    Actually, looks like I am situated in an older hypervisor that only has access to the old gateway. I was scheduled to get a ticket today asking for permission to move to the new hypervisor, but I caught them earlier.

    Migrated the VM and problem solved!

    Admin please close?

    Thanked by (3)GeekWanderer FrankZ Not_Oles

    The all seeing eye sees everything...

  • FrankZFrankZ Moderator

    /thread

    For staff assistance or support issues please use the helpdesk ticket system at https://support.lowendspirit.com/index.php?a=add

This discussion has been closed.

© LowEndSpirit 2024

ipv6 ready