This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | Next revisionBoth sides next revision |
| docs:guide-user:network:wifi:linux-meteredconnection [2021/05/30 22:26] – filimonic | docs:guide-user:network:wifi:linux-meteredconnection [2021/06/01 19:51] – filimonic |
|---|
| [[https://networkmanager.dev/|NetworkManager]] (**NM**) has [[https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/5307b1ed733fd0b91a1ef8bd5c58d8c68312ee2c|implemented]] same detection method as [[docs:guide-user:network:wifi:ms-meteredconnection|Microsoft Windows]] using 'MS-NCT' protocol. | [[https://networkmanager.dev/|NetworkManager]] (**NM**) has [[https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/5307b1ed733fd0b91a1ef8bd5c58d8c68312ee2c|implemented]] same detection method as [[docs:guide-user:network:wifi:ms-meteredconnection|Microsoft Windows]] using 'MS-NCT' protocol. |
| |
| FIXME :!: As for now, according to [[https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/90818b539120b8d1d11fd2c5ecbbcf7105612c75/src/core/nm-core-utils.c#L4607|NM source code]], there is a [[https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/734|bug]] in **NM** implementation because second ''Reserved'' byte is used instead of ''Cost_Level'' byte. \\ | FIXME :!: As for now (2021.06.01), there is a [[https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/734|bug]] in **NM** implementation because second ''Reserved'' byte is used instead of ''Cost_Level'' byte. \\ |
| According to **NM** code, value of this byte must be **greater** than ''0x01'' to make **NM** think connection is metered. \\ | According to **NM** code, value of this byte must be **greater** than ''0x01'' to make **NM** think connection is metered. \\ |
| <color #ed1c24>According to [[https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nct/|[MS-NCT]]], the byte used by **NM** **SHOULD** always be 0x00, so it may cause compatibility errors, so you can change it on your own risk.</color> | <color #ed1c24>According to [[https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-nct/|[MS-NCT]]], the byte used by **NM** **SHOULD** always be 0x00, so it may cause compatibility errors, so you can change it on your own risk.</color> |