LinuxQuestions.org
Download your favorite Linux distribution at LQ ISO.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 06-01-2008, 09:00 PM   #16
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,145
Blog Entries: 28

Rep: Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373

Hi,

Why do you need both eth0 & eth1? I would work to get one functional then the other. Your IP assignment is the same for both devices. Why?

You were suggested to look at the '/etc/udev/rules.d/70-persistent-net.rules', did you? if so post them unedited. Is there a reason for masking the IPs'? We're not going to hack you and if the class is '192.168.xxx.xxx' you surely have some protection anyway. Paranoia is good but when trouble shooting a problem at this level the minute mistake can mean everything to get it solved.

You can edit the '/etc/rc.d/rc.inet1.conf' to suit your needs. You don't have to run 'netconfig' multiple times. You don't have to reboot, this is not M$. To restart the inet; '/etc/rc.d/rc.inet1 restart' You can do this after editing the '/etc/rc.d/rc.inet1.conf' file.


I would setup a static IP first, do as root from cli;

Code:
~#ifconfig -a                      #get recognized devices
~#ifconfig eth0 192.168.0.10       #set to a available IP
~#route add default gw 192.168.0.1 #set to your gateway
~#route -n                         #show the route table
~#ifconfig eth0 up                 #should be up already
~#ping 192.168.0.1                 #ping your gateway
~#ping 208.69.32.130               #google.com IP
~#ping google.com                  #test DNS, if fail then
                                   #check /etc/resolv.conf
You should have your '/etc/resolv.conf' setup with your 'ISP DNS' nameservers

You can setup eth1 the same way. This static IP setup for eth0 should work for you. Just change the local data as needed.

If the above static IP works then just edit the '/etc/rc.d/rc.inet1.conf' and place the necessary parameters.
 
Old 06-02-2008, 05:43 AM   #17
martysha
LQ Newbie
 
Registered: May 2008
Location: Sofia, Bulgaria (GMT+2)
Distribution: Slackware 12
Posts: 26

Original Poster
Rep: Reputation: 15
thank you guys, now i'm at work, but i've printed all and this evening will follow all your suggestions

Quote:
You can edit the '/etc/rc.d/rc.inet1.conf' to suit your needs. You don't have to run 'netconfig' multiple times. You don't have to reboot, this is not M$. To restart the inet; '/etc/rc.d/rc.inet1 restart' You can do this after editing the '/etc/rc.d/rc.inet1.conf' file.
yeah, i know. i've tried to restart inet1.conf several times but it gives me "Permission denied" i don't know why

about the lan cards, i'm using only eth1. the other is not needed now. i'm not configuring it - but each time i run netconfig it makes eth0 configuration. maybe i should delete it from conf files. i'll try

about the ip-s. my provider warned me do not give my ip address on the net. it's not that i'm too suspicious, paranoid and afraid by attacks

Last edited by martysha; 06-02-2008 at 10:34 AM. Reason: delete ips
 
Old 06-02-2008, 09:39 AM   #18
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,145
Blog Entries: 28

Rep: Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373
Hi,

Too run configuration on your system you must be 'root'.

Just edit the '/etc/rc.d/rc.inet1.conf' and comment out what you don't wish to use with a '#' sign. Post the requested information if you want us to help in diagnosis of the problem.

Did you try the static setup I suggested? If so what happened?
 
Old 06-02-2008, 09:41 AM   #19
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,145
Blog Entries: 28

Rep: Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373
Hi,

Those are static IP'S. Edit the post and delete the IP.
 
Old 06-02-2008, 11:05 AM   #20
martysha
LQ Newbie
 
Registered: May 2008
Location: Sofia, Bulgaria (GMT+2)
Distribution: Slackware 12
Posts: 26

Original Poster
Rep: Reputation: 15
Quote:
Originally Posted by onebuck View Post
Too run configuration on your system you must be 'root'.

Did you try the static setup I suggested? If so what happened?
of course i'm logging as root, that's why it's so strange!

no, not yet. when i'm back from work i'll do everything and let you know now i'm reading only.

thank you all for your help!!
 
Old 06-02-2008, 11:36 AM   #21
T3slider
Senior Member
 
Registered: Jul 2007
Distribution: Slackware64-14.1
Posts: 2,366

Rep: Reputation: 837Reputation: 837Reputation: 837Reputation: 837Reputation: 837Reputation: 837Reputation: 837
Quote:
Originally Posted by martysha
i've tried to restart inet1.conf several times but it gives me "Permission denied" i don't know why
It should be
Code:
# /etc/rc.d/rc.inet1 restart
and NOT
Code:
# /etc/rc.d/rc.inet1.conf restart
You should also make sure that the permissions are correct on /etc/rc.d/rc.inet1:
Code:
# ls -l /etc/rc.d/rc.inet1
-rwxr-xr-x 1 root root 9237 2007-06-30 22:04 /etc/rc.d/rc.inet1*
(Note that the timestamp will probably be different)
 
Old 06-02-2008, 04:35 PM   #22
martysha
LQ Newbie
 
Registered: May 2008
Location: Sofia, Bulgaria (GMT+2)
Distribution: Slackware 12
Posts: 26

Original Poster
Rep: Reputation: 15
ok.. problem finally fixed!! it's working!

report:

like T3slider suggested, i've decided to delete all info about eth0. (it's a integrated lan card that i'm not using but in the beginning i didn't know which card i was using - eth0 or eth1, so that's why i left the info from the netconfig eth0 in the conf files).

firstly i've opened the udev directory, the rules file and i saw that it's not difficult to switch eth0 and eth1.

but i decided to try the other solutions first. i deleted all the info eth0 in all files i knew.
after that, i started to configure eth1 by the list given from onebuck. it's very good because it's step by step no need to think, hehe

and.. magic happened inside - it's working now!!! i've rebooted a few times for sure.

conclusion: if you have two lan cards and try to use only one of them, do not configure any details for the other. and, the most important - do not provide the same ip address for the two.

T3slider you were absolutely right - i was writing # /etc/rc.d/rc.inet1.conf restart instead of # /etc/rc.d/rc.inet1 restart i have no idea why!!!

thank you all so much again !!

now.. step 4 - building a kernel... and i have a lot of manuals if something goes wrong -- i'll let you know...
 
Old 06-03-2008, 12:35 PM   #23
onebuck
Moderator
 
Registered: Jan 2005
Location: Summer Midwest USA, Central Illinois, Winter Central Florida
Distribution: SlackwareŽ
Posts: 13,145
Blog Entries: 28

Rep: Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373Reputation: 2373
Hi,

Actually all you have to do is comment out the unnecessary data with a '#' in the '/etc/rc.d/rc.inet1.conf'. That way you can comment and change the file to suit your needs.

In the future read all the post(s) for understanding. If you had read earlier post(s), you were told to do a '/etc/rc.d/rc.inet1 restart'. I know that this much information can be hard to understand all at once. I'm glad to see you got the system up!
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
Slackware 10 network configuration. Problem with 8139 network card drivers ! Padmakiran Linux - Networking 8 03-27-2007 06:48 AM
No LAN type found in network configuration on redhat 9.0 ejain Linux - Networking 3 05-11-2005 09:30 AM
LAN type not found in network configuration ejain Linux - Hardware 1 04-01-2005 09:41 AM
problem with LAN configuration aditya1 Linux - Networking 5 03-10-2005 01:46 PM
Lan configuration problem - NFS boot problem - RX&TX packets errors 242VDM242 Linux - Networking 4 11-25-2004 01:35 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 01:35 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Facebook: linuxquestions Google+: linuxquestions
Open Source Consulting | Domain Registration