Hi, Im just getting back into linux after a couple years off. My project I have started is an old PIII running slackware 12 with the new kernel. I got wireless installed and working somewhat but I still have some stuff to work out. I have a couple questions, first why is resolv.conf blank? Where do I manually configure the way I used to with resolv.conf? I want to use this computer as a firewall/router that sits right behind my modem then use its wireless card as an access point for all the other computers on the network. Can anyone direct me to a good tutorial on doing this? I dont even know where to start so for now Im just trying to trim my kernel down and get the things I know are wrong fixed. Any help is much appreciated, thanks in advance.

Todd

I do not use wireless but hopefully resolv.conf has contents

nameserver xxx.yyy.x.zzz...replace with numbers
nameserver xxx.yyy.x.zzb

until you fill up all the known primary and secondary ips for your isp.

Have not used slack in years but until a better reply start here pls
http://www.slackware.com/config/network.php

Thanks I will start there.

Is this machine getting it's IP via DHCP. If so, then the default setup on Slack should create the /etc/resolc.conf file with the information provided via DHCP. Unless you've configured the DHCP client specifically not to overwrite it.

Cheers.

I will have three interfaces. Two nics and one wireless card. eth0 will be plugged into my modem and will obtain its ip via dhcp, the second nic will be plugged into a plain jane linksys hub for the computers that need a hard wire. The wireless card will service the other computers through out the house. So Im guessing Ill have to set up a dhcp server on the machine and tie that server to whatever IP I give wlan0. Also I will have to setup nic #2 to gets ip from the local dhcp server. Im really not sure what all I need to do thats why I figured my best bet was to read a decent tutorial. Basicly I want all the traffic going through this machine so I can firewall the whole network how I see fit. Do you see any problems with that approach? Im still trying to get back into the swing of things since I havent touch linux in quite a while.

Edit: Also the reason I want this machine right on the modem is so I can access it from anywhere and run a webserver etc without having to buy a new IP address from the cable company.

I'm not sure how you would tell nic #2 and wlan0 to use "localhost" to resolve an IP. They will always try and broadcast a DHCP request. Why not give them static IPs, on your local subnet, and if you need it, run a DHCP server to support the remainder of the local network.

But the original question was about /etc/resolv.conf. Did you get that resolved. Which then raises another issue. If you are getting the nameservers, from your ISP, via DHCP on nic #1, how are you going to pass that information on to the rest of your internal network, if you go along the DHCP route.

Cheers.

I did manually edit resolv.conf and that fixed alot of the problems I was having. As far as the rest of your question, I dont know. Since you put it that way it does sound kinda retarded. My tinkering in the last couple hours has lead to me to think that static for the internal computers is best like you said. I found some good info here and there but I have a fresh problem that Im going to post on a new thread. Im gonna need a ton of help getting this thing together, no scratch that Im gonna need a ton of help just understanding what I need to do! I know Ive bit off a rather large chunk as a newbie but I love the callenge. I dont mind reading so dont be afraid to send links to docs.