Tag Info

New answers tagged

0

If you can ping any Gateway, you don't need an ethernet driver, because ethernet is already working. From what you described, I would say your network setup is just wrong. You most probably need to configure a proper routing setup so that your host knows how to get to the outside world. If available in your network, try first using DHCP. Now, depending on ...


2

I have same ethernet controller and same problem. It will work with: sudo modprobe -v r8169 Make a test manually, if it work fine add this command permanently: sudo gedit /etc/rc.local before 'exit 0' Really this is a bug at version 15.04 after actualization kernel 3.19.0-25. Before this kernel (3.19.0-22) it's worked perfectly.


0

Without further data, the easiest fix is to go into the VM's settings directly, select the virtual network adapter, and edit it so that it is using NAT. This will let it communicate outbound via the host computer's connections which are already active. (This is also the least headachey to set up)


1

Most simple must be to get one repeater of wireless that has etherenet connection. I have one "netgear range extender" that has ethernet interface. They do not cost much, and you do not need to change anything in the system.


1

Please make sure that NetworkManager is properly installed and not messed up. To find try the following command in terminal: which NetworkManager It should return /usr/sbin/NetworkManager To reinstall NetworkManager have a look at https://help.ubuntu.com/community/NetworkManager


0

The problem is with glitchy Realtek driver r8169. Many reported that disabling autonegotiation helps. You can turn it off by using the following command: sudo ethtool -s eth0 speed 100 duplex full autoneg off


0

You need to install firmware. Run in terminal sudo apt-get install firmware-b43-installer


0

Run in terminal sudo apt-get install r8168-dkms and reboot. This will install another driver. It should work better.


1

First you can fix your wireless connection by running in terminal sudo tee /etc/modprobe.d/iwlwifi-opt.conf <<< "options iwlwifi 11n_disable=1" and reboot. You seem to be behind a proxy. You will need to add it to your configuration. Run gedit ~/.bashrc and add at the bottom of the file ...


0

First you must install sudo apt-get install vlan load kernel module sudo modprobe 8021q Create a new interface that is a member of a specific VLAN, VLAN id 100 We use the physical interface eth0 in this example. This command will add an additional interface next to the interfaces which have been configured already sudo vconfig add eth0 100 ...


3

From the quoted link: If a DHCP client attempts to get an address, but fails to find a DHCP server after the timeout and retries period it will randomly assume an address from this network. This allows communication with hosts that have failed to obtain a DHCP address. However, your interfaces file requests a static IP address that is likely ...


0

