Help setting up ip-rotation | Lavalink | Page 1

woeful mason May 7, 2024, 1:38 PM

#

up have same problem but in other provider

pastel hornet May 7, 2024, 2:42 PM

#

woeful mason up have same problem but in other provider

Try these how-to first
If your server already had ipv6 I recommend the bottom one
https://blog.arbjerg.dev/2020/3/tunnelbroker-with-lavalink
https://github.com/Tomato6966/Debian-Cheat-Sheet-Setup/wiki/6-lavalink-tutorial#how-to-do-ip-routing-notes

Freya's notes

Using Tunnelbroker to make Lavalink balance its requests over many ...

When scraping metadata with Lavalink, it may be useful to have a large block of IPv6 addresses available. Allocating a large prefix of addresses to a machine can be difficult, as this is dependent on the configuration of the IP addresses, which is generally out of your control if you are renting a server.

GitHub

6 lavalink tutorial

How to setup your linux server and install nodejs, python, ffmpeg and java. Working good for Discord Bot hosting and other hostings! - Tomato6966/Debian-Cheat-Sheet-Setup

woeful mason May 7, 2024, 3:18 PM

#

pastel hornet Try these how-to first If your server already had ipv6 I recommend the bottom on...

thank you Luvi,

i think the people who make post this run xD.
my problem on lavalink when i was setup the tunnel broker, following few docs the given.
but lavalink return like :

📎 message.txt

#

2024-05-07T17:16:10.009+02:00  WARN 3822219 --- [  XNIO-1 task-2] c.s.d.l.p.DefaultAudioPlayerManager      : Suspicious exception for loading item ytsearch:music

com.sedmelluq.discord.lavaplayer.tools.FriendlyException: This video cannot be loaded.

#

i dont have any idea now

pastel hornet May 7, 2024, 3:21 PM

#

"Connect timed out"

Did you check that your ipv6 is working?

from https://blog.arbjerg.dev/2020/3/tunnelbroker-with-lavalink - Test your configuration

# Test that IPv6 works in the first place
ping6 google.com

# If you have the IPv6 block 1234:1234:1234::/48
# You should be able to use any of the IPs within that block
ping6 -I 1234:1234:1234:: google.com
ping6 -I 1234:1234:1234::1 google.com
ping6 -I 1234:1234:1234:dead::beef google.com

# Make sure your /48 block appears when running this command
ip -6 route

woeful mason May 7, 2024, 3:46 PM

#

like this right ?

📎 message.txt

#

pastel hornet May 7, 2024, 4:03 PM

#

woeful mason

If your IPV6 is working

ip -6 route replace local YOUR_48_BLOCK dev lo
and check your lavalink config then it sould be working

woeful mason May 7, 2024, 4:05 PM

#

pastel hornet If your IPV6 is working `ip -6 route replace local YOUR_48_BLOCK dev lo` and ch...

i was do this before

#

and im stuck in here like a week

#

just more info,

all work sportfy, soundcloud, radio but not with youtube

woeful mason May 7, 2024, 4:25 PM

#

woeful mason thank you Luvi, i think the people who make post this run xD. my problem on la...

the lavalink logs before if using RotateOnBan.

this if using LoadBalance

📎 message.txt

woeful mason May 7, 2024, 4:40 PM

#

ah i found the issue

#

now worked.
so for people who has config correctly, testing ping allworked. but still error like me at above.
u need check `ip -6 route`

ip -6 route

