Screen Shots of Debian Install / Slackware Help

[UNLTuba]

OK. Here's what I've decided to do. I decided to do a fairly compact install of Slackware so that I could use the graphical nature of the comman-line shell in order to take screen shots of the Debian install process while in Slackware. I figure I can get captures of the shell window easier than I could ever do during the test-based install of Debian. Does that make sense? Hopefully it'll work.

Anyway - I got Slackware installed fairly quickly (MUCH easier now that I had gone through Debian's process), however I am having troubles connecting to the internet. I swear that I entered the network settings correctly, but no matter what I do I can't connect (even though I could in Debian). Is there an auto-detect package for Slackware similar to the auto-detect of internet settings during Debian's install process? I connect straight to the internet, so it isn't like there's a firewall problem somewhere or something. Is there anything else I can try other than netconfig while logged in as root in Slackware? Thanks for your help in advance...

Another oh yeah... Back to class today. I knew Spring Break wouldn't last forever.

 

[drag]

Slack's got a netconfig utility that'll help configure everything for you, but my luck with it isn't so hot either....

However if you want to make sure that everything works before configuring it perminately you can use the manual-type controls:

ifconfig --in linux if you just type this command it'll display the state of the network interfaces...
you should have at least a lo device for loopback.. a eth0 if you have 1 ethernet card working... ppp0 for dial-out connections

ping -of course ping..

route -establishes the routing tables...

dhclient - for using dhcp to configure every thing.

Now I probably won't worry about dhcp right now, well since I realy don't remember how set it up manually off the top of my head.
I'll assume that 192.168.0.1 on network 192.168.0.0 with the dns and gateway both 192.168.0.254
ok do "ifconfig"
do you have the eth0 there? Does it have the correct/valid address? if not
iconfig eth0 192.168.0.15/24 up
if that doesn't work not you'll have to find the correct modules or whatnot and set them up.
(the /24 part is optional and is for the netmask... )if you know what netmasks are, it refers to 11111111.11111111.11111111.00000000 in binary or 255.255.255.0 in normal terms... more /28 means 28 1's and 4 zeros
11111111.11111111.11111111.11110000 or 255.255.255.240, if that all makes sense... 255.255.255.0

ok then it is time to check your route configuration
try just typing "route"
you should have at least localnet and loopback setup, and hopefully the gateway is there, too, labled "default" more than likely. If you only have the 2 loops then try:

route add default gw 192.168.0.254

and that should be enough for your computer's routing tables... then check out your
/etc/resolv.conf and make sure your dns server is in there if not add:

nameserver 192.168.0.254

or whatever your dns server is, you can have more than one and it's a good idea to set it up even if you use dhcp.. ok now that we have you ipaddress, dns address, and gateway set up then we test with ping to make sure everything works

ping 127.0.0.1
this is to test your own computers ability to network, if this doesn't work then you got bad problems...
ping 192.168.0.15
similar to above, it makes sure that your computer can use it's can use it's own settings
ping 192.168.0.254
pings the nameserver/router/gateway, if you can't reach this then either your settings are not correct or your router is not working properly...
then
ping your.dns.stuff,
but in this pretend howto, I assumed your DNS server is the same as your router, but if is seperate you want to make sure you can reach it.
ping 216.239.57.99
if this works then you are at least able to get to the internet, this is google's address, if not then the trouble is the gateway, or your computers ability to use the gateway...
ping www.google.com
if this doesn't work then something is wrong with either your networking software or the DNS server is not working, if your router is the dns server, too then make sure it's set up right, too. But then if another computer/OS works with it then it is probably not the router's fault.

And if it does then your on the internet, congrats! if something like your brorwser doesn't work, then it's probably your browser fault, unless of course you have a firewall installed on your computer and that may be screwed up.

this is about the best way of making sure Unix boxes networking works. It also works for Windows boxes, too. Of course the commands are different, but the concept is the same. hope it helps