Comments (2)
mzanetti
commented on June 1, 2024
Hmm... this is strange... it's not that nymea-networkmanager requires DCHP to be turned off, but rather that it requires the use of NetworkManager, which brings its own implementation for DHCP (actually uses dhclient internally) and conflicts with dhcpcd. There are a lot of nymea setups on ethernet and so far no problems with DHCP on ethernet were reported.
Are you perhaps suffering from something like this? https://bbs.archlinux.org/viewtopic.php?id=192894
from nymea-networkmanager.
Nosfistis
commented on June 1, 2024
It seems that nymea-networkmanager is not the problem. Indeed I found that it uses the standard NetworkManager behind the scenes. The problem also does not seem to be consistent - different connections to a router and different cables might cause or not a connection, in a way that the ethernet does not even get an IPv4. The logs do not look the same as the link you supplied either:
Dec 25 14:21:24 RPi-3 NetworkManager[356]: <info> [1608898884.7272] device (eth0): carrier: link connected
Dec 25 14:21:24 RPi-3 NetworkManager[356]: <info> [1608898884.7301] device (eth0): state change: unavailable -> disconnected (reason 'carrier-changed', sys-iface-state: 'managed')
Dec 25 14:21:24 RPi-3 NetworkManager[356]: <info> [1608898884.7381] policy: auto-activating connection 'Wired connection 1' (699f2b07-a157-30fe-809a-dfb3fa5e8614)
Dec 25 14:21:24 RPi-3 nymea-networkmanager[636]: I | NetworkManager: "eth0" --> State changed: "NetworkDeviceStateDisconnected" : "NetworkDeviceStateReasonCarrier"
Dec 25 14:21:24 RPi-3 NetworkManager[356]: <info> [1608898884.7454] device (eth0): Activation: starting connection 'Wired connection 1' (699f2b07-a157-30fe-809a-dfb3fa5e8614)
Dec 25 14:21:24 RPi-3 NetworkManager[356]: <info> [1608898884.7486] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
Dec 25 14:21:24 RPi-3 NetworkManager[356]: <info> [1608898884.7548] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
Dec 25 14:21:24 RPi-3 NetworkManager[356]: <info> [1608898884.7626] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'managed')
Dec 25 14:21:24 RPi-3 NetworkManager[356]: <info> [1608898884.7662] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Dec 25 14:21:24 RPi-3 NetworkManager[356]: <info> [1608898884.7785] dhcp4 (eth0): dhclient started with pid 855
Dec 25 14:21:24 RPi-3 nymea-networkmanager[636]: I | NetworkManager: "eth0" --> State changed: "NetworkDeviceStatePrepare" : "NetworkDeviceStateReasonNone"
Dec 25 14:21:24 RPi-3 nymea-networkmanager[636]: I | NetworkManager: "eth0" --> State changed: "NetworkDeviceStateConfig" : "NetworkDeviceStateReasonNone"
Dec 25 14:21:24 RPi-3 nymea-networkmanager[636]: I | NetworkManager: "eth0" --> State changed: "NetworkDeviceStateIpConfig" : "NetworkDeviceStateReasonNone"
Dec 25 14:21:27 RPi-3 NetworkManager[356]: <info> [1608898887.1559] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
Dec 25 14:21:27 RPi-3 NetworkManager[356]: <info> [1608898887.1670] dhcp6 (eth0): dhclient started with pid 861
Dec 25 14:21:28 RPi-3 NetworkManager[356]: <info> [1608898888.8744] dhcp4 (eth0): address 192.168.1.115
Dec 25 14:21:28 RPi-3 NetworkManager[356]: <info> [1608898888.8746] dhcp4 (eth0): plen 24 (255.255.255.0)
Dec 25 14:21:28 RPi-3 NetworkManager[356]: <info> [1608898888.8747] dhcp4 (eth0): gateway 192.168.1.1
Dec 25 14:21:28 RPi-3 NetworkManager[356]: <info> [1608898888.8749] dhcp4 (eth0): lease time 86400
Dec 25 14:21:28 RPi-3 NetworkManager[356]: <info> [1608898888.8750] dhcp4 (eth0): nameserver '192.168.1.1'
Dec 25 14:21:28 RPi-3 NetworkManager[356]: <info> [1608898888.8752] dhcp4 (eth0): state changed unknown -> bound
Dec 25 14:21:28 RPi-3 NetworkManager[356]: <info> [1608898888.8951] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'managed')
Dec 25 14:21:28 RPi-3 nymea-networkmanager[636]: I | NetworkManager: "eth0" --> State changed: "NetworkDeviceStateIpCheck" : "NetworkDeviceStateReasonNone"
Dec 25 14:21:28 RPi-3 NetworkManager[356]: <info> [1608898888.9059] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'managed')
Dec 25 14:21:28 RPi-3 NetworkManager[356]: <info> [1608898888.9120] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'managed')
Dec 25 14:21:28 RPi-3 NetworkManager[356]: <info> [1608898888.9380] policy: set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS
Dec 25 14:21:28 RPi-3 NetworkManager[356]: <info> [1608898888.9429] dns-mgr: Writing DNS information to /sbin/resolvconf
Dec 25 14:21:29 RPi-3 NetworkManager[356]: <info> [1608898889.0007] device (eth0): Activation: successful, device activated.
Dec 25 14:21:29 RPi-3 dbus-daemon[336]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=356 comm="/usr/sbin/NetworkManager --no-daemon ")
Dec 25 14:21:29 RPi-3 nymea-networkmanager[636]: I | NetworkManager: "eth0" --> State changed: "NetworkDeviceStateSecondaries" : "NetworkDeviceStateReasonNone"
Dec 25 14:21:29 RPi-3 nymea-networkmanager[636]: I | NetworkManager: "eth0" --> State changed: "NetworkDeviceStateActivated" : "NetworkDeviceStateReasonNone"
Dec 25 14:21:40 RPi-3 systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Dec 25 14:22:05 RPi-3 NetworkManager[356]: <info> [1608898925.5465] device (eth0): state change: activated -> unavailable (reason 'carrier-changed', sys-iface-state: 'managed')
Dec 25 14:22:05 RPi-3 NetworkManager[356]: <info> [1608898925.6155] dhcp4 (eth0): canceled DHCP transaction, DHCP client pid 855
Dec 25 14:22:05 RPi-3 NetworkManager[356]: <info> [1608898925.6156] dhcp4 (eth0): state changed bound -> done
Dec 25 14:22:05 RPi-3 NetworkManager[356]: <info> [1608898925.6215] dhcp6 (eth0): canceled DHCP transaction, DHCP client pid 861
Dec 25 14:22:05 RPi-3 NetworkManager[356]: <info> [1608898925.6218] dhcp6 (eth0): state changed unknown -> done
Dec 25 14:22:05 RPi-3 NetworkManager[356]: <info> [1608898925.6336] dns-mgr: Writing DNS information to /sbin/resolvconf
Dec 25 14:22:05 RPi-3 nymea-networkmanager[636]: I | NetworkManager: "eth0" --> State changed: "NetworkDeviceStateUnavailable" : "NetworkDeviceStateReasonCarrier"
Dec 25 14:22:05 RPi-3 NetworkManager[356]: <info> [1608898925.7412] policy: set 'guest-network' (wlan0) as default for IPv4 routing and DNS
Dec 25 14:22:05 RPi-3 dbus-daemon[336]: [system] Activating via systemd: service name='org.freedesktop.nm_dispatcher' unit='dbus-org.freedesktop.nm-dispatcher.service' requested by ':1.8' (uid=0 pid=356 comm="/usr/sbin/NetworkManager --no-daemon ")
Dec 25 14:22:16 RPi-3 systemd[1]: NetworkManager-dispatcher.service: Succeeded.
I am trying to check if this is an issue when using both wlan0 and eth0, but since this is not a fault of nymea-networkmanager, I am closing this issue.
from nymea-networkmanager.
Related Issues (20)
- symbol lookup error: undefined symbol: _ZN15BluetoothServer14runningChangedERKb HOT 6
- Pi Zero Build not working HOT 16
- Repo problems HOT 2
- Two wlan interfaces HOT 2
- Custom native app to interact with nymea HOT 21
- issue installing berrylan on arm64 HOT 2
- Berrylan only works with a fresh SD card install. 2nd boot, get "error occurred trying to start advertising" HOT 6
- L2CAP write request incomplete: 0 of 23 HOT 7
- Communicate via BT Browser API HOT 1
- stopping nymea after network established and running secondary ble HOT 8
- Wireless networks duplicated HOT 7
- nymea-networkmanager asking to pair HOT 2
- Unable to start NetworkManagerBluetoothServer with newest Intel NUC devices HOT 5
- Impossible to find the bluetooth device - Pi Zero HOT 7
- API needs better error handling capabilities
- Bluetooth stops advertising after 1 minute HOT 5
- NetworkManager start/stop bluetooth repeatedly on Raspbian 11 64bit on Pi 4 HOT 2
- Stuck on Setting up nymea-networkmanager (1.0.0+202203142203~buster+rpi1) ... HOT 1
- Service hangs/stop responding after connecting to network HOT 5
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from nymea-networkmanager.