root@catfein:/var/lib/pterodactyl/volumes/c72e2b97-05d4-4fac-8130-272616ea648d# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
blackhole 100::1 dev lo proto bird metric 32 pref medium
2001:470:7069::/48 dev he-ipv6 proto bird metric 32 pref medium
2001:470:7069::/48 dev he-ipv6 proto kernel metric 256 pref medium
2a03:4000:6a:10::/64 dev eth0 proto kernel metric 256 pref medium
2a03:4000:6a:10::/64 dev lo metric 1024 pref medium
unreachable 2a05:dfc1:9158::/48 dev lo proto bird metric 32 pref medium
fdba:17c8:6c94::/64 dev pterodactyl0 proto bird metric 32 pref medium
fdba:17c8:6c94::/64 dev pterodactyl0 proto kernel metric 256 pref medium
fdba:17c8:6c94::/64 dev pterodactyl0 metric 1024 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev pterodactyl0 proto kernel metric 256 pref medium
...
default proto static metric 1024 pref medium
        nexthop via 2001:470:7069::1 dev he-ipv6 weight 1 
        nexthop via fe80::1 dev eth0 weight 1

Remove ~~nexthop via fe80::1 dev eth0 weight 1~~

just make sure the default route only one and thats is your ipv6 like :

default proto static metric 1024 pref medium
        nexthop via 2001:470:7069::1 dev he-ipv6 weight 1

midnight moth May 7, 2024, 4:55 PM

#

commands I used in exact order

sysctl -w net.ipv6.ip_nonlocal_bind=1
echo 'net.ipv6.ip_nonlocal_bind=1' >> /etc/sysctl.conf
sysctl -w net.ipv6.conf.all.autoconf=0
sysctl -w net.ipv6.conf.all.accept_ra=0
echo 'net.ipv6.conf.all.autoconf=0' >> /etc/sysctl.conf
echo 'net.ipv6.conf.all.accept_ra=0' >> /etc/sysctl.conf
cd /etc/netplan/
sudo nano ipv6_tunnel.yaml

#

->

network:
  version: 2
  tunnels:
    he-ipv6:
      mode: sit
      remote: 216.66.80.98
      local: 81.17.100.27
      addresses:
        - "2001:470:25:6a::2/64"
      routes:
        - to: default
          via: "2001:470:25:6a::1"

save -> exit

sudo netplan apply

#

now I am getting this error:

woeful mason May 7, 2024, 5:01 PM

#

midnight moth now I am getting this error:

can u do : ip -6 route

midnight moth May 7, 2024, 5:01 PM

#

root@vmd139683:/etc/netplan# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:470:25:6a::/64 dev he-ipv6 proto kernel metric 256 pref medium
2a02:c206:3013:9683::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default proto static metric 1024 pref medium
        nexthop via 2001:470:25:6a::1 dev he-ipv6 weight 1
        nexthop via fe80::1 dev eth0 weight 1 onlink

woeful mason May 7, 2024, 5:09 PM

#

midnight moth ```bash root@vmd139683:/etc/netplan# ip -6 route ::1 dev lo proto kernel metric ...

have u try ?

change 1234:1234 etc with u ipv6

# Test that IPv6 works in the first place
ping6 google.com

# If you have the IPv6 block 1234:1234:1234::/48
# You should be able to use any of the IPs within that block
ping6 -I 1234:1234:1234:: google.com
ping6 -I 1234:1234:1234::1 google.com
ping6 -I 1234:1234:1234:dead::beef google.com

# Make sure your /48 block appears when running this command
ip -6 route

woeful mason May 7, 2024, 5:09 PM

#

midnight moth ```bash root@vmd139683:/etc/netplan# ip -6 route ::1 dev lo proto kernel metric ...

for this u need remove nexthop via fe80::1 dev eth0 weight 1 onlink

#

refer my case #1237382246420189375 message if can ping but the ip rotation not worked at lavalink

midnight moth May 7, 2024, 5:27 PM

#

I modified my .yaml in etc/netplan

and now I ge this:

root@vmd139683:/# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:470:25:6a::/64 dev he-ipv6 proto kernel metric 256 pref medium
2a02:c206:3013:9683::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via 2001:470:25:6a::1 dev he-ipv6 proto static metric 1024 pref medium

woeful mason May 7, 2024, 5:30 PM

#

um wait u wanna using /64 right ? or /48 ?

midnight moth May 7, 2024, 5:31 PM

#

idk what is better

woeful mason May 7, 2024, 5:32 PM

#

/48 better than /64

