Tiny Core Base > Micro Core
static ip address not resolving names
bmarkus:
What is the ouput of the 'ifconfig' and 'route' commands and what is the IP address of your router?
cannonfodder:
I think I have an idea why I can't get static IP to resolve on the one machine.
Turns out roberts may have hit the nail on the head when he mentioned router settings.
I tried Tiny Core 1.3 on the machine not resolving and the problem persisted. I then tried the same Tiny Core 1.3 CD on another machine already running Tiny Core with a working static IP, used its modified /opt/bootlocal.sh to set static IP and it too COULD ping domain names.
Logically, my static IP problems now look to be unrelated to Tiny Core.
The difference between the setup of the two machines? I have a WDS set up using two Linksys routers. One router runs dd-wrt, the other default Linksys software. The PC with a working static IP is connected to the dd-wrt gateway.
The dd-wrt gateway is dns-masq enabled, the plain Linksys router is not.
If my assumptions are correct and dns-masq is responsible for getting the PC with the working static IP to resolve, I suppose I could look into enabling the same function in my other router.
Thing is, /etc/resolve.conf should be working.
Any further input or suggestions is more than welcome...
cannonfodder:
After a fresh round of troubleshooting, I'm having to rethink some of my conclusions/assumptions.
Router or router configuration aren't the issue:
- The PC running Tiny Core 1.2 or 1.3 with correctly working static IP is a laptop. Whether this laptop is connected to one router or the other, domain names get resolved.
- The PC running Micro Core with incorrectly working static IP has multiple OSes on it. To wit, I have CrunchBang set up with correctly functioning static IP on this machine.
@ bmarkus:
With the laptop and PC side-by-side connected to the same router and with the former working as desired and the latter not, the results of ifconfig and route are identical except for internal IP address.
It would appear, then, to be a problem with configuration.
When I have more time, I'll start up Micro Core with nodhcp base norestore and try to run the eth0.sh script one line at a time to see what happens....
cannonfodder:
Happy to report that this problem has been SOLVED...
Embarrassed about the nature of the problem, however.
I was echoing nameserver info to /etc/resolve.conf and NOT /etc/resolv.conf
Navigation
[0] Message Index
[*] Previous page
Go to full version