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.
I have a Siemens wired/wireless adsl router/modem SE567.
It has a an ip address of: 192.168.1.254
This unit is hooked up to my telus line and I have a computer wired up to the #1 ethernet jack.
It gets ip 192.168.1.64. It works the internet.
I also have a cat5 cable from #4 ethernet jack which has "WAN" marked on it out to the dining room router
It is a Dlink wired/wireless router.
It has an ip address of 192.168.0.1.
I have a computer in the dining room hooked to the this Dlink unit by cat 5 and I get an ip from the dns on this Dlink. It shows as 192.168.0.100.
I do not get the internet from the dining room computer.
I use the dining room computer and look at the routers web page and it shows that it also cannot get an ip from the dns of the Siemens router.
I wonder if I have to change the Dlink ip to one matching the Siemens router to make things work.
I can do that as it allows me to change the ip of the Dlink so I could make it something like 192.168.1.100 or so. Would that work or do you have any other suggested fixes for me.
The reason for trying to use a second wireless router is I have a laptop in the living room that can't get an rf signal from the Siemens router because the furnace and other items of steel are right in the sigs line of site.
After having that nifty reply to my query I have decided to stop using LinuxQuestions.org.
The replier to my query was very sure I had not searched around for help before I posted.
I have been around Linux for much longer than most and I have always searched for answers to my problems before I posted.
So I will stay away from your site from now on.
There's no need to get insulted in my opinion. You have to realize that we get a lot of questions here from people who are looking for a 'copy paste' answer.
I believe that your problem is related to the fact that both routers, the Siemens and the Dlink are set up as router. You'll just have to change the Dlink to function only as an access point and get it's IP from the Siemens. I believe the Dlink router should be connected to a regular LAN port and not as indicated on a WAN port.
If I'm correct in doing that the Dlink will get a regular IP just as any other connected device from the Siemens router. If the setup of the Dlink has been changed to Access Point only, then all wireless traffic will automatically be routed through the Siemens? The Dlink will only function as a DHCP server and gateway to the Siemens router.
Post the type of your Dlink please in order to check if it has this possibility, but I believe it will.
After having that nifty reply to my query I have decided to stop using LinuxQuestions.org.
The replier to my query was very sure I had not searched around for help before I posted.
I have been around Linux for much longer than most and I have always searched for answers to my problems before I posted.
So I will stay away from your site from now on.
If you decide to check that thread again later, send me PM. I will explain how to organise your network.
After having that nifty reply to my query I have decided to stop using LinuxQuestions.org.
The replier to my query was very sure I had not searched around for help before I posted.
I have been around Linux for much longer than most and I have always searched for answers to my problems before I posted.
So I will stay away from your site from now on.
Even if the replier as insulted you (witch IMHO I don't believe he did), your answer is a very immature one.
It's totally immature to judge a community with more than 500000 members by the answers of one member.
Let me give you a small piece of advice, if I may. Grow up.
It is possible to have two DHCP NAT routers in series. The LAN ports for each need to use different network IPs which yours do. 192.168.1.0 and 192.168.0.0. Make sure that you are using a netmask of 255.255.255.0. You could try assigning the second router's WAN port with a fixed IP address. Usually a router's DHCP server assigns IP addresses within a certain range. You could assign the second routers WAN port to a static IP address outside the first router's DHCP IP range. Next copy the ISP's DNS settings from the first router to the second. The second router's DHCP server will now issue the same DNS entries to it's client. Set the default gateway of the second router to the IP address of the first router.
It has been a long time since it was necessary to use a cross over cable to connect two routers. Auto-negotiation takes care of that, but I have seen devices where it doesn't work as advertised. ( such as some of our switches at work )
With the routers configured, check that your hosts have both IP addresses assigned and DNS settings. If you are using Linux try the command "getent hosts www.google.com". It will return the IP addresses for both local hosts (from the /etc/hosts file) and internet hosts from your ISPs DNS servers. Check that your hosts have your ISPs DNS settings. Some routers use the router's IP address instead, and this may not be working. You could have a problem where a DNS search isn't makeing it's way back to the ISPs dns server.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.