Unfortunately no one can be told what fun_plug is - you have to see it for yourself.
You are not logged in.
Hi,
I recently purchased a DNS-323, am using fonz's fun_plug on FW 1.06 and generally think this is a fine combination of hardware and software. But quite often there is a problem with connecting to a nameserver. Nothing works, not ping, not nslookup, not torrents.
Trying for example google nslookup, I get only the following output:
root@dlink-EC67A4:~# nslookup www.google.com
Server: 193.229.0.40
In the Admin Web GUI - LAN settings I have the DCHP Client option enabled. The device automatically acquires the following name servers: 193.229.0.40 and 193.229.0.42, which interestingly are NOT the same nameservers my own computer acquires despite being connected to the Internet via the same service provider/ADSL modem/hub.
When I click Save settings (without changing any settings), nslookup (and nameserver queries in general, I think) work normally FOR A WHILE (let’s say for half an hour):
root@dlink-EC67A4:~# nslookup www.google.com
Server: 193.229.0.40
Address 1: 193.229.0.40 resolver1.kolumbus.fi
Name: www.google.com
Address 1: 74.125.39.104 fx-in-f104.google.com
Address 2: 74.125.39.105 fx-in-f105.google.com
Address 3: 74.125.39.106 fx-in-f106.google.com
Address 4: 74.125.39.147 fx-in-f147.google.com
Address 5: 74.125.39.99 fx-in-f99.google.com
Address 6: 74.125.39.103 fx-in-f103.google.com
I don’t know what else to add, except to mention that my /ffp/etc/resolv.conf is empty. Can you help a linux/DNS323 noob figure this out? Thanks in advance.
Offline
zpd wrote:
/ffp/etc/resolv.conf is empty
Look at /etc/resolv.conf, instead. You may also want to try to configure a fixed IP address and fixed nameservers to see if that's stable.
Offline
/etc/resolv.conf reads:
nameserver 193.229.0.40
nameserver 193.229.0.42
Thanks for the hints, I'll get back to you when I've experimented with what you suggested :-)
Offline
I find I misjudged the problem. It isn't that during these lapses the device cannot connect to nameservers - it is that it apparently cannot connect to the Internet at all! I tried pinging IP addresses that my desktop computer no trouble reaching, and got nothing on the dns323. The desktop uses the same ADSL box / hub.
Local access through the LAN is unaffected during the lapses. As previously stated, hitting Save settings cures the problem for a while.
Offline