Random sex chat c2c free webcam chat - Linux dhcp client not updating dns

After that I opened /etc/and saw that the nameserver ips were not updated accordingly.

These IPs were the ones which are configured through DHCP by the ISP & they can't be accessed by the outside internet.

linux dhcp client not updating dns-9linux dhcp client not updating dns-20

updating windows without internet - Linux dhcp client not updating dns

TECH142841 and as soon as I ran $sudo route add -host 1.2.3.4 dev eth0 , my VPN connection started saying host unreachable. Enabling the following (serverside) is needed for starters, because it'll basically tell your client to route all traffic through the vpn tunnel (changing the default route which is not being done now). Normally the MASQUERADE should do the job just fine in this case; but just for the sake of it try using a specific source NAT statement: Do you have the possibility to do a packet capture on the external interface of the server to check if there are any related packets leaving (verify if they're getting source natted correctly etc)?

Enabling the following (serverside) is needed for starters, because it'll basically tell your client to route all traffic through the vpn tunnel (changing the default route which is not being done now)[email protected] ~ $ ip route 0.0.0.0/1 via 10.8.0.5 dev tun0 default via 123.237.128.1 dev eth0 10.8.0.1 via 10.8.0.5 dev tun0 10.8.0.5 dev tun0 proto kernel scope link src 10.8.0.6 123.237.128.0/21 dev eth0 proto kernel scope link src 123.237.128.173 128.0.0.0/1 via 10.8.0.5 dev tun0 1.2.3.4 via 123.237.128.1 dev eth0 [email protected] ~ $ [email protected] ~ $ sudo route -n Password: Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 10.8.0.5 128.0.0.0 UG 0 0 0 tun0 0.0.0.0 123.237.128.1 0.0.0.0 UG 0 0 0 eth0 10.8.0.1 10.8.0.5 255.255.255.255 UGH 0 0 0 tun0 10.8.0.5 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 123.237.128.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0 128.0.0.0 10.8.0.5 128.0.0.0 UG 0 0 0 tun0 1.2.3.4 123.237.128.1 255.255.255.255 UGH 0 0 0 eth0 [email protected] ~ $ But, I can't still do $curl --interface tun0 checkip. Normally the MASQUERADE should do the job just fine in this case; but just for the sake of it try using a specific source NAT statement: So, the actual reason for not able to open a website on the client was that the DNS was not set properly.

I debugged this after I pinged 8.8.8.8 and I was able to ping it successfully.

When I try to connect to the server, everything gets completed successfully.

The server's tun0 gets the ip address 10.8.0.1 & client's tun0 gets the ip address 10.8.0.6. My ISP's connection gets the address something like 123.*.

What is it that I need to route all my traffic through VPN?

I also tried doing Fri Jun 8 2012 [aws_ec2] Peer Connection Initiated with 1.2.3.94 Fri Jun 8 2012 SENT CONTROL [aws_ec2]: ' PUSH_REQUEST' (status=1) Fri Jun 8 2012 PUSH: Received control message: ' PUSH_REPLY,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5' Fri Jun 8 2012 OPTIONS IMPORT: timers and/or timeouts modified Fri Jun 8 2012 OPTIONS IMPORT: --ifconfig/up options modified Fri Jun 8 2012 OPTIONS IMPORT: route options modified Fri Jun 8 2012 ROUTE default_gateway=123.237.128.1 Fri Jun 8 2012 TUN/TAP device tun0 opened Fri Jun 8 2012 TUN/TAP TX queue length set to 100 Fri Jun 8 2012 /usr/sbin/ip link set dev tun0 up mtu 1500 Fri Jun 8 2012 /usr/sbin/ip addr add dev tun0 local 10.8.0.6 peer 10.8.0.5 Fri Jun 8 2012 /usr/sbin/ip route add 10.8.0.1/32 via 10.8.0.5 Fri Jun 8 2012 Initialization Sequence Completed macbookpro/123.237.129.2931 Fri Jun 8 2012 macbookpro/123.237.129.2931 MULTI: primary virtual IP for macbookpro/123.237.129.2931: 10.8.0.6 Fri Jun 8 2012 macbookpro/123.237.129.2931 PUSH: Received control message: ' PUSH_REQUEST' Fri Jun 8 2012 macbookpro/123.237.129.2931 SENT CONTROL [macbookpro]: ' PUSH_REPLY,route 10.8.0.1,topology net30,ping 10,ping-restart 120,ifconfig 10.8.0.6 10.8.0.5' (status=1)[email protected] ~ $ route -n Kernel IP routing table Destination Gateway Genmask Flags Metric Ref Use Iface 0.0.0.0 123.237.128.1 0.0.0.0 UG 0 0 0 eth0 10.8.0.1 10.8.0.5 255.255.255.255 UGH 0 0 0 tun0 10.8.0.5 0.0.0.0 255.255.255.255 UH 0 0 0 tun0 123.237.128.0 0.0.0.0 255.255.248.0 U 0 0 0 eth0 [email protected] ~port 1194 proto udp dev tun ca /etc/openvpn/cert /etc/openvpn/aws_ec2key /etc/openvpn/aws_ec2# This file should be kept secret dh /etc/openvpn/dh2048server 10.8.0.0 255.255.255.0 ifconfig-pool-persist keepalive 10 120 tls-auth /etc/openvpn/0 comp-lzo persist-key persist-tun status verb 3client dev tun proto udp remote ec21194 resolv-retry infinite nobind persist-key persist-tun ca /etc/openvpn/cert /etc/openvpn/key /etc/openvpn/ns-cert-type server tls-auth /etc/openvpn/1 comp-lzo verb 3 Okay, that's not really indicated on the wiki.

Basically, when the connection arrives on your openvpn server, it doesn't now what to do because it's not the destination IP.

What you need is a firewall such as shorewall to configure routing.

It's not a problem concerning your VPN, you just need to set up masquerading between you VPN interface (tun0) and internet interface (eth0 ? [[email protected] shadyabhi]# iptables -L -t nat -n Chain PREROUTING (policy ACCEPT) target prot opt source destination Chain INPUT (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain POSTROUTING (policy ACCEPT) target prot opt source destination MASQUERADE all -- 10.8.0.0/24 0.0.0.0/0 [[email protected] shadyabhi]# [[email protected] shadyabhi]# ip route default via 123.237.128.1 dev eth0 proto static 123.237.128.0/21 dev eth0 proto kernel scope link src 123.237.128.173 [[email protected] shadyabhi]# ip route default via 123.237.128.1 dev eth0 proto static 10.8.0.1 via 10.8.0.5 dev tun0 10.8.0.5 dev tun0 proto kernel scope link src 10.8.0.6 123.237.128.0/21 dev eth0 proto kernel scope link src 123.237.128.173 [[email protected] shadyabhi]# I am still getting timeout when I do $curl --interface tun0 checkip.on the client.

On the server, doing $curl --interface tun0 checkip.works just fine. The only improvement now is that the VPN connection from the client is not broken due to the "1.2.3.4 123.237.128.1 255.255.255.255 UGH 0 0 0 eth0" rule.

Comments are closed.