Hot answers tagged

4

I had same problem. use package in this page (or build it if you don't trust) http://tomtomtom.org/networkmanager-openconnect/ It works for me


3

I had this very same issue with connection.gateway-ping-timeout. Forcing a value different from default 0 from a shell worked for me: nmcli c modify "Wired connection 1" connection.gateway-ping-timeout 10 I was then able to configure a manual IP address from the KDE Connection Editor.


2

Make the parameter permanent with the terminal: sudo -i echo "options rtl8723ae msi=1" > /etc/modprobe.d/rtl8723ae.conf exit Upon boot you should be all set.


2

Please make sure you have the following packages installed: network-manager-openvpn network-manager-openvpn-gnome network-manager-pptp network-manager-vpnc You can install them on the command line by copying and pasting the following command: sudo apt install network-manager-openvpn network-manager-openvpn-gnome network-manager-pptp ...


2

I've got this device too. We need both of these files for WiFi to work: /lib/firmware/brcm/brcmfmac43340-sdio.bin /lib/firmware/brcm/brcmfmac43340-sdio.txt Step 1 Using Android firmware was the standard fix for our card (and still works), but now you can get the binary from the Linux firmware repository (and it's already in the installation with 16.04, so ...


1

Finally I was able to fix the issues after trying out numbers of different methods. Get details of your PCI wireless card by running sudo lshw -class network Get your card model info according to the product line. For instance, as you can see in the question description it says product: RTL8723BE PCIe Wireless Network Adapter so the model of my card is ...


1

You'll need to add a route to 10.0.0.0/8: route add -net 10.0.0.0 netmask 255.0.0.0 gw 10.73.9.1 dev em2 (untested) To make it permanent add it to your interfaces config in the em2 section: up route add -net 10.0.0.0 netmask 255.0.0.0 gw 10.73.9.1 dev em2 Just for understanding: Your computer knows where to send packets in your local net. For everything ...


1

The problem was my ethernet adapter was not being driven at all. I found that the realtek site only offered drivers for linux kernels 3.x or older so I installed 14.04 and installed the driver and its online now.


1

OK, I think I got it - my Auto Ethernet connection was set to Method "Automatic (DHCP)", and I noticed more-less by accident there is another option "Automatic (DHCP) addresses only", so I tried setting that: ... and finally, I can have both local Ethernet and broadband connections active - and I can access both local network addresses and Internet. Hope ...


1

To supplement Morteza Pourkazemi's answer, the answer works for me, but I need to install the following packages which are required by the configure command. sudo apt-get install intltool libxml2-dev libgtk-3-dev libsecret-1-dev libopenconnect-dev network-manager-dev libnm-util-dev libnm-glib-dev libnm-glib-vpn-dev


1

What you are seeing is not your machine remembering the IP. In syslog you see DISCOVER REQUEST OFFER ACK however this is not in the order that it happened. It actually went DISCOVER OFFER REQUEST ACK to confirm this you can sniff the traffic between the PC and upstream DHCP server. You sent DISCOVER the server sent back OFFER and you got the IP from the ...


1

Could it be the DHCP lease time? Does the router release the address after 24 hours, perhaps? (Of course, you would then want to ask why it didn't refresh automatically)


1

If I understand correctly you want sometimes a different configuration for your network and you want to use Network Manager - I presume GUI. So you open the network manager, add another connection (call it static address or so). Now configure this connection with the settings you want, don't set Automatically connect to this network.. Whenever you need ...


1

The problem here is evident in this log line: Thu Mar 17 16:13:37 2016 /sbin/ip route add 192.168.1.0/24 via 10.0.254.21 Openvpn causing traffic for your local LAN to be routed via the tunnel interface. The following log line shows that 10.0.254.21 is the remote end of your tunnel connection: Thu Mar 17 16:13:34 2016 /sbin/ip addr add dev tun0 ...


1

This is and always will be a will guess without being on-site, but there here are some reasons that might prevent Ethernet to function properly. Windows driver for the card might be able to do some automagic to degrade the settings of your card. Or the card needs some poke to do the autonegotiation. The most obvious might be duplicate MAC addressed. ...


1

Another tool that you might want to employ is iperf. You can use this to determine if the local networking is killing your throughput. A reference is located at: https://iperf.fr/. You can simply generate high bandwidth loads and then check what that actual reported throughput is. If you have two nodes you can do the following check. First run sudo lshw -c ...


1

You can use the ip command for setting up routes. You basically need to remove your default route. At make sure you have a route entry into your local network.


1

I am experiencing the same issue. It looks like a bug, according to this link: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/606365


1

I am having the same problem on fresh install of Ubuntu 16.04. You can however connect via terminal : sudo openconnect https://<remote.host.here> after that you should be prompted for user name and password.



Only top voted, non community-wiki answers of a minimum length are eligible