Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
root@erdos:~# iptables -nvL
Chain INPUT (policy ACCEPT 165 packets, 11636 bytes)
pkts bytes target prot opt in out source destination
Chain FORWARD (policy ACCEPT 0 packets, 0 bytes)
pkts bytes target prot opt in out source destination
0 0 ACCEPT all -- eth1 * 10.0.2.0/24 0.0.0.0/0
Chain OUTPUT (policy ACCEPT 172 packets, 18544 bytes)
pkts bytes target prot opt in out source destination
root@erdos:~#
From linux router to router:
root@erdos:~# ping 10.0.1.1
PING 10.0.1.1 (10.0.1.1) 56(84) bytes of data.
64 bytes from 10.0.1.1: icmp_seq=1 ttl=64 time=0.324 ms
64 bytes from 10.0.1.1: icmp_seq=2 ttl=64 time=0.305 ms
64 bytes from 10.0.1.1: icmp_seq=3 ttl=64 time=0.294 ms
Pinging 10.0.2.1 with 32 bytes of data:
Reply from 10.0.2.1: bytes=32 time<1ms TTL=64
Reply from 10.0.2.1: bytes=32 time<1ms TTL=64
Reply from 10.0.2.1: bytes=32 time<1ms TTL=64
Reply from 10.0.2.1: bytes=32 time<1ms TTL=64
Ping statistics for 10.0.2.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
C:\Users\orion>
From the PC to linux router eth0:
C:\Users\orion>ping 10.0.1.4
Pinging 10.0.1.4 with 32 bytes of data:
Reply from 10.0.1.4: bytes=32 time<1ms TTL=64
Reply from 10.0.1.4: bytes=32 time<1ms TTL=64
Reply from 10.0.1.4: bytes=32 time<1ms TTL=64
Reply from 10.0.1.4: bytes=32 time<1ms TTL=64
Ping statistics for 10.0.1.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms
how do you connect to this forum exactly? do you have another internet connection or something?
just try open your browser && go surfing via your linux router - or - nslookup something.domain --> if it find the address then there should be no problem for you connect to the internet.
I'm connecting to this forum via router: mypc=>router(not linux router)=>internet
C:\Users\orion>nslookup www.linuxquestions.org
DNS request timed out.
timeout was 2 seconds.
Server: UnKnown
Address: 62.80.244.2
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
Maybe my DHCP configuration on the linux router is incorrect ?
/etc/dhcpd.conf
ddns-updates on;
ddns-update-style ad-hoc;
option domain-name-servers 10.0.1.1;
option subnet-mask 255.255.255.0;
option routers 10.0.2.1;
# Local LAN
subnet 10.0.2.0 netmask 255.255.255.0 {
ddns-updates on;
range 10.0.2.3 10.0.2.150;
}
Look at the line "option domain-name-servers 10.0.1.1;" I've just changed the IP address of real DNS server to router's IP, but still can't connect to the net.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.