D
dsk
Guest
I have an internet connection that won't stay connected.
My build:
Arch x86_64 plain UEFI/BIOS install on USB mSATA SSD
Network Manager
dhcp is enabled at boot with static IP
resolv.conf is set to use OpenNIC
I have no problem with booting up and connecting to the internet. However, it will eventually disconnect and I can not reconnect until I reboot. I always get the same timeout failure.
This seems to only occur when I am using a VPN or VirtualBox (E.g.: Windows 7 VM from inside Arch). I can still initally use the VPN or VM internet normally with good settings but it will inevitable disconnect. I don't want to conclude that the VPN or VM are related to the cause but I do notice that it will happen fairly quickly (5 minutes to 1 hour).
I may not fully understand how dhcp, resolv.conf and resolvconf.conf are working in relation to each other.
All generate an identical output before and after the fact:
ip addr, ip route, iw list, iw mlan0 info
I have added this to create a static IP:
dhcpcd.conf
# define static profile
profile static_mlan0
static ip_address=192.168.1.11
static routers=192.168.1.1
static domain_name_servers=107.170.95.180
# fallback to static profile on mlan0
interface mlan0
fallback static_mlan0
I added the OpenNic DNS servers to resolv.conf:
resolv.conf
# Generated by resolvconf
nameserver 198.100.146.51
nameserver 192.168.1.1
nameserver 107.170.95.180
nameserver 75.127.14.107
Intersetingly, even with 192.168.1.1 there, I do not have the heartbleed, atleast according to IPLeak. Oddly, to me, 107.170.95.180 is never at the top of the list even it is written expressly in the dhcpcp.conf. It is using the manual entry from resolvconf.conf.
resolvconf.conf
name_servers=75.127.14.107
name_servers=107.170.95.180
name_servers=198.100.146.51
Journaling has been off in fstab since creation per SSD r/w issues.
I have been struggling to understand how I can fix this issue for over a month and a half. Any help would be appreciated.
My build:
Arch x86_64 plain UEFI/BIOS install on USB mSATA SSD
Network Manager
dhcp is enabled at boot with static IP
resolv.conf is set to use OpenNIC
I have no problem with booting up and connecting to the internet. However, it will eventually disconnect and I can not reconnect until I reboot. I always get the same timeout failure.
This seems to only occur when I am using a VPN or VirtualBox (E.g.: Windows 7 VM from inside Arch). I can still initally use the VPN or VM internet normally with good settings but it will inevitable disconnect. I don't want to conclude that the VPN or VM are related to the cause but I do notice that it will happen fairly quickly (5 minutes to 1 hour).
I may not fully understand how dhcp, resolv.conf and resolvconf.conf are working in relation to each other.
All generate an identical output before and after the fact:
ip addr, ip route, iw list, iw mlan0 info
I have added this to create a static IP:
dhcpcd.conf
# define static profile
profile static_mlan0
static ip_address=192.168.1.11
static routers=192.168.1.1
static domain_name_servers=107.170.95.180
# fallback to static profile on mlan0
interface mlan0
fallback static_mlan0
I added the OpenNic DNS servers to resolv.conf:
resolv.conf
# Generated by resolvconf
nameserver 198.100.146.51
nameserver 192.168.1.1
nameserver 107.170.95.180
nameserver 75.127.14.107
Intersetingly, even with 192.168.1.1 there, I do not have the heartbleed, atleast according to IPLeak. Oddly, to me, 107.170.95.180 is never at the top of the list even it is written expressly in the dhcpcp.conf. It is using the manual entry from resolvconf.conf.
resolvconf.conf
name_servers=75.127.14.107
name_servers=107.170.95.180
name_servers=198.100.146.51
Journaling has been off in fstab since creation per SSD r/w issues.
I have been struggling to understand how I can fix this issue for over a month and a half. Any help would be appreciated.
