- Jan 28, 2014
- 7
- 0
- 10,510
I run an Ubuntu Server behind an Asus Router (http://www.asus.com/us/Networking/RTAC68R/specifications/). Wireless works perfectly, and Router can ping the Server, but the Server cannot ping the Router, but the Router can ping itself.
From what I've read, I think it may be that the Router's dhcp server conflicts with the Router's dhcp server (but, I know nothing, so this is only my guess).
I believe what I want to do is to run the Server behind the Router (as it is now), but to limit the Router's dhcp server to a different subnet, or at least have it serve to a different range of IP ad-dresses in the same subnet. Although, I have seen others come to various conclusions including (1) put Server's ip into the DMZ of the Router, or (2) simply turn off the Router DHCP server.
Although I do find the latter option tempting, I am not entirely sure that I haven't already ruined the Server's dhcp settings to the extent that my roommates would go nuts if the internet was down while I tried to reconfigure the Server's dhcp settings.
Here are the contents of various relevant files:
1) route –n:
2) ifconfig:
3) ping 8.8.8.8:
4) Contents of /var/lib/dhcp/dhcp.leases:
5) Contents of "cat /var/lib/dhcp/dhclient.eth1.leases"
6) Contents of "/etc/hosts/":
From what I've read, I think it may be that the Router's dhcp server conflicts with the Router's dhcp server (but, I know nothing, so this is only my guess).
I believe what I want to do is to run the Server behind the Router (as it is now), but to limit the Router's dhcp server to a different subnet, or at least have it serve to a different range of IP ad-dresses in the same subnet. Although, I have seen others come to various conclusions including (1) put Server's ip into the DMZ of the Router, or (2) simply turn off the Router DHCP server.
Although I do find the latter option tempting, I am not entirely sure that I haven't already ruined the Server's dhcp settings to the extent that my roommates would go nuts if the internet was down while I tried to reconfigure the Server's dhcp settings.
Here are the contents of various relevant files:
1) route –n:
Code:
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 192.168.1.1 0.0.0.0 UG 100 0 0 eth1
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth12) ifconfig:
Code:
Eth1
Link encap:Ethernet HWaddr 00:25:90:d4:e9:38
Inet addrr: 192.168.1.2 Bcast: 192.168.1.2555 Mask: 255.255.255.0
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
Collissions:0 txqueuelen:1000
RX bytes:0 (0.0B) TX byes:0 (0.0B)
Interrupt:16 Memory:df900000-920000
lo
Link encap:Local Loopback
Inet addrr: 127.0.0.1 Mask: 255.0.0.0
Inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:65536 Metric:1
RX packets:324968 errors:0 dropped:0 overruns:0 frame:0
TX packets:322968 errors:0 dropped:0 overruns:0 carrier:0
collissions:0 txqueuelen:1000
RX bytes:55193168 (55.1MB) TX byes:55193168 (55.1MB)
Code:
PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data
From 192.168.1.2 icmp_seq_1 Destination Host Unreachable
From 192.168.1.2 icmp_seq_1 Destination Host Unreachable
…
Code:
var/lib/dhcp/dhcp.leases/dhclient.leases
var/lib/dhcp/dhcp.leases/dch/dhclient.eth1.leases
Code:
lease {
interface "eth1";
fixed-address 192.168.1.2;
option subnet-mask 255.255.255.0;
option routers 192.168.1.1;
option dhcp-lease-time 86400;
option dhcp-message-type 5;
option domain-name-servers 192.168.1.1;
option dhcp-server-identifier 192.168.1.1;
renew 5 2014/09/12 03:03:47;
rebind 5 2014/09/12 03:03:47;
expire 5 2014/09/12 03:03:47;
}
Code:
127.0.0.1 localhost
Facebook
Twitter
Instagram