New answers tagged

0

for product: RTL8101/2/6E PCI Express Fast/Gigabit Ethernet controller the above solution didn't work. i had to download driver from: http://www.realtek.com.tw/downloads/downloadsView.aspx?Langid=1&PNid=7&PFid=7&Level=5&Conn=4&DownTypeID=3&GetDown=false#2 and install with ./autorun.sh . After that i still couldn't connect to the ...


0

There is some issue with dynamic IP allocation in Ubuntu 16.04 LTS Please use the below code and it work fine: sudo dhclient


0

I am running Ubuntu 16.04.1 LTS, Linux plaptop 4.4.0-31-genericx86_64 MATE. I did only step one and it worked. Ubuntu created a new names directly after reboot: Edit your /etc/default/grub changing the line from GRUB_CMDLINE_LINUX="" to GRUB_CMDLINE_LINUX="net.ifnames=0 biosdevname=0" and, finally run as root: $ sudo update-...


1

I think I have found a simpler work around for this. I still use the usual Network Connections interface to populate all the 802.1x Security tab including the password (this is neccessary to activate the 'Save' button even though the password isn't stored correctly). I then open a terminal and run "nmtui-connect" and activate the connection there, it ...


0

If you have installed a file sync program (for instance, Dropbox or ownCloud), try disabling and removing them. After a restart, check if you're still randomly disconnecting. Me and another user have made the same complaint, and you seem to have the same issues.


1

In your log I see that ipv6 is configured too Jul 17 10:56:41 ninja-desktop avahi-daemon[593]: Joining mDNS multicast group on interface eth0.IPv6 with address fe80::eea8:6bff:fe70:9564. Jul 17 10:56:41 ninja-desktop avahi-daemon[593]: New relevant interface eth0.IPv6 for mDNS. Jul 17 10:56:41 ninja-desktop avahi-daemon[593]: Registering new address record ...


0

You need to check the DNS settings of your network. Go to Network--> Settings--> IPV4 Settings-->Additional DNS Settings add the DNS address provided by your service provider, restart the browser and check.


0

First try to get the firmware. wget http://mirrors.kernel.org/ubuntu/pool/main/l/linux-firmware/linux-firmware_1.158_all.deb sudo dpkg -i linux-firmware*.deb sudo modprobe -r ath10k_pci && sudo modprobe ath10k_pci Reboot. This should fix your wireless adapter issues. If it does not, please post the output for dmesg|grep ath10k after following ...


-1

It is possible, edit the following file with your favorite editor (vi for example) vi /etc/udev/rules.d/70-persistent-net.rules


0

It looks like you don't have some software that is usually included with a default Ubuntu install. This is probably why wifi worked during the live session but did not work after the install. Preferably, you should find an ethernet cable to provide network access. After you establish a network connection, press CTRL + ALT + T to open a terminal and then ...


0

You can assign a different IP address to each network interface or have them assigned by the DHCP server on their respective network (the default if you don't assign an IP manually). You already assigned an IP address to the wired network interface and I would guess that the wireless network has a DHCP server, so you can just leave that at its default ...


0

Check if the wire works at all. There is absolutely no reason why a stock configuration would not be able to handle an Ethernet connection. This is a hardware issue.


1

Speculative answer: You probably have a DHCP server on your network, that periodically hands out "leases" on the addresses in its pool. Your static address ending in 110 is in that pool, but it hasn't been handed out by the DHCP so it takes it back, and gives you 134 in return. Try a different IP address as far away from the DHCP pool as possible, which ...


0

Login to your router by typing your router ip into the address, usually 192.168.1.254 or 192.168.1.1 Look for something like DHCP server settings and turn the DHCP server off then see if it makes any difference.


0

Check the gateway settings. On the gateway -router you will need to assign the same static ip address based on your server MAC address.


0

After restart eth0 does not come up. My problem was auto eth0 in /etc/network/interfaces was commented: #auto eth0 Removed the # and it's OK.


1

It would appear (tested with ifupdown version 0.7.53.1) that we can add several iface eth0 inet6 stanzas to the interfaces file, which is more declarative than the accepted answer. The following code instructs the ifupdown suite to use stateless autoconfiguration and two additional static IPv6 addresses for the eth0 network interface: iface eth0 inet6 auto ...


0

If you have a DHCP Server in you network, try (as root): $dhclient In a Terminal/Shell. This should work. If you need a specific configuration, you can do this like the others described in /etc/network/interfaces and /etc/resolv.conf (for the nameservers). I think it would be a good idea, if you post your /etc/network/interfaces and /etc/resolv.conf, ...


0

Well, you could have a hidden error (surely you don't have address X in your file), and using X for all values makes it hard for me to tell you to do: ip route sudo ip route add X dev enp0s31f6 In this case, by X, I mean the same X you hid from us in gateway X


1

Your interfaces file need only contain: # The loopback network interface auto lo iface io inet loopback # The primary network interface auto enp0s31f6 iface enp0s31f6 inet static address xxx netmask xxx gateway xxx dns-nameservers xxx Please note that you said 'adress' and it should be address. Be sure to select an address outside the range used in the ...


1

See if your interface got an ip from dhcp first. ifconfig -a (if it doesn't have an ip try assigning one manually) Then if you got an ip then try ping <gateway> (if this doesn't work your network config is wrong) If that works then try pinging a public ip like 8.8.8.8. (if this works then your name resolution is not working (dns). cat /etc/...


1

Looking at some of the specifications of the Summit X440 series switches I can see both console and net management ports: Summit X440-8t 8 x 10/100/1000BASE-T (RJ45) ports 4 x 100/1000BASE-X (SFP) unpopulated ports 2 x SummitStack 1 x Serial (console port) 1 x 10/100BASE-T out-of-band management port The last port listed is the net management port, ...


0

Not a full solution, but downloading WICD decreased the frequency of network problems I experienced when I was using lubuntu.


0

The easiest way to do it, is using a router. Or connect both pc using ethernet cable and activate internet connection sharing in windows 10.


1

You'd need to get both machines on the same local network (LAN). Once you have that, you can either define one as the default gateway of the other. Or you can just connect both machines to your LAN and use the central networking device as gateway for both. But to create a LAN, it probably won't be enough to just put a cable between them. You'd need some ...


1

-H is to specify a host file in a format similar to your system's /etc/hosts file. If that isn't what you're attempting to use, look into -f flag. This allows you to use a tcpdump style pre or post filter - depending on where it is placed. Here are a few examples: tshark -f "host 192.168.1.1" -i eth0 -w outputfile.pcap tshark -i eth0 -f "host 192.168.1....



Top 50 recent answers are included