Slackware 12.2 network connection issue

fyr3 · 03-14-2009, 09:05 PM

Hi all i just recently installed slackware 12.2 on my freshly dual booted computer. Ive got a trendnet nic and KDE as my default Window Manager. So the issue i have is when i start slackware dhcp times out on connection and also says dhcpcd not started. Ive been trying ifconfig up, ./rc.inet1 restart(start) etc for about 3 hours now. Ive fiddled with my resolv.conf and it has my comcast DNS servers listed automatically from my router.
*also ive tried alternating settings of gateway, forcing the resolv to not be updated, and dns hostname combinations

Now.. the problem is i just got frustrated and started KDE, went to the network manager, hit enable at eth0 and bam its active with dhcp and everything. This doesnt really help me that much because i dont want to use the window manager practically at all, and for startup the connection still doesnt work. So when i start the connection using the network manager, then type ifconfig eth0 down, then ifconfig eth0 up it doesnt even start back up correctly. Im mainly building this computer for some server experience so i want to avoid window managers at all cost until i know how to do things without them. Pretty much what i want to know is what is KDE doing when you select an interface and hit "enable interface" that im not doing in the CLI. Thanks.

Drakeo · 03-14-2009, 09:30 PM

Here you go this is in Slackware 12.2 extra it does it all for you down load instal reboot then click the icon on the bottom right and tell it to connect by wireless or wired.

Quote:

http://slackware.cs.utah.edu/pub/sla...9-noarch-1.tgz

fyr3 · 03-14-2009, 09:48 PM

thanks for the link but this wicd thing helps connections when you startx? If so i can just use the kde network manager to do that, i just want to figure out how to get the connection going without going into X at all.

Slacker_Rex · 03-14-2009, 10:19 PM

From the wicd page:

Code:

Features
   7. wireless networks
         1. automatically connect at boot - no user intervention required, even for encrypted networks
         2. keeps network keys in root accesible only (600) files (unencrypted, however)
         3. automatically selects between static IP addresses and DHCP on a per network basis
         4. encryption (template based)
               1. WPA 1/2
               2. WEP
               3. LEAP
               4. TTLS
               5. EAP
               6. PEAP 
   8. automatically connects at resume from suspend
   9. displays information about the network
  10. support for Ralink cards
  11. ability to run scripts before/after connecting/disconnecting

http://wicd.net/features.php

fyr3 · 03-14-2009, 11:05 PM

oh, i figured it was only during X since drakeo said click the icon in the bottom right. Didnt think there were icons without X, but ill check it out. I just figured it was something not requiring any different software since the enabling of eth0 in KDE used my same configuration files. Ill report back once i fix it.

Drakeo · 03-14-2009, 11:34 PM

If all you wanted to do was connect to the internet at boot with a eth0 lan card was to do this to the /etc/rc.d/rc.inet1.conf

Quote:

# Config information for eth0:
IPADDR[0]=""
NETMASK[0]=""
USE_DHCP[0]="yes"
DHCP_HOSTNAME[0]=""

this tells the system to ifconfig eth0 up and do a dhcpcd. at boot good luck.
My fault I thought you were using different cards like a eth0 and a wlan0 so sorry I confused you.

fyr3 · 03-16-2009, 11:26 AM

Cool thanks for everybodys help, i couldnt get DHCP to work so i just set it to a static ip and BAM connection. Happily on the slackware box atm, thanks every1!