WRT54G with local DNS

Linksys / Wrt54g
December 13, 2009 at 08:53:35
Specs: Ubuntu 8.04, 1.8ghz, 512 mb ram
Hey,

I have a local network which is a WRT54G in it's default mode and a 2 consumer switchs connected to the WRT54G to give me 10 wired connections.

I have properly named all of the devices in DHCP and I want to be able to contact the devices using DNS.

Example, my printer is called "david-printer" but it is often off the the IP often changes, that being said I would rather enter "david-printer" as the address for networked printing instead of "192.168.1.142".

Can the Linksys WRT54G do this without using 3rd party firmware? I don't want to use different firmware cause I have version 6 of the router and dd-wrt is highly unstable.

thanks,

David

Why not?


See More: WRT54G with local DNS

Report •

#1
December 13, 2009 at 13:46:40
In my Dlink I have the ability to configure the router to assign a static IP to a specific mac address. Does the Netgear have this facility in it's DHCP configuration interface? If so then your problem is solved. Just assign a static IP to the printer and your networked PCs will not lose track of it.

Goin' Fishin' (Some day)


Report •

#2
December 14, 2009 at 05:08:15
make sure in tcp/ip properties that netbios over tcp/ip is enabled, everyone is in the same workgroup. Master browser will be appointed and compile a list which all will reference even with dynamic ip.

to do it strickly with dns you would need a local lan dynamic dns server.


Report •

#3
December 14, 2009 at 05:40:54
"to do it strictly with dns you would need a local lan dynamic dns server."

I was wondering if the WRT54G ( Linksys ) had this capability.

Why not?


Report •

Related Solutions

#4
December 14, 2009 at 05:43:13
I use tomato firmware on our WRT54GL's at work and it's very stable. I've never tried DDWRT so can't say about it.

I don't know if you can DNS in the router anyhow even if you are using 3'd party firmware. I'm not sure they're capable of it and I'm not at work so can't check if it's offered in tomaro. But you could setup the HOSTS file on all your PC's at home and then use hostnames to contact everything.


Report •

#5
December 14, 2009 at 08:35:17
I just looked at one of the routers I have setup here at work as a wireless access point. They're running the tomato firmware and it does have some DNS capability.

I don't know if the default firmware offers this or not and I'm not sure what's available in tomato will do what you require.


Report •

#6
December 14, 2009 at 08:40:24
If you were using static ip then a hosts file would work fine. Unfortunately with dynamic the ip to name can change making the hosts invalid.

Version of tomato has to support dnsmasq
http://en.wikipedia.org/wiki/Dnsmasq


Report •

#7
December 14, 2009 at 17:30:11
My router is the version 6 router which barely has enough memory to run dd-wrt, so it very often hits out-of-memory conditions.

That's why it is unstable on my router.

Why not?


Report •

#8
December 14, 2009 at 17:31:40
Tomato does not support my router. My trouble with hosts is that it does not connect to DHCP.

Why not?


Report •

#9
December 14, 2009 at 21:31:29
then you need to follow the recommendation in post 2 and not use ip for name resolution but netbios which is built in.

Report •

#10
December 15, 2009 at 05:49:03
Tomato does not support my router.

Want to bet on that?

Take a look at the following link to Tomato firmware and read the very first sentence of the very first paragraph.

Here, I'll make it easy for you:

"Tomato is a small, lean and simple replacement firmware for Linksys' WRT54G/GL/GS, Buffalo WHR-G54S/WHR-HP-G54 and other Broadcom-based routers."

Is that, or is that not your router?


Report •

#11
December 15, 2009 at 17:28:36
Sure let's bet, read the second note in the notes section on the same page.

"Linksys WRT54G v1-v4, WRT54GS v1-v4, WRT54GL v1.x, WRTSL54GS (no USB support) "

Mine is a v6 ;)

Why not?


Report •

#12
December 16, 2009 at 05:46:01
You conveniently skipped a sentence:

Routers that are known to work with Tomato:
Linksys WRT54G v1-v4, WRT54GS v1-v4, WRT54GL v1.x, WRTSL54GS (no USB support)

No where does it say, "known to work with Linksys WRT54G v1-v4 but not any higher versions". That means they (the makers of tomato) have tested it with those versions and likely no other. It doesn't mean they tested it with all versions and only v1-4 worked.

Since you don't seem to have a lot of options, I would try tomato on your router.


Report •

#13
December 19, 2009 at 16:28:17
At the botton of the same box :

"This will not work on Linksys WRT54G/GS v5 or newer WRT54G/GS routers."

I have a v6 router which is never than WRT54G v5 :P

Why not?


Report •

#14
December 20, 2009 at 05:57:18
Bummer, I guess you need to go buy a new one.