midnight moth May 7, 2024, 5:32 PM

#

how do I change that than

woeful mason May 7, 2024, 5:33 PM

#

on u file .yaml at etc/netplan

midnight moth May 7, 2024, 5:33 PM

#

network:
  version: 2
  tunnels:
    he-ipv6:
      mode: sit
      remote: 216.66.80.98
      local: 81.17.100.27
      addresses:
        - "2001:470:25:6a::2/64"
      routes:
        - to: default
          via: "2001:470:25:6a::1"
  ethernets:
    eth0:
      dhcp4: true
      dhcp6: false

#

yes but change what

#

addresses?

#

"2001:470:25:6a::2/64"

to

"2001:470:b422::/48"
?

#

woeful mason May 7, 2024, 5:35 PM

#

        - "2001:470:b422::2/48"
      routes:
        - to: default
          via: "2001:470:b422::1"```

midnight moth May 7, 2024, 5:37 PM

#

root@vmd139683:/# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:470:b422::/48 dev he-ipv6 proto kernel metric 256 pref medium
2a02:c206:3013:9683::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via 2001:470:b422::1 dev he-ipv6 proto static metric 1024 pref medium

woeful mason May 7, 2024, 5:37 PM

#

yep

#

try ping

midnight moth May 7, 2024, 5:37 PM

#

ping6 google.com works

how do I check the other ones

woeful mason May 7, 2024, 5:38 PM

#

ping6 -I 2001:470:b422:: google.com
ping6 -I 2001:470:b422::1 google.com
ping6 -I 2001:470:b422:dead::beef google.com

midnight moth May 7, 2024, 5:38 PM

#

ping6 -I 2001:470:b422:: google.com
ping6 -I 2001:470:b422::1 google.com
ping6 -I 2001:470:b422:dead::beef google.com

#

ah ok

#

woeful mason May 7, 2024, 5:39 PM

#

another

midnight moth May 7, 2024, 5:39 PM

#

woeful mason May 7, 2024, 5:40 PM

#

again

midnight moth May 7, 2024, 5:40 PM

#

again?

#

same command

#

or different

woeful mason May 7, 2024, 5:40 PM

#

ping6 -I 2001:470:b422:dead::beef google.com

midnight moth May 7, 2024, 5:41 PM

#

same

woeful mason May 7, 2024, 5:41 PM

#

MiniheraBall1 rip

midnight moth May 7, 2024, 5:42 PM

#

xd any suggestions on how to fix haha

cloud void May 7, 2024, 7:26 PM

#

midnight moth now I am getting this error:

this looks like a permissions issue, did you ever fix the permissions on your config files?

midnight moth May 7, 2024, 7:26 PM

#

yes

#

sudo chmod 600 /etc/netplan/50-cloud-init.yaml /etc/netplan/ipv6_tunnel.yaml

cloud void May 7, 2024, 7:33 PM

#

well idk how to help with the conflicting routes issue unfortunately. i found a stackoverflow article which seems to show someone with a similar problem + a vague solution, but I'm not knowledgable enough in networking to help you apply it to your situation

#

https://askubuntu.com/questions/1386063/ubuntu-server-netplan-conflicting-default-route-declarations-for-ipv4-4-diff also note they're using ip4 in this example

Ask Ubuntu

Ubuntu Server Netplan - conflicting default route declarations for ...

I have a server with 2 network cards of 4 ports, but only one of them is used. Each port is connected to a L2 switch and configured for a different VLAN with 1 usable IP from a different /24 subnet -

midnight moth May 7, 2024, 7:51 PM

#

cloud void well idk how to help with the conflicting routes issue unfortunately. i found a ...

i solved the issue with conflicting routes

#

its just the package loss

#

when using the tunnel

cloud void May 7, 2024, 7:52 PM

#

ahh i see

#

are you hosting on your own machine or with cloud stuff?

midnight moth May 7, 2024, 7:52 PM

#

i tried this

#

didnt solve the issue

midnight moth May 7, 2024, 7:53 PM

#

cloud void are you hosting on your own machine or with cloud stuff?

i got the server from contabo

cloud void May 7, 2024, 7:56 PM

#

it's possible that their hardware doesn't support protocol 41 (ip6in4). I was having an issue similar to yours, where I could ping myself at ::1 but when trying to ping tunnelbroker endpoint of the tunnel (::2) I was also getting 100% packet loss. it turns out that my router's firmware doesn't allow protocol 41 traffic, which is a necessity if u want to use tunnelbroker

#

maybe its the same issue for you, maybe not. i did a quick google search and couldn't find a certain answer about whether contabo supports this protocol or not. as a paying customer though, I'm sure their customer support would get you an answer if you asked them about it

midnight moth May 7, 2024, 7:58 PM

#

ye idk if they are happy with me using the server to scrape data using lavalink

cloud void May 7, 2024, 7:58 PM

#

lol perhaps not

midnight moth May 7, 2024, 7:58 PM

#

xd

#

so what should I google

cloud void May 7, 2024, 7:59 PM

#

i would ask contabo customer support if they support protocol 41

midnight moth May 7, 2024, 8:01 PM

#

ok

i found a guy using contabo who did it, i think: #1211003213248069632 message

idk what to follow tho

#

#1211003213248069632 message

#

like I this works:

ping6 google.com

but not these ones

ping6 -I 2001:470:b422:: google.com
ping6 -I 2001:470:b422::1 google.com
ping6 -I 2001:470:b422:dead::beef google.com

cloud void May 7, 2024, 8:07 PM

#

well that's good that you have a working example to follow, I'm not sure how else to help personally. good luck vexi

midnight moth May 7, 2024, 8:09 PM

#

ty

midnight moth May 7, 2024, 8:25 PM

#

idk i tried following what @timid flicker told the guy here #1211003213248069632 message

and I did the steps he did but I still have 100% packet loss.. what a bummer

woeful mason May 8, 2024, 3:02 AM

#

midnight moth like I this works: - ping6 google.com but not these ones ```bash ping6 -I 2001:...

