-
-
Notifications
You must be signed in to change notification settings - Fork 23
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
Support for UDM SE #82
Comments
You are correct, the UDM SE and UDR are currently unsupported since they were released after this project was developed. Porting this project to those devices requires building the Once the UDM (Pro) is on 2.x, I will start porting this project to the new firmware. |
If you only want wireguard support this project works great on UDM-SE: https://github.com/tusc/wireguard-kmod |
Hi @fabianishere wondering if this is still on your radar? :) (We now have moved to Unifi OS 3.x) |
This is still on my ToDo list, but I don't have access to a UDM Pro at the moment. I'll probably start working on this start of next year. |
UDM/Pro is being updated to the same 3.x branch with UDM Pro SE 3.x, migration is already started for early access so this issue will probably apply to UDM/Pro soon once they go GA |
@fabianishere: I have got an udm se and am interested to help getting this project running. Could you point out what we have to achive to get it running? Some advise how to start? |
You'll have to retrieve the kernel sources from Ubiquiti and verify whether you can build kexec-mod for the kernel. Then it is a matter of updating the udm-bootctl command to not make use of |
Is there an specific adress at unifi to get the sources? Who did you
turn to to get the sources?
Am 21.01.2023 um 21:06 schrieb Fabian Mastenbroek:
…
@fabianishere <https://github.com/fabianishere>: I have got an udm
se and am interested to help getting this project running. Could
you point out what we have to achive to get it running? Some
advise how to start?
You'll have to retrieve the kernel sources from Ubiquiti and verify
whether you can build kexec-mod
<https://github.com/fabianishere/kexec-mod> for the kernel.
Then it is a matter of updating the udm-bootctl
<https://github.com/fabianishere/udm-kernel-tools/blob/master/udm-bootctl>
command to not make use of |ssh-proxy|, but invoke the commands on the
system directly.
—
Reply to this email directly, view it on GitHub
<#82 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AACYGU3HAXJI6U6Y7RVSLELWTQ6VPANCNFSM6AAAAAARCMKEGA>.
You are receiving this because you commented.Message ID:
***@***.***>
|
You can mail Ubiquiti at [email protected] to request the GPL sources for the UDM SE. |
I have got the kernel sources and will take a look wether i can build kexec-mod. |
ok i get the following error:
Did you build kexec-mod on the udm? I tried using the windows subsystem for linux. I will try using a plain linux later. |
You need to cross-compile to ARM64, by setting |
I cam here to share I got sources but I have been defeated! Well done! Its quite telling the UDMSE sources came quick but UDMPRO, nada! |
With cross compile i get a different error. Any hint for this?
|
Ok got it working by using the absolut path for KDIR not a relative one. Build finished. Make of the User-space helper was also successfull. What are the next steps? |
Build a custom kerneland make sure to add the configs for BPF needed for podman. Then you can follow the docs and boot into that kernel. |
Ok i am just building the kernel. How can i test it manually? Just by coping the kernel, kexex-module and redir.so to the udm and then run LD_PRELOAD=/root/redir.so kexec -l /path/to/custom/kernel --reuse-cmdline? |
@foxcris just wanted to reach out and see if you were able to successfully boot into this kernel on your SE and run containers? |
Today i had some time to go on with kexec an a custom kernel. Currently i still didn't manage to boot a custom kernel. My problem is that i cannot load the kexec_mod module. First isse was the wrong version magic
I figured out how to fix this by setting the EXTRAVERSION. However it took me a while to "remove" the "+" sign. Wasn't really obvious and caused by git (you have to set LOCALVERSION manually during build).
@fabianishere: Any hints how to go on now? As soon as i can manually boot the custom kernel i will try to build/adapt your packages. |
Oh i just missed to load "kexec_mod_arm64.ko" first. |
Kexec is still compaining about miss /proc/kcore.
|
Ok found the error. I used the wrong path to redir.so. Now the kernel is loaded. Will try to boot it with kexec -e. |
After running
they system is hanning. The display on the router tells something about plugging in the wan cable (but its still plugged in). I needed to reboot it manually by switching it off and on again.
the system directly restarts and uses its own kernel again. |
Curious if you've made any progress on this? Or if there's a different kernel that will work on the SE so that I can finally get multicast routing working? |
Multicast routing should already be supported in the stock UDM SE kernels. |
Doesn't seem to be working for me and all I saw was a bunch of posts pointing to here about Multicast routing...is there something I need to enable that I'm missing? Multicast DNS seems to work, but not routing |
@jimmy-ungerman You can verify it on your device as follows: $ zgrep "MROUTE" /proc/config.gz
CONFIG_IP_MROUTE_COMMON=y
CONFIG_IP_MROUTE=y
# CONFIG_IP_MROUTE_MULTIPLE_TABLES is not set
# CONFIG_IPV6_MROUTE is not set Make sure you actually have the multicast routes installed into the kernel. |
@fabianishere I'm sorry I realized I've been saying "Multicast" when I meant "MultiPATH". Are you aware if this is enabled or not? |
@jimmy-ungerman No, multipath routing is not supported by the stock kernel. You’ll need to use a custom kernel for that (if you search in the repository, you’ll find others also using it for that feature). |
Yeah that's what I thought. That's why I'm following this issue so closely, hoping to be able to get my UDM-Pro SE updated as soon as there is support |
Any progress on this? I am really in need of Multipath support also. Looks like some progress was made, any chance we have something for the SE anytime soon? |
Just wanted to add that I'm currently hitting this wall as well, on 3.0.13 (I've requested but still haven't received the GPL sources associated with 3.0.18). Working off of the v2.x branch, among other things, I had to update the If there's a particular log I can check to get a better read on what's happening, please let me know. I'm also trying to simply enable multi-path routing, and it's increasingly looking like just overwriting the kernel in the boot image is the more feasible path than trying to get kexec hacks to work. (And as a side note, if anyone has resources handy for quickly modifying the U-Boot image specifically for UDM SE, that'd be appreciated.) |
@EddieRingle Check the files in |
Are we safe to assume that work has stopped on this? |
has anyone been able to make this work on the udm se? |
Hi,
I wanted to install a custom kernel for the UDMSE (version
2.5.11
), however, it seems to fail:I assume this is due to the new 'major' UniFi-OS version, as the UDM and UDMP are at
1.12.30
, while the UDMSE and UDR are at2.5.11
. However, I was unable to find any documentation on this - is there any?Thank you!
The text was updated successfully, but these errors were encountered: