Every network device has a type. This is stored in the sysfs under
'/sys/class/net//type' as a number and can be queried.
This commit adds this information as a string to the ubus.
'ubus call network.device status'
{
...
"eth0": {
"dev_type": "ETHER",
...
}
Signed-off-by:
Every network device has a type. This is stored in the sysfs under
'/sys/class/net//type' as a number and can be queried.
This commit adds this information as a string to the ubus.
'ubus call network.device status'
{
...
"eth0": {
"dev_type": "ETHER",
...
}
Signed-off-by:
Could coreutils in rust be interesting for this project? (memory safety,
at least at a later date)
They use MIT license, however.
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
They use MIT license, however.
https://github.com/uutils/coreutils
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
> On 6. Dec 2021, at 13:37, Paul D wrote:
>
> Could coreutils in rust be interesting for this project? (memory safety, at
> least at a later date)
I think long term rust routers would be of interest, did you already do some
rather research? From a first looks it seem to miss a shell which i
On 2021-12-06 14:33, Paul Spooren wrote:
On 6. Dec 2021, at 13:37, Paul D wrote:
Could coreutils in rust be interesting for this project? (memory safety, at
least at a later date)
I think long term rust routers would be of interest, did you already do some
rather research? From a first l
Hi,
imho these types are not that useful in practice (e.g. tap devices etc. are
all reported as "ethernet". Maybe expose /sys/class/net/$devname/uevent
DEVTYP= instead.
~ Jo
signature.asc
Description: OpenPGP digital signature
___
openwrt-devel maili
Could this be picked to 21.02 branch, please?
https://github.com/openwrt/openwrt/commit/e309b57619b9c073b9b8857858d9456183f27d7d
___
openwrt-devel mailing list
openwrt-devel@lists.openwrt.org
https://lists.openwrt.org/mailman/listinfo/openwrt-devel
I tried enabling the wifi settings for 2.4 and 5Ghz.:
== time_advertisement ==
Result: OK. Time appears in beacon frames. e.g.
Tag: Time Advertisement
Tag Number: Time Advertisement (69)
Tag length: 17
Timing capabilities: UTC time at which the TSF timer is 0 (2)
Time Value: e50
From: Junnan XU
The value of the resolv_conf variable can be specified by input parameters
when netifd is started.So when the length of the resolv_conf variable value
is less than "/tmp/resolv.conf-%s.d/resolv.conf.auto", the memory
out-of-bounds operation will occur in interface_write_resolv_co
10 matches
Mail list logo