if me i will do :

clear all network ipv6 default.
clear ipv6 tunnel broker too.

after all clear,
install again the ipv6 /48 from tunnel broker

woeful mason May 8, 2024, 12:37 PM

#

woeful mason now worked. so for people who has config correctly, testing ping allworked. but ...

net.ipv6.conf.eth0.disable_ipv6 = 1

midnight moth May 9, 2024, 4:00 PM

#

woeful mason if me i will do : 1. clear all network ipv6 default. 2. clear ipv6 tunnel broker...

I tried different stuff out.

This is what I found out:

#

if I use the netplan provided by tunnelbroker:

network:
  version: 2
  tunnels:
    he-ipv6:
      mode: sit
      remote: 216.66.80.98
      local: 81.17.100.27
      addresses:
        - "2001:470:25:6a::2/64"
      routes:
        - to: default
          via: "2001:470:25:6a::1"

this command works and I have no packet loss:
ping6 -I 2001:470:b422::1 google.com

#

however if I try to use this:

network:
  version: 2
  tunnels:
    he-ipv6:
      mode: sit
      remote: 216.66.80.98
      local: 81.17.100.27
      addresses:
        - "2001:470:b422::2/48"
      routes:
        - to: default
          via: "2001:470:25:6a::1"

then I get 100% packet loss

timid flicker May 9, 2024, 4:07 PM

#

Because ur routes via is incorrect

midnight moth May 9, 2024, 4:08 PM

#

what should it be

timid flicker May 9, 2024, 4:08 PM

#

Should be ur block lol/48

woeful mason May 9, 2024, 4:08 PM

#

kek2

midnight moth May 9, 2024, 4:09 PM

#

"via: "2001:470:b422::1"?

woeful mason May 9, 2024, 4:09 PM

#

yep

midnight moth May 9, 2024, 4:10 PM

#

still 100% packet loss

woeful mason May 9, 2024, 4:11 PM

#

try :

network:
  version: 2
  tunnels:
    he-ipv6:
      mode: sit
      remote: 216.66.80.98
      local: 81.17.100.27
      addresses:
        - "2001:470:b422::2/48"
      gateway6: "2001:470:b422::1"

netplan apply

and

ip -6 route

give the screenshhot / logs

midnight moth May 9, 2024, 4:12 PM

#

root@vmd139683:/etc/netplan# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:470:b422::/48 dev lo proto kernel metric 256 pref medium
2001:470:b422::/48 dev he-ipv6 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium

woeful mason May 9, 2024, 4:13 PM

#

ip -6 route replace local 2001:470:b422::/48 dev lo

#

done

#

actually i didnt see the default route on that ip -6 route. sus

but try ping using, test one by one

ping6 -I 2001:470:b422:: google.com ping6 -I 2001:470:b422::1 google.com ping6 -I 2001:470:b422:dead::beef google.com

midnight moth May 9, 2024, 4:19 PM

#

still same 100% packet loss

woeful mason May 9, 2024, 4:21 PM

#

midnight moth ``` root@vmd139683:/etc/netplan# ip -6 route ::1 dev lo proto kernel metric 256 ...

because log of u ip -6 route didnt have any default route for u ipv6

looks like :

::1 dev lo proto kernel metric 256 pref medium
blackhole 100::1 dev lo proto bird metric 32 pref medium
2001:470:7069::/48 dev he-ipv6 proto bird metric 32 pref medium               <- ur ipv6/48
2001:470:7069::/48 dev he-ipv6 proto kernel metric 256 pref medium            <- ur ipv6/48
2a03:4000:6a:10::/64 dev eth0 proto kernel metric 256 pref medium
2a03:4000:6a:10::/64 dev lo metric 1024 pref medium
unreachable 2a05:dfc1:9158::/48 dev lo proto bird metric 32 pref medium
fdba:17c8:6c94::/64 dev pterodactyl0 proto bird metric 32 pref medium
fdba:17c8:6c94::/64 dev pterodactyl0 proto kernel metric 256 pref medium
fdba:17c8:6c94::/64 dev pterodactyl0 metric 1024 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
fe80::/64 dev pterodactyl0 proto kernel metric 256 pref medium
default proto static metric 1024 pref medium
        nexthop via 2001:470:7069::1 dev he-ipv6 weight 1                    <- ur gateway / default route

^

midnight moth May 9, 2024, 4:22 PM

#

yes cause removed default route for ipv6 because i ran into this issue:

** (process:16116): WARNING **: 17:51:26.653: Problem encountered while validating default route consistency.Please set up multiple routing tables and use `routing-policy` instead.
Error: Conflicting default route declarations for IPv6 (table: main, metric: default), first declared in he-ipv6 but also in eth0

#

this is my modified 50-cloud-init.yaml: https://sourceb.in/x4faaJz4yV
this is my ipv6_tunnel.yaml: https://sourceb.in/xyDkPynNRc

woeful mason May 9, 2024, 4:25 PM

#

midnight moth this is my modified 50-cloud-init.yaml: https://sourceb.in/x4faaJz4yV this is my...

can i see the /etc/sysctl.conf ?

midnight moth May 9, 2024, 4:27 PM

#

https://sourceb.in/40OEAbqSo8

woeful mason May 9, 2024, 4:30 PM

#

midnight moth https://sourceb.in/40OEAbqSo8

try remove :

net.ipv6.conf.all.autoconf=0
net.ipv6.conf.all.accept_ra=0

and do sysctl -p

#

netplan apply

midnight moth May 9, 2024, 4:31 PM

#

** (process:16841): WARNING **: 18:31:17.912: gateway6 has been deprecated, use default routes instead.
See the 'Default routes' section of the documentation for more details.

woeful mason May 9, 2024, 4:32 PM

#

ignore

midnight moth May 9, 2024, 4:32 PM

#

root@vmd139683:/# sysctl -p
net.ipv6.ip_nonlocal_bind = 1

woeful mason May 9, 2024, 4:32 PM

#

now what log of

ip -6 route

after do netplan apply

midnight moth May 9, 2024, 4:32 PM

#

root@vmd139683:/# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:470:b422::/48 dev lo proto kernel metric 256 pref medium
2001:470:b422::/48 dev he-ipv6 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium

woeful mason May 9, 2024, 4:33 PM

#

wtf

midnight moth May 9, 2024, 4:33 PM

#

is there a way to reset the 50-cloud-init.yaml file to its original state

#

sorry this one

#

https://sourceb.in/1qgCEYVkhy

woeful mason May 9, 2024, 4:38 PM

#

um wait, try cahnge again back to

network:
  version: 2
  tunnels:
    he-ipv6:
      mode: sit
      remote: 216.66.80.98
      local: 81.17.100.27
      addresses:
        - "2001:470:b422::2/48"
      routes:
        - to: default
          via: "2001:470:b422::1"

the tunnel file

#

and netplan apply

midnight moth May 9, 2024, 4:38 PM

#

yes

#

ip -6 route again?

woeful mason May 9, 2024, 4:39 PM

#

yep

#

same ?

midnight moth May 9, 2024, 4:39 PM

#

root@vmd139683:/# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:470:b422::/48 dev lo proto kernel metric 256 pref medium
2001:470:b422::/48 dev he-ipv6 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium

woeful mason May 9, 2024, 4:39 PM

#

ping lost too ?

midnight moth May 9, 2024, 4:40 PM

#

ye 100% packet loss

#

it only works with this

network:
  version: 2
  tunnels:
    he-ipv6:
      mode: sit
      remote: 216.66.80.98
      local: 81.17.100.27
      addresses:
        - "2001:470:25:6a::2/64"
      routes:
        - to: default
          via: "2001:470:25:6a::1"

woeful mason May 9, 2024, 4:41 PM

#

midnight moth it only works with this ```yaml network: version: 2 tunnels: he-ipv6: ...

try this

#

and do
netplan apply

ip -6 route

midnight moth May 9, 2024, 4:42 PM

#

root@vmd139683:/# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:470:25:6a::/64 dev he-ipv6 proto kernel metric 256 pref medium
2001:470:b422::/48 dev lo proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via 2001:470:25:6a::1 dev he-ipv6 proto static metric 1024 pref medium
root@vmd139683:/# ping6 -I 2001:470:b422:: google.com
PING google.com(ams16s21-in-x0e.1e100.net (2a00:1450:400e:802::200e)) from 2001:470:b422:: : 56 data bytes
64 bytes from ams15s41-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=1 ttl=117 time=29.5 ms
64 bytes from ams15s41-in-x0e.1e100.net (2a00:1450:400e:802::200e): icmp_seq=2 ttl=117 time=29.1 ms

woeful mason May 9, 2024, 4:42 PM

#

that we got default via 2001:470:25:6a::1 dev he-ipv6 proto static metric 1024 pref medium

#

wait

midnight moth May 9, 2024, 4:43 PM

#

y

woeful mason May 9, 2024, 4:43 PM

#

can u delete : 2001:470:b422::/48 dev lo proto kernel metric 256 pref medium

midnight moth May 9, 2024, 4:43 PM

#

how

#

sudo ip route del 2001:470:b422::/48 dev lo proto kernel metric 256 pref medium

woeful mason May 9, 2024, 4:43 PM

#

try

sudo ip route del 2001:470:b422::/48 dev lo

midnight moth May 9, 2024, 4:44 PM

#

ok and then

woeful mason May 9, 2024, 4:44 PM

#

check again ip route

midnight moth May 9, 2024, 4:44 PM

#

root@vmd139683:/# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:470:25:6a::/64 dev he-ipv6 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via 2001:470:25:6a::1 dev he-ipv6 proto static metric 1024 pref medium

woeful mason May 9, 2024, 4:44 PM

#

cool

midnight moth May 9, 2024, 4:45 PM

