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

Follow-up of comments on #399 lime-librenet6 package #579

Closed
ilario opened this issue Sep 6, 2019 · 2 comments
Closed

Follow-up of comments on #399 lime-librenet6 package #579

ilario opened this issue Sep 6, 2019 · 2 comments

Comments

@ilario
Copy link
Member

ilario commented Sep 6, 2019

Some requests were rised by @G10h4ck on #399 but in #400 the code was merged as it was.
I copy and paste here the comments:

packages/lime-librenet6/files/etc/tinc/librenet6/tinc-up

#!/bin/sh
ifconfig $INTERFACE up txqueuelen 1000

@G10h4ck
ifconfig is deprecated! Isn't ip installed by default on openwrt at least some minimal version from busybox ?

packages/lime-librenet6/files/etc/uci-defaults/tinc-setup

uci commit network

# set IPv6 subnet of librenet6.librenet.org
uci set lime.network.main_ipv6_address '2002:8aff:5905:%N1%N2::/64'

@G10h4ck
This seems to interfere with normal lime behavior or am I missing something?

@aparcar
Well you have to use an IP of that subnet if you want a working connection. To keep it simple for users I decided to add this

@G10h4ck
I think that we should not alter the IP on the package level... to use an IP that will get upstream connection from one librenet6 provider or another is a matter that should be addressed at network profile level + babel source specific routes

packages/lime-librenet6/files/etc/uci-defaults/tinc-setup

uci commit lime

# apply all changes
lime-config

@G10h4ck
This two line seems could interfere with normal lime behavior too

@ilario
Copy link
Member Author

ilario commented Oct 4, 2019

Another issue to be fixed in lime-librenet6 is #424

@ilario
Copy link
Member Author

ilario commented Mar 2, 2023

Is librenet6 still functional?
Anyway lime-librenet6 is not present anymore in this repository, closing.

@ilario ilario closed this as completed Mar 2, 2023
LibreMesh 2020.2 release automation moved this from Needs triage to Closed Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
LibreMesh 20.xx release
  
Needs triage
Development

No branches or pull requests

1 participant