Open UrusovVladimir opened 3 months ago
No. I have, until further notice, abandoned the 4.2 effort. Low resources and all that. 4.1.12 (soon to become 4.1.13) is the one intended for production.
Are you really using MAP-T? Part of the reason why it's fallen down the priority hole is because I haven't seen many people using it, and no one has given feedback.
Yes, i very need mapt module. I uses it evreday in my test, for testing router's OS
Hmmm. All right, let me release 4.1.13. Then I'll try to merge it into 4.2.0-rc3.
I can test module every release and give feedback for you
Thank yo so much!
I also use dslite(old project aftr). Is has been aboundoned and no longer being update =(
Hello. Tell me please, you'll can add mapt to release or add new kernels support to 4.2? Thanks
Hi When we can expect 4.2.0-rc3. I am also using MAPT for daily testing. Thanks.
I can only reliably work on Jool during weekends. Also, rc2 is very old, so this is probably going to be a difficult merge.
So, next Sunday at the earliest.
Thanks!🙏
Thanks ..!
Try this branch: https://github.com/NICMx/Jool/tree/mapt
Ok, thanks !
It is working fine. Thank you so much !
Hi, all. Sorry, I need a little more time for wil test it. But i have one problem with building. Could help me solve issue? When i was building I saw errors
configure: error: Package requirements (xtables) were not met:
Package 'xtables', required by 'virtual:world', not found
Consider adjusting the PKG_CONFIG_PATH environment variable if you
installed software in a non-standard prefix.
Alternatively, you may set the environment variables XTABLES_CFLAGS
and XTABLES_LIBS to avoid the need to call pkg-config.
See the pkg-config man page for more details.
I solved it I instaled packet libxtables-dev Thanks
I instaled packet libxtables-dev
Alternatively, if you don't need --iptables
, configure with
./configure --with-xtables=no
Thank you so much!
Hello. I have a problem with compilation jool with mapt package, on OS debian with kernel 6.10 I saw that this issue was resolved in the 4.1.12 release. Can you please tell me if this will be fixed for 4.2 in the future?