#

so now what?
do I change my netplan again

#

to /48

woeful mason May 9, 2024, 4:45 PM

#

now try :
change again the config file to

network:
  version: 2
  tunnels:
    he-ipv6-New:
      mode: sit
      remote: 216.66.80.98
      local: 81.17.100.27
      addresses:
        - "2001:470:b422::2/48"
      gateway6: "2001:470:b422::1"

#

netplan apply

#

check ip route

midnight moth May 9, 2024, 4:46 PM

#

root@vmd139683:/# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:470:25:6a::/64 dev he-ipv6 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via 2001:470:25:6a::1 dev he-ipv6 proto static metric 1024 pref medium

woeful mason May 9, 2024, 4:46 PM

#

netplan apply ?

midnight moth May 9, 2024, 4:46 PM

#

i did

#

woeful mason May 9, 2024, 4:48 PM

#

what if :

network:
  version: 2
  tunnels:
    he-ipv6-New:
      mode: sit
      remote: 216.66.80.98
      local: 81.17.100.27
      addresses:
        - "2001:470:b422::2/48"
      routes:
        - to: default
          via: "2001:470:b422::1"

midnight moth May 9, 2024, 4:48 PM

#

root@vmd139683:/# ip -6 route
::1 dev lo proto kernel metric 256 pref medium
2001:470:25:6a::/64 dev he-ipv6 proto kernel metric 256 pref medium
fe80::/64 dev eth0 proto kernel metric 256 pref medium
default via 2001:470:25:6a::1 dev he-ipv6 proto static metric 1024 pref medium

#

now ping works

#

but what did change

woeful mason May 9, 2024, 4:49 PM

#

MiniheraBall1

#

all ping ?

midnight moth May 9, 2024, 4:49 PM

#

yes

#

so and what do I put in my lavalink yaml

woeful mason May 9, 2024, 4:50 PM

#

This right ?

ping6 -I 2001:470:b422::1 google.com
ping6 -I 2001:470:b422:dead::beef google.com```

midnight moth May 9, 2024, 4:50 PM

#

woeful mason This right ? ```ping6 -I 2001:470:b422:: google.com ping6 -I 2001:470:b422::1 go...

yes this works now

woeful mason May 9, 2024, 4:50 PM

#

midnight moth so and what do I put in my lavalink yaml

just :

        ratelimit:
            ipBlocks:
                - 2001:470:b422::/48
            retryLimit: 1
            searchTriggersFail: true
            strategy: LoadBalance

midnight moth May 9, 2024, 4:51 PM

#

ok tysm btw

#

i was literally on the edge of giving up because i kept getting 100% packet loss

#

even after following the instructions

#

1 to 1

woeful mason May 9, 2024, 4:51 PM

#

try it, i really wanna know are that working corerctly, because its little funny

#

StarWarsPepe

midnight moth May 9, 2024, 4:56 PM

#

so I tried playing music and it works

woeful mason May 9, 2024, 4:57 PM

#

can i see the logs of lavalink when playing music ?

#

just damn, idk why it work and why before not work

midnight moth May 9, 2024, 4:57 PM

#

📎 spring.log

woeful mason May 9, 2024, 4:58 PM

#

midnight moth

waitttt

#

i didnt see the ipblock config correctly

midnight moth May 9, 2024, 4:59 PM

#

#

or where do you mean

woeful mason May 9, 2024, 4:59 PM

#

wrong place

midnight moth May 9, 2024, 4:59 PM

#

oh i see

woeful mason May 9, 2024, 4:59 PM

#