First you have to configure IP address for both Ubuntu and Windows 7. (http://www.howtogeek.com/howto/19249/how-to-assign-a-static-ip-address-in-xp-vista-or-windows-7/). Also change Ubuntu IP address (How to set static IP address?) Windows 7 IP Configurations IP Address : 192.168.2.2 Subnet Mask : 255.255.255.0 Default gateway : 192.168.2.1 Ubuntu IP ...


1

Try NitroShare ! Which will support Ubuntu as well as Windows To Install: sudo add-apt-repository ppa:george-edison55/nitroshare-dev sudo apt-get update sudo apt-get install nitroshare For details click here http://nitroshare.net/downloads/


0

cat /proc/net/dev to get the list of available interfaces (most likely you'll have eth0 and wlan0). Then ifup the interface via sudo ifconfig eth0 up. You may need to run sudo dhclient eth0 once the interface is up to get an IP address. For wireless interface, after ifup, you'll need Network Manager to configure it to connect to a given AP. Also if ...


0

You need to read this: https://wiki.debian.org/NetworkConfiguration It helps out with learning what you need to do for what.


0

The problem may come from your router that your computer is connected to, some people had issue while dual booting Windows and Ubuntu. Their workaround was to disable DHCP and manually assign the same IP address to Windows and Ubuntu.


0

I have the same/similar problem. As long as I don't use Windows® I can reliably connect even after multiple reboots. However any time after I boot into Windows®, then if I want to use my wired ethernet in Linux, I must power down the computer AND remove the AC cord into the computer's power supply AND remove the ethernet cable into the computer for a few ...


0

This adapter [10ec:8168] does not need r8168 driver. Default r8169 module supports it better. You can test it by sudo modprobe -r r8168 sudo modprobe r8169 If you installed r8168 from Ubuntu repositories, then run sudo apt-get purge r8168-dkms to make it permanent.


0

Your module must be badly supported by the kernel r8169 module. Connect to internet using some other adapter and run in terminal sudo apt-get install r8168-dkms


1

As sharing the folders which containing the files is possible scenario i recommend samba configuration on ubuntu which will setup shared folder due to which you can simply copy paste whichever file you like from both ubuntu to mac or vice-versa samba installation in ubuntu


0

Using route -n and also nm-tool: I could see that eth1 had become set as the default, and was pointing to the gateway address. Our setup required eth0 to be the default. This was resolved using: sudo ip route change to default dev eth0 via 172.21.0.1 where 172.21.0.1 is the gateway address.


0

The easiest would be to make a bridge(laptop): apt-get install bridge-utils brctl addbr br1 brctl addif br1 eth0 brctl addif br1 wlan0 ifconfig br1 up dhclient -4 br1 See this tutorial: https://help.ubuntu.com/community/NetworkConnectionBridge


0

From what I can tell, you have a wireless network with resources you need to access from your desktop. See this tutorial: https://help.ubuntu.com/community/NetworkConnectionBridge The easiest would be to make a bridge(laptop): apt-get install bridge-utils brctl addbr br1 brctl addif br1 eth0 brctl addif br1 wlan0 ifconfig br1 up dhclient -4 br1


0

The majority of these instructions are for the laptop. First of all, disable UFW firewall for now: sudo ufw disable Next, plug the ethernet cable into both computers. Now, click on network-manager icon on the laptop and select edit connections. Click to select the wired connection and then click edit. Click on the ipv6 settings tab and change the ...


0

To bond two virtual interfaces eth0:1 and eth0:2, to create an auto failover interface, try this: Open a terminal,Press Ctrl+Alt+T Run it: To enable bonding You must install the ifenslave package: sudo apt-get update sudo apt-get install ifenslave To configure it, You must modify the /etc/network/interfaces file: sudo nano /etc/network/interfaces ...


1

Here are some possible options and alternatives I can suggest: Download the driver on Windows machine, save on USB, transfer to Ubuntu, install that driver with sudo dpkg -i package-file. Boot that Windows machine with an Ubuntu Live CD or USB that you used for installing Ubuntu (hopefully you still have it) and use that live desktop in as wifi to ...


1

Another solution, using udevadm udevadm info -a -p /sys/class/net/eth{0..10} | awk '/device.*eth/' {0..10} – checks the initerfaces from eth0 … eth10 Therefore you could use this command pci_address=$(udevadm info -a -p /sys/class/net/eth{0..10} | awk -F/ '/device.*eth/ {print $4}') Example output looking at device ...


2

lswh and lspci bot are capable of showing that information.As you have found out already, you can do lshw -class network -businfo. For instance, here's my output: $ sudo lshw -c network -businfo Bus info Device Class ...


1

It looks you can tie them together by the IRQ. ifconfig -a will print the ethernet devices including Interrupt. eg. eth2 Link encap:Ethernet HWaddr 00:25:11:19:8b:77 inet addr:192.168.1.3 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::225:11ff:fe19:8b77/64 Scope:Link UP BROADCAST RUNNING MULTICAST ...


0

Okay I solved the problem with this commands: ip link set dev eth2 down sudo dhclient eth2


2

You can try to install another driver for this Ethernet card sudo apt-get install r8168-dkms If that does not help, check the cable, contacts on both sides. Expanaition Realtek Ethernet RTL8111/8168 adapters are generally supported out of the box by Linux kernel. There is r8169 module for that. In most cases it works well. But some hardware revisions ...



Top 50 recent answers are included