Report •

#15
December 28, 2009 at 17:29:39
Yea, I just don't have the money right now. Economic crisis and all, you know ;)

Why not?


Report •

#16
December 28, 2009 at 20:17:44
See what you can trade for it on craigslist. No harm in asking v5 for v6.

Report •

#17
February 8, 2010 at 08:34:15
I got my hands on a WRT54GL router which supports DD-WRT and Tomato. I currently have on my network two linux machines, 1 macintosh and 1 windows machine. I also have several other misc devices such as printers, phones, data etc...

From Linux and Mac, things work perfectly. But from Windows things work badly :

Microsoft Windows XP [version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Propriétaire>nslookup
Serveur par dÚfaut : Lublink
Address: 192.168.70.1

> lublink-archive
Serveur : Lublink
Address: 192.168.70.1

Nom : lublink-archive
Address: 192.168.70.120

> exit

C:\Documents and Settings\Propriétaire>ping lublink-archive
La requête Ping n'a pas pu trouver l'hôte lublink-archive. Vérifiez le nom et es
sayez à nouveau.

Translations :

Serveur par dÚfaut = Default serveur, but Windows XP screwed up on the accent
La requête Ping n'a pas pu trouver l'hôte lublink-archive. = Ping could not find the host lublink-archive
Vérifiez le nom et essayez à nouveau. = "Check the name and try again".

Does Windows require a special setting to work with DNS ? Perhaps it is expecting a FQDN ? Like lublink-archive.somedomainname.net ?

Any idea what I am missing to get Windows to work as well as Linux and Mac ?

Thanks,

David

I remember when Windows used to be easier than Linux, Ubuntu certainly changed that


Report •

#18
February 8, 2010 at 08:38:30
in a xp box's tcp/ip properties what it is it pointing to for dns?

Report •

#19
February 8, 2010 at 08:41:42
Open a command prompt window on the Windows box (Start >> Run >> type "cmd" and hit Enter) and run the following command:

ipconfig /all

Now open a terminal window on a working linux box and do an ifconfig

Compare settings. All TCP/IP settings should be identical with the exception of the actual IP itself. The IP should be in the same subnet as the rest but still be unique.

It sounds to me like you may be having a DNS issue.

Are you able to ping other client computers on the LAN?


Report •

#20
February 8, 2010 at 11:45:33
Microsoft Windows XP [version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Propriétaire>ipconfig /all

Configuration IP de Windows

Nom de l'hôte . . . . . . . . . . : david-xp
Suffixe DNS principal . . . . . . :
Type de noud . . . . . . . . . . : Pair-Pair
Routage IP activé . . . . . . . . : Non
Proxy WINS activé . . . . . . . . : Non

Carte Ethernet Local:

Suffixe DNS propre à la connexion :
Description . . . . . . . . . . . : Intel(R) PRO/1000 MT Network Connect
ion
Adresse physique . . . . . . . . .: 00-0B-DB-58-B1-23
DHCP activé. . . . . . . . . . . : Oui
Configuration automatique activée . . . . : Oui
Adresse IP. . . . . . . . . . . . : 192.168.70.140
Masque de sous-réseau . . . . . . : 255.255.255.0
Passerelle par défaut . . . . . . : 192.168.70.1
Serveur DHCP. . . . . . . . . . . : 192.168.70.1
Serveurs DNS . . . . . . . . . . : 192.168.70.1
Bail obtenu . . . . . . . . . . . : 8 février 2010 07:30:48
Bail expirant . . . . . . . . . . : 9 février 2010 07:30:48

C:\Documents and Settings\Propriétaire>

The DNS server is pointing to the correct location.

If only Windows was as easy as Linux.


Report •

#21
February 8, 2010 at 13:27:38
If 192.168.70.1 is your router then the XP box should be working.

How do the TCP/IP settings on the working linux box compare? Are they all identical except for the actual IP address? If not, show us which ones differ. Better yet, just post the output of an ifconfig from a working linux box and we can compare to the above output from the XP box.


Report •

#22
February 16, 2010 at 11:10:39
Windows seems to want a DNS suffix to work. So I set "example.net" in the DHCP server, so the ipconfig /all now reads :

Suffixe DNS propre à la connexion : example.net

I can now type "david-printer" in my address bar.

David

If only Windows was as easy as Linux.


Report •

#23
February 16, 2010 at 11:45:47
I want to be able to reach my router by typing "router" instead of "192.168.70.1". How do I get the router to be included in the DNS file ?

Thanks,

David

If only Windows was as easy as Linux.


Report •

#24
February 16, 2010 at 13:32:23
You don't since you have no dns server. You put that in a hosts file on your local pc.

Report •

Ask Question