5cd0a85405
Router advertisement servers advertise prefixes together with a default router in layer 2 networks. There may be multiple router advertisement servers in one layer 2 network. Each of those router advertisement servers can advertise different prefixes and a different default router. A client can accept multiple of the advertised prefixes at the same time. If it does that, it installs an address in each of the advertised prefixes. It also has to install default routes from the router advertisements. Since default routers are sometimes not able to forward ip packets from arbitrary source addresses, the client should install routes to all default routers and use the correct one depending on which of the installed addresses it is sending from. This can be addressed using source based routing. The odhcpv6 script already attempts to implement this. The setting is named "sourcefilter". In this commit, we enable it. Note, that the following examples show output of ip-full. I am not sure, whether the "from" part is acutally shown by ip-tiny. Before this commit: root@platzhalter-525400123457:/# ip -6 route show default default via fe80::8ae6:40ff:feba:a099 dev br-client proto static metric 512 pref medium After this commit: root@platzhalter-525400123457:/# ip -6 route show default default from 2001:678:978:199::/64 via fe80::8ae6:40ff:feba:1099 dev br-client proto static metric 512 pref medium default from 2a02:790:ff:799::/64 via fe80::8ae6:40ff:feba:1099 dev br-client proto static metric 512 pref medium default from 2a02:790:ff:899::/64 via fe80::8ae6:40ff:feba:1099 dev br-client proto static metric 512 pref medium default from 2a02:790:ff:999::/64 via fe80::8ae6:40ff:feba:1099 dev br-client proto static metric 512 pref medium default from 2a02:790:ff:1099::/64 via fe80::8ae6:40ff:feba:1099 dev br-client proto static metric 512 pref medium default from fdca:ffee:8:99::/64 via fe80::8ae6:40ff:feba:1099 dev br-client proto static metric 512 pref medium Fixes #2180 Tested-By: Leonardo Mörlein <git@irrelefant.net> |
||
|---|---|---|
| .github | ||
| contrib | ||
| docs | ||
| package | ||
| patches | ||
| scripts | ||
| targets | ||
| tests | ||
| .editorconfig | ||
| .gitignore | ||
| .luacheckrc | ||
| CONTRIBUTING.md | ||
| LICENSE | ||
| Makefile | ||
| modules | ||
| README.md | ||
Documentation (incomplete at this time, contribute if you can!) may be found at https://gluon.readthedocs.io/.
If you're new to Gluon and ready to get your feet wet, have a look at the Getting Started Guide.
Gluon's developers frequent an IRC chatroom at #gluon on hackint. There is also a webchat that allows for access from within your browser.
Issues & Feature requests
Before opening an issue, make sure to check whether any existing issues (open or closed) match. If you're suggesting a new feature, drop by on IRC or our mailinglist to discuss it first.
We maintain a Roadmap for the future development of Gluon.
Use a release!
Please refrain from using the master branch for anything else but development purposes!
Use the most recent release instead. You can list all releases by running git tag
and switch to one by running git checkout v2020.2.2 && make update.
If you're using the autoupdater, do not autoupdate nodes with anything but releases. If you upgrade using random master commits the nodes will break eventually.
Mailinglist
To subscribe to the list, send a message to:
gluon+subscribe@luebeck.freifunk.net
To remove your address from the list, just send a message to
the address in the List-Unsubscribe header of any list
message. If you haven't changed addresses since subscribing,
you can also send a message to:
gluon+unsubscribe@luebeck.freifunk.net