Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jool fails on Ubuntu 20.04 Focal Fossa #326

Closed
elburb opened this issue Apr 25, 2020 · 8 comments
Closed

Jool fails on Ubuntu 20.04 Focal Fossa #326

elburb opened this issue Apr 25, 2020 · 8 comments
Milestone

Comments

@elburb
Copy link

elburb commented Apr 25, 2020

jool fails with 'Error: Error receiving the kernel module's response: Invalid input data or parameter' when trying to run on the latest Ubuntu 20.04

Steps to reproduce:

Fresh install of Ubuntu 20.04:

# uname -a
Linux uk-lon4 5.4.0-26-generic #30-Ubuntu SMP Mon Apr 20 16:58:30 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Install jool 4.0.8.0 from source or from provided .debs.
The build appears to complete without error.

# dmesg -t | tail -1
NAT64 Jool v4.0.8.0 module inserted.
# jool --version
4.0.8.0

Attempt to add a NAT64 instance:

# jool instance add "example" --iptables --pool6 64:ff9b::/96
Error: Error receiving the kernel module's response: Invalid input data or parameter
@ydahhrk
Copy link
Member

ydahhrk commented Apr 25, 2020

Can confirm easily.

Do notice that Jool 4.0.7 made it into Ubuntu 20. As a workaround, try

sudo modprobe -r jool
cd jool-4.0.8
sudo make uninstall
sudo dkms remove jool/4.0.8 --all

sudo apt install jool-dkms jool-tools

That allows me to create the instance.

Of the two bugs 4.0.7 has, only one should affect you, and is easy to prevent. (Delete all instances manually before r-modprobing.)

@elburb
Copy link
Author

elburb commented Apr 25, 2020

Thanks, and yes, 4.0.7 does work ok.

@ydahhrk ydahhrk closed this as completed in fad9dc9 May 5, 2020
@ydahhrk ydahhrk added this to the 4.0.9 milestone May 5, 2020
@jaki300
Copy link

jaki300 commented Jun 8, 2020

HI @ydahhrk this is not working for me as i am using ubuntu. 20.04
still signature verification error
master:
root@jool-plat-master:/home/gci_gestion# dmesg | grep jool
[ 4.690495] systemd[1]: Set hostname to .
[ 34.703622] jool_common: loading out-of-tree module taints kernel.
[ 34.703735] jool_common: module verification failed: signature and/or required key missing - tainting kernel
root@jool-plat-master:/home/gci_gestion#

Slave:
[227984.036003] joold[95298]: segfault at 7fcc6f946f70 ip 00007fcc709c3a01 sp 00007fcc6f946ec0 error 6 in libc-2.31.so[7fcc7096f000+178000]
[227986.040096] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
[228046.254467] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
[228106.497292] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
[228166.701877] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
[228358.623065] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
[228419.802604] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
[228480.007827] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
[230449.509516] netlink: 4 bytes leftover after parsing attributes in process `jool'.

@ydahhrk
Copy link
Member

ydahhrk commented Jun 8, 2020

@jaki300: I think this is a separate issue. And the kernel taint probably doesn't have anything to do with it; it's effectively just a warning.

It seems your joold daemon crashed. May I have your joold configuration?
(But please open a separate issue)

@ydahhrk
Copy link
Member

ydahhrk commented Jun 8, 2020

Also, joold's logs would help too.

@jaki300
Copy link

jaki300 commented Jun 8, 2020

{
"multicast address": "ff08::db8:64:64",
"multicast port": "6464",
"in interface": "ens192",
"out interface": "ens192",
"reuseaddr": 1,
"ttl": 3
}

@jaki300
Copy link

jaki300 commented Jun 8, 2020

jool-tools_4.0.9-1_amd64.deb netsocket.json
root@jool-plat-slave:/home/gci_gestion# vi modsocket.json
{
"instance": "default"
}

@jaki300
Copy link

jaki300 commented Jun 8, 2020

6f946f70 ip 00007fcc709c3a01 sp 00007fcc6f946ec0 error 6 in libc-2.31.so[7fcc7096f000+178000]
Jun 8 16:40:58 jool-plat-slave kernel: [227986.040096] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
Jun 8 16:41:58 jool-plat-slave kernel: [228046.254467] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
Jun 8 16:42:58 jool-plat-slave kernel: [228106.497292] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
Jun 8 16:43:58 jool-plat-slave kernel: [228166.701877] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
Jun 8 16:47:10 jool-plat-slave kernel: [228358.623065] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
Jun 8 16:48:11 jool-plat-slave kernel: [228419.802604] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
Jun 8 16:49:12 jool-plat-slave kernel: [228480.007827] Jool WARNING (send_to_userspace): Looks like nobody received my multicast message. Is the joold daemon really active? (errcode -3)
Jun 8 17:22:43 jool-plat-slave joold: Opening file netsocket.json...
Jun 8 17:22:43 jool-plat-slave joold: Getting address info of ff08::db8:64:64#6464...
Jun 8 17:22:43 jool-plat-slave joold: Trying an address candidate...
Jun 8 17:22:43 jool-plat-slave joold: Setting SO_REUSEADDR as 1...
Jun 8 17:22:43 jool-plat-slave joold: The socket to the network was created.
Jun 8 17:22:43 jool-plat-slave joold: Configuring multicast options on the socket...
Jun 8 17:22:43 jool-plat-slave joold: We're now registered to the multicast group.
Jun 8 17:22:43 jool-plat-slave joold: Multicast loopback disabled.
Jun 8 17:22:43 jool-plat-slave joold: Tweaked the TTL of multicasts.
Jun 8 17:22:43 jool-plat-slave joold: The outgoing interface was overridden.
Jun 8 17:22:43 jool-plat-slave joold: Listening...
Jun 8 17:53:18 jool-plat-slave joold: Opening file netsocket.json...
Jun 8 17:53:18 jool-plat-slave joold: Getting address info of ff08::db8:64:64#6464...
Jun 8 17:53:18 jool-plat-slave joold: Trying an address candidate...
Jun 8 17:53:18 jool-plat-slave joold: Setting SO_REUSEADDR as 1...
Jun 8 17:53:18 jool-plat-slave joold: The socket to the network was created.
Jun 8 17:53:18 jool-plat-slave joold: Configuring multicast options on the socket...
Jun 8 17:53:18 jool-plat-slave joold: We're now registered to the multicast group.
Jun 8 17:53:18 jool-plat-slave joold: Multicast loopback disabled.
Jun 8 17:53:18 jool-plat-slave joold: Tweaked the TTL of multicasts.
Jun 8 17:53:18 jool-plat-slave joold: The outgoing interface was overridden.
Jun 8 17:53:18 jool-plat-slave joold: Listening...

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants