You are not logged in.
Hi,
On my laptop, I have found an instability on the eth if wlan is also connected.
The problem occurs only when I'm on visioconference over Google Hangout, Appear.in or Zoom.us, usecases probably more "sensitives"
If I'm disabling the wifi, the visio working well.
Did you ever had this kind of problem, and if yes, how did you solved it ?
Offline
Are the two NICs connected to the same network, or are they on different networks. In other words, Are you at home, using your home wireless, and then are you plugging your wired network into the same router?
Define "instability". Back that up with error messages and logs, if you please.
Edit: Also, what are you using to control your networks? Please post the output of find /etc/systemd
Last edited by ewaller (2018-04-04 14:02:57)
Nothing is too wonderful to be true, if it be consistent with the laws of nature -- Michael Faraday
Sometimes it is the people no one can imagine anything of who do the things no one can imagine. -- Alan Turing
---
How to Ask Questions the Smart Way
Offline
Are the two NICs connected to the same network, or are they on different networks. In other words, Are you at home, using your home wireless, and then are you plugging your wired network into the same router?
Yes I'm on the same network.
I have a tomato router.
The DHCP give volontary the same IP to two MAC Address : the wlan and the eth
And obviously by writing this I realize my issue probably comes from this configuration.
I set the static DHCP like that because of scripting/rsync and basically to reach my laptop with the same IP address connected by eth or by wifi.
But maybe it was an error...
Define "instability". Back that up with error messages and logs, if you please.
By instabillity, I mean : the visio broke after few minutes and I had to relaunch the visio again to estart it for few minutes more
Please post the output of find /etc/systemd
/etc/systemd
/etc/systemd/journal-remote.conf
/etc/systemd/logind.conf
/etc/systemd/network
/etc/systemd/journald.conf
/etc/systemd/user.conf
/etc/systemd/timesyncd.conf
/etc/systemd/system.conf
/etc/systemd/journal-upload.conf
/etc/systemd/user
/etc/systemd/user/default.target.wants
/etc/systemd/user/default.target.wants/xdg-user-dirs-update.service
/etc/systemd/user/sockets.target.wants
/etc/systemd/user/sockets.target.wants/dirmngr.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-extra.socket
/etc/systemd/user/sockets.target.wants/pulseaudio.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-ssh.socket
/etc/systemd/user/sockets.target.wants/gpg-agent.socket
/etc/systemd/user/sockets.target.wants/gpg-agent-browser.socket
/etc/systemd/coredump.conf
/etc/systemd/system
/etc/systemd/system/display-manager.service
/etc/systemd/system/dbus-org.freedesktop.nm-dispatcher.service
/etc/systemd/system/getty.target.wants
/etc/systemd/system/getty.target.wants/getty@tty1.service
/etc/systemd/system/remote-fs.target.wants
/etc/systemd/system/remote-fs.target.wants/nfs-client.target
/etc/systemd/system/network-online.target.wants
/etc/systemd/system/network-online.target.wants/NetworkManager-wait-online.service
/etc/systemd/system/multi-user.target.wants
/etc/systemd/system/multi-user.target.wants/rpcbind.service
/etc/systemd/system/multi-user.target.wants/cronie.service
/etc/systemd/system/multi-user.target.wants/dhcpcd.service
/etc/systemd/system/multi-user.target.wants/sshd.service
/etc/systemd/system/multi-user.target.wants/cpupower.service
/etc/systemd/system/multi-user.target.wants/remote-fs.target
/etc/systemd/system/multi-user.target.wants/NetworkManager.service
/etc/systemd/system/multi-user.target.wants/nfs-client.target
/etc/systemd/system/dbus-org.freedesktop.NetworkManager.service
/etc/systemd/resolved.conf
Offline
You're running dhcpcd and networkmanager concurrently.
Pick one or ensure to keep them apart (one service per interface - otherwise they'll enter a race on the interface and kick off each other)
Offline
The DHCP give volontary the same IP to two MAC Address : the wlan and the eth
And obviously by writing this I realize my issue probably comes from this configuration.
Yes, having the same IP for both interfaces is causing your issue.
IP addresses have to be unique on the same network, otherwise you hit all sorts of problems as the devices start fighting with your router's/switch's ARP table over who owns the address.
Offline
Thanks seth for the tip. I disabled dhcpcd.
@Slithery : I think it was this because even after disabled dhcpcd, the issue was still there.
I really like to have the same IP with eth or wlan
So I think I will find a way to select only one interface a time.
Offline
The correct solution is to have different IP addresses for each network connection, and setup a DNS server so you can use names instead of IPs when addressing your laptop.
Offline
OK noted !
Thanks !
Offline