Posted: Thu Jul 02, 2009 10:28 Post subject: WRT54GL Repeater Bridge DNS problem (LAN clients only)
Configured my WRT54GL to be a Repeater Bridge.
Wireless clients can connect and access internet through RB without issue (I'm posting it from a netbook connected to the RB).
Wired (LAN) clients can connect with static IP only (haven't fixed the DHCP issue yet, haven't tried), but DNS will not resolve. I can access http://209.85.225.147 (Google's IP address), but cannot access http://www.google.com on the same wired (LAN) laptop.
I have tried the fix listed on the Client Mode article under Linking Articles section. No dice.
Any ideas?
I am running DD-WRT v24-sp2 (05/21/09) std-nokaid - build 12188 on a WRT54GL v1.1 router.
Make sure you have a the primary router as the gateway in your RB. If that doesn't work, post a screenshot of your RB basic setup page. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Is your PRIMARY router at 10.1.10.1? That is a strange IP for a primary. Also leave local DNS blank. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
Posted: Fri Jul 03, 2009 1:25 Post subject: Re: WRT54GL Repeater Bridge DNS problem (LAN clients only)
smiley505 wrote:
Wired (LAN) clients can connect with static IP only (haven't fixed the DHCP issue yet, haven't tried), but DNS will not resolve. I can access http://209.85.225.147 (Google's IP address), but cannot access http://www.google.com on the same wired (LAN) laptop.
Did you set your DNS server(s) in the static IP config of your hosts and if so then what address(es) did you use? _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
My next question was going to be what was set for dns on the primary router. (I think that is was Phuzi0n asked, but he talks over my head all the time ). Check out the wiki on openDNS. _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
(I think that is was Phuzi0n asked, but he talks over my head all the time )
Since the hosts are using static configs it doesn't matter what the router has configured because the hosts are going to use their own settings. If they don't have any DNS set then they won't be able to resolve any domains. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
What do you get when you run nslookup google.com from one of the hosts? Could you post a small pic of your ip settings. _________________ Read the forum announcements thoroughly! Be cautious if you're inexperienced.
Available for paid consulting. (Don't PM about complicated setups otherwise)
Looking for bricks and spare routers to expand my collection. (not interested in G spec models)
(I think that is was Phuzi0n asked, but he talks over my head all the time )
Since the hosts are using static configs it doesn't matter what the router has configured because the hosts are going to use their own settings. If they don't have any DNS set then they won't be able to resolve any domains.
Look....he did it again.
Did you set the primary router to open dns, or the bridged router. I meant set the primary router...the one at 10.1.10.1. (You might not be able to do that if it is a building wide system.) Perhaps describe the setup behind your router. Any other routers/switches besides the one at 10.1.10.1? Perhaps you are setting the gateway to what is actually another bridged router....? _________________ SIG:
I'm trying to teach you to fish, not give you a fish. If you just want a fish, wait for a fisherman who hands them out. I'm more of a fishing instructor.
LOM: "If you show that you have not bothered to read the forum announcements or to follow the advices in them then the level of help available for you will drop substantially, also known as Murrkf's law.."
If you router uses 10.0.1.1 as the defualt login address then I would advice you to port forward it some other ip. You can read here how to port forward 10.0.1.1
). Check out the wiki on openDNS.
Since the hosts are using static configs it doesn't matter what the router has configured because the hosts are going to use their own settings. If they don't have any DNS set then they won't be able to resolve any domains.