server:
        bufferDurationMs: 400
        filters:
            channelMix: true
            distortion: true
            equalizer: true
            karaoke: true
            lowPass: true
            rotation: true
            timescale: true
            tremolo: true
            vibrato: true
            volume: true
        frameBufferDurationMs: 10000
        gc-warnings: true
        opusEncodingQuality: 10
        password: catfein
        playerUpdateInterval: 5
        ratelimit:
            ipBlocks:
                - 2001:470:7845::/48   <- Here
            retryLimit: 1
            searchTriggersFail: true
            strategy: LoadBalance
        resamplingQuality: HIGH
        soundcloudSearchEnabled: true
        sources:
            bandcamp: true
            http: true
            local: false
            soundcloud: true
            twitch: true
            vimeo: true
            youtube: false
        trackStuckThresholdMs: 10000
        useSeekGhosting: true

midnight moth May 9, 2024, 5:00 PM

#

yes i moved it there

woeful mason May 9, 2024, 5:01 PM

#

it worked ? need see the logs

midnight moth May 9, 2024, 5:01 PM

#

no i got error on startup now

woeful mason May 9, 2024, 5:02 PM

#

what is

midnight moth May 9, 2024, 5:02 PM

#

📎 spring.log

#

APPLICATION FAILED TO START

Description:

Failed to bind properties under 'lavalink.server.ratelimit' to lavalink.server.config.RateLimitConfig:

Reason: org.springframework.core.convert.ConverterNotFoundException: No converter found capable of converting from type [java.lang.String] to type [lavalink.server.config.RateLimitConfig]

Action:

Update your application's configuration

#

this is my applicationyml: https://sourceb.in/bHoZSBdukc

#

wait

#

i maybe found the error myself

woeful mason May 9, 2024, 5:04 PM

#

i see it

midnight moth May 9, 2024, 5:05 PM

#

📎 spring.log

woeful mason May 9, 2024, 5:06 PM

#

thats correct

#

try play music

midnight moth May 9, 2024, 5:07 PM

#

works

#

do you need logs as well?

woeful mason May 9, 2024, 5:07 PM

#

yeppss i love logs

#

BlizzyXD

midnight moth May 9, 2024, 5:08 PM

#

📎 spring.log

#

it works with yt search as well

#

not only spotify

#

woeful mason May 9, 2024, 5:10 PM

#

midnight moth

glad hear it.

cooll

#

halal

midnight moth May 9, 2024, 5:10 PM

#

thank you so much

woeful mason May 9, 2024, 5:10 PM

#

yups

midnight moth May 9, 2024, 5:10 PM

#

<3

#

PeepoDJ

timid flicker May 9, 2024, 5:11 PM

#

midnight moth not only spotify

It won’t be used with Spotify

midnight moth May 9, 2024, 5:18 PM

#

yes thats why i tested with ytsearch

#

after realising i input a spotify url to search

#

lmao

livid edge May 12, 2024, 9:27 AM

#

I have same problem

#

network:
��ethernets:
����eth1:
������addresses:
����� - 82.16.177.67/27
����� - 2a09:17c0::2/48

������match:
��������macaddress: B0:58:99:FF:R2:C7
������nameservers:
��������addresses:
������� - 1.1.1.1
������� - 8.8.8.8
������� - 4.4.4.4
������routes:
����� - to: default
��������via: 82.16.177.67
����� - to: default
��������via: 2a09:17c0::1
��version: 2```

#

My netplan configuration

#

::1 dev lo proto kernel metric 256 pref medium
2001:470:1829::2 dev he-ipv6 metric 1024 pref medium
2001:470:1829::/64 dev he-ipv6 proto kernel metric 256 pref medium
2a09:17c0::/48 dev eth1 proto kernel metric 256 pref medium
fe80::/64 dev he-ipv6 proto kernel metric 256 pref medium
fe80::/64 dev eth1 proto kernel metric 256 pref medium
default metric 1024 pref medium
        nexthop via 2001:470:1829::2 dev he-ipv6 weight 1 onlink 
        nexthop via 2a09:17c0::1 dev eth1 weight 1```

#

ip -6 route

#

@woeful mason Could you please help me ?

#Help setting up ip-rotation

now worked. so for people who has config correctly, testing ping allworked. but still error like me at above. u need check ip -6 route

now worked.
so for people who has config correctly, testing ping allworked. but still error like me at above.
u need check `ip -6 route`