Tag Info

New answers tagged

0

as from dmesg -T | grep eth0 output, you are using r8169 driver which has been unstable for few network cards try manually downgrading driver to r8168 hope this helps


2

Usually you don't need to specify broadcast. The broadcast address is the last address in subnet. The network mask already specifies the range of the subnet. When you configure an interface, you may set the IP address and network mask only. The order of the parameters in your command is wrong. You tell your NIC to set broadcast and netmask before ip ...


0

Yes, you can do that in Ubuntu too. There is a detailed description here. I hope you should follow that and see if you can solve your problem.


0

In the question you reference, the second answer shows the equivalent solution for IPv4. In the case of IPv6, the /etc/network/interfaces file should contain something like this: iface eth0 inet6 static address 2001:db8:1:2::2 netmask 64 # Add additional IPv6 addresses when $IFACE goes up up ip -6 addr add 2001:db8:1:2::3/64 dev $IFACE up ip -6 ...


0

May be you could try to limit the speed of the ethernet adapter ? Try: sudo ethtool -s eth0 speed 100 duplex half Or if this does not help, try https://unix.stackexchange.com/questions/37727/solving-ethernet-watchdog-timer-deadlocks


0

Same here... worked perfectly in 14.04 then there were issues in 14.10 with virtual machines causing eth0 to stop working now in 15.04 eth0 only works for a few seconds then stops. if I restart $ sudo service network-manager restart then the network comes back up for only a few seconds then stops again. The driver is "alx" $ lshw *-network ...


0

If you have networking and can ping by IP address or hosts listed in your /etc/hosts file, but can't browse to websites, it sounds like improper DNS resolution. Some quick tests: $ ls -l /etc/resolv.conf lrwxrwxrwx 1 root root 29 Apr 23 09:44 /etc/resolv.conf -> ../run/resolvconf/resolv.conf $ cat /etc/resolv.conf # Dynamic resolv.conf(5) file for ...


0

Found answers here and here. And the conclusion I take from this mess is: I'm not coming back, Red Hat, not after throwing 4+ hours in the trash for nothing.


1

You make mistake not sudo ifconfig eth10 192.168.1.150 you must add network mask sudo ifconfig eth10 192.168.1.150 netmask 255.255.255.0


0

I'm not really that this is a bug really. Considering that it works for a majority of users Using openVPN and network manager. Do you have the proper permissions of the key and certificate file? What happens if you run openvpn --config nameofyourconfigfile.conf as root from the terminal? please paste the output here if it does not work. It should ...


0

The following command resolved the problem echo -e "nameserver 8.8.8.8\nnameserver 8.8.4.4" | sudo tee /etc/resolv.conf Then restart network-manager with the following command sudo service network-manager restart Then I restarted the computer for it to work.


0

Add "forcedeth msi=0 msix=0" to /etc/modules. This way you won't have to stop the loaded module and reload it with the proper options as it sould be loaded properly to begin with. Sources: Previous clues in comments and other answer. http://ubuntuforums.org/archive/index.php/t-1982856.html


1

Note: I'm posting this workaround as an answer due to the number of times this has been reported as a bug only to expire shortly thereafter and resurface again. Test Enter Ubuntu recovery mode: a. Power on system and press "Shift" during boot up for GRUB menu. b. Choose "Advanced options for Ubuntu" > Ubuntu, [kernal version] (recovery mode) Choose ...


0

Note that for a windows guest, you might need to install special drivers for virtio to work properly. Please see these references: http://wiki.libvirt.org/page/Virtio http://www.linux-kvm.org/page/WindowsGuestDrivers/Download_Drivers https://launchpad.net/kvm-guest-drivers-windows/+download The following is from one of my VM's. Your mac address and address ...


1

It seems the 8169 driver listed in your configuration for the wired network connection doesn't function properly and the 8168 is the better choice. 1) Download the appropriate version of the driver for your kernel version from the Realtek download page I used this page. and chose the Global link for LINUX driver for kernel 3.x and 2.6.x and 2.4.x 2) ...


1

I needed to change driver of the Realtek ethernet controller from r8169 to r8168. I used the method on https://unixblogger.wordpress.com/2011/10/18/the-pain-of-an-realtek-rtl8111rtl8168-ethernet-card/ (via a link by user Elder Geek).


2

Stop worrying! You'll have a heart attack before your time! ;-) Promiscuous mode on a computer has nothing to do with catching nasty viruses like AIDS... It just means that your network adapter will be able to read TCP/IP packets that are meant for other adapters. (A.k.a. "sniffing" and that's a great tool to find obscure TCP/IP communication bugs)



Top 50 recent answers are included