you have to watch sending pics because with firmware changes come new and different screens

I thought maybe that's why around the web, and moses's screenshots of the fowarding tab looked different. I just wasn't too sure.

Thanks

In a browser, or just CLI?

I can get in via CLI as well, but browser just recycles and cycles.

I just plugged through my /etc/proftpd.conf file and it defintely looks normal, I don't see anything in there that would make it not work in a browser (I don't require a valid shell). But this would be another problem, seperate from the server issue it would seem.

Thank you all again

Cool

Are you allowing anonymous ftp?

Yes, AFAIK I am, I can connect via anonymous in CLI.

From IE6 on my win2k box.

BTW- Thanks for the Tori Amos mp3

ha ha ha, No problem

Well I will work that out, I think I can figure out conf file things ok, so I will work on what the deal is there.

Hi everybody, sadly I just went down for a reboot to swap out my cdrom drive, and when I came back up the network didn't connect...

I had to go back into my router change it to work as a DHCP server again, edit /etc/rc.d/rc.inet1 to use DHCP again, and now am back up. I then, just as before, went back to rc.inet1 switched it from using dhcp and reran the script, and it worked, again. So I am at a loss, yet again. Each subsequent reboot proves fruitless. I cannot reboot in "static" IP mode and get the network working, but if I boot up in DHCP mode, get it working, and the rerun the script to set it up as static, it's fine.

Anyone got any more ideas?

Thanks

I know I could get around the problem by less frequent reboots (which would be fine, I'm not a huge rebooter) but I'd rather figure out how to make it work, always, whether I reboot or not, and in slackware.

Thanks

Do you see any errors either in the boot screen, dmesg, or
/var/log/message (or syslog)?
What are your settings on the Filter section of the Advanced menu
on the router? what are your settings under the Dynamic Routing
section?
I get errors when attempting to read the above PNGs. . .

I don't see errors during boot or by browsing dmesg /var/log/messages or syslog.

Here is what I see in dmesg and /var/log/messages when I have it setup not to use DHCP on bootup:
Yeah, I appologize for using a "not so easy to use" pic host. If you copy the URL for the pics above, and enter them into a browser, then hit enter or refresh several times, they will come up.

As for settings, I've got Gateway selected, and Tx/Rx are both disabled.

Thanks for helpin me out on this, again

Cool

Hmm. . .
I got those images to work, and nothing looks terribly wrong to
me. I have TX and RX both set at Rip2 and it seems to work fine.
I've got the security (AOL crap) turned off, I've got a DMZ host
that works, I'm not forwarding or filtering any ports. I'm really just
using it as a kind of dumb router with no security built in, I do all
my security on the individual boxen. My home machines are
not terribly secure, but they're not on all the time either. I'll
probably be cracked by some joker now. . . ;)

Try setting all the DNS stuff in your DHCP section to 0s. I'm not
using that, and everything resolves just fine. I think the router
is smart enough to send the information from its DHCP server
(your ISP) on to its clients. (or maybe I cheat, see below)

Also, if you assert what your server's IP address is, the router
will respect that, as long as it hasn't given away the IP to
someone else. I solve this by setting the starting IP to be 20,
and then for the hosts that need to have a static IP, I set it to be
something less than 20 (192.168.0.2-19). For other hosts, I set
them up with DHCP. It works. For a host with a static IP, I have
the DNS information stored in /etc/resolv.conf

Thanks Moses. I tried removing the DNS entries in the DHCP tab, didn't change anything at all. Still go down for a reboot and when I came back up, same old thing. I have to:
edit /etc/rc.d/rc.inet1
Uncomment the "use DHCP=yes" line
run /etc/rc.d/rc.inet1
Edit /etc/rc.d/rc.inet1
Comment the "use DHCP=yes" line
run /etc/rc.d/rc.inet1
And it works. It sets my server IP to what I want it at (192.168.1.50) and connects me to the internet.

The other option I have here is before I go down for a reboot edit /etc/rc.d/rc.inet1 and uncomment DHCP=yes and then after the reboot I'm online, but then from using DHCP my IP for my server is jacked up (usually assigned 192.168.1.101 since I start my DHCP assigning at 100 as to not interfere with my static IP pool). So then I am back at editing the /etc/rc.d.rc.inet1 and running it again to assign my proper IP.

I thought maybe it had something to do with the "route" but I don't even know where to start on that. I looked at it, and it appears no different to me whether I startup with DHCP enabled or not.

Sorry Moses that I suck this bad, I thank you very much for continuing to help me on this

I have got my new server box on the network now (well not really...) but cannot get that to even be able to ping the router's IP. I really don't want this to sound like a new question as it's not (If I can't figure it out, I'll post it up as another new question... I'm sure full of questions lately ), I am just telling you in case that will help during the troubleshooting.

Thanks again for following me this far.

Cool

"netstat -r" or "route" will show your default gateway, for all machines on your 192.whatever network this should be the router's IP that starts with 192.

Then you need DNS servers set up, this is probably fine under DHCP and probably chokes when you assign a manual IP since you don't define it, I think you can cat /etc/resolv.conf or maybe it will be /etc/dhcpc/resolv.conf when using DHCP.

Also, Slack has all net settings for your ethernet card stored in /etc/rc.d/rc.inet1 which is overly well documented so that just reading it will let you know what to change.

If your having problems getting your machine up with the static IP, do these pings and post what works, doesn't work, or gives errors as it may help pin down what still doesn't work. Heck at this point, I'm not really sure...what exactly is it that still isn't working?

ping 192.168.0.1
ping 213.130.63.234
ping www.slackware.com

PS do a traceroute www.linuxquestions.com or any site and you will notice that the second "hop" is your router's external IP, your IP update program uses something akin to grepping this info out, that's how it gets your IP address

After a reboot, if I'm assigning the Static IP, I cannot connect to the internet. If I use DHCP to configure the internet, I can get on. At that point, I can then adjust my IP the static one I want my machine to have.... Until I reboot, and then starts the viscious cycle over again.

I am going down right now to give those ideas a try, thank you for your reply and I will let you know how things go.

Cool