Linux Mint/Ubuntu/Debian Dual NICs networks problem when enabling and disabling one device

The Scenario

You have dual NICs and you disable NIC1 which uses 192.168.1.1 as its gateway.  With NIC2 you enable it/connect it to another network which also has the gateway 192.168.1.1

Everything will work fine at this point.

When switching back to NIC1 even with NIC2 disabled and even unplugged, the OS basically can't pick up the new/updated ARP entry of the old device for 192.168.1.1 and perhaps thinks it is a security risk or spoof of some sorts and blocks it all.  You may think there is an issue somewhere else but the syslog shows the issue below.

Mar 13 23:16:58 mybox dbus[1698]: [system] Rejected send message, 7 matched rules; type="method_return", sender=":1.9" (uid=0 pid=2031 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=1983 comm="NetworkManager ")
Mar 13 23:16:59 mybox dbus[1698]: [system] Rejected send message, 7 matched rules; type="method_return", sender=":1.9" (uid=0 pid=2031 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=1983 comm="NetworkManager ")
Mar 13 23:17:01 mybox CRON[27807]: pam_unix(cron:session): session opened for user root by (uid=0)
Mar 13 23:17:01 mybox CRON[27807]: pam_unix(cron:session): session closed for user root
Mar 13 23:17:16 mybox sudo: pam_unix(sudo:auth): conversation failed
Mar 13 23:17:16 mybox sudo: pam_unix(sudo:auth): auth could not identify password for [one]
Mar 13 23:17:24 mybox smbd[21006]: pam_unix(samba:session): session closed for user nobody
Mar 13 23:17:41 mybox dbus[1698]: [system] Rejected send message, 7 matched rules; type="method_return", sender=":1.9" (uid=0 pid=2031 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=1983 comm="NetworkManager ")
Mar 13 23:17:42 mybox dbus[1698]: [system] Rejected send message, 7 matched rules; type="method_return", sender=":1.9" (uid=0 pid=2031 comm="/usr/sbin/dnsmasq --no-resolv --keep-in-foreground") interface="(unset)" member="(unset)" error name="(unset)" requested_reply="0" destination=":1.6" (uid=0 pid=1983 comm="NetworkManager ")

Solution

 sudo service network-manager restart
network-manager stop/waiting
network-manager start/running, process 31647
 


Tags:

linux, mint, ubuntu, debian, dual, nics, networks, enabling, disabling, devicethe, disable, nic, gateway, enable, switching, disabled, unplugged, os, updated, arp, entry, spoof, syslog, mar, mybox, dbus, rejected, matched, quot, method_return, sender, uid, pid, comm, usr, sbin, dnsmasq, resolv, foreground, interface, unset, requested_reply, destination, networkmanager, cron, pam_unix, user, sudo, auth, password, smbd, samba, restart,

Latest Articles

  • Cisco Router Setup Guide and Tutorial Howto With Commands and Examples
  • Linux Bash Script To List All Connected IPs and their network name
  • Cisco Switches How To Get Of Port Line Status Console Messages
  • Cisco DHCP Snooping Relay Setup Information
  • Cisco Switch Setup Guide Command List
  • Cisco 2960 Switch Reset To Factory Defaults
  • How To Boot Cisco CUCM UCSInstall 8.6, 10, 11 and 12 on KVM/Proxmox
  • VBOX VirtualBox How To Import Raw .img Disk File
  • Windows Server 2012, 2016, 2019 How To Install and Missing Disabled Telnet Client
  • proxmox vm networking breaks when you restart your network on the hostnode
  • Linux ln symlink how to update existing symbolic link
  • Ubuntu 18.04 / Linux Mint 19.1 Cannot Type or Login - solution
  • LUKS Hard Drive Encryption on Linux Mint Ubuntu Debian etc how to mount encrypted hard drive
  • How to use nmap locate other machines/computers/servers on your network using nmap
  • Linux Mint 18.2 Create Config File To Start Application Upon Login
  • Dell Wyse Thin Client BIOS Access Key
  • sudoers file in /etc warning about comments/includes!
  • Centos 7 Reallocate logical volume space to another
  • lvm how to reduce volume size
  • letsencrypt certbot error "Unable to find a virtual host listening on port 80 which is currently needed for Certbot to prove to the CA that you control your domain. Please add a virtual host for port 80."