Linux - Networking This forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game. |
Notices |
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
Are you new to LinuxQuestions.org? Visit the following links:
Site Howto |
Site FAQ |
Sitemap |
Register Now
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
|
 |
|
12-03-2004, 06:37 PM
|
#1
|
LQ Newbie
Registered: Dec 2004
Distribution: Suse / Fedora
Posts: 7
Rep:
|
Can't get network connectivity
I have recently installed 2 different versions of Linux (Suse 9.1 & Fedora Core 1) on two different computers in two different network environments and in both cases have failed to get IP network connectivity working.
Firstly I'd like to state that I have previously installed Suse 8.2 & 9 without any network issues.
In the first case, I installed Suse 9.1 on a HP LH 3 server in a network that has a W 2003 server providing DHCP.
The install proceeded without any problems, and DHCP was selected as networking option. When installation was complete, no IP connectivity was possible, I could not ping any other device on network, neither coule any other device ping the Linux host.
Changing the NIC to be static IP had no impact, pinging local host gives expected result as does pinging statically assigned IP from local host but communication to any other network device is not possible.
In the second case, I installed Fedora Core 1 on a completely different computer on a different network (Netgear Router providing DHCP) but am experiencing the same issue (no network connectivity). Neither static or DHCP option makes any difference.
The hardware is all functioning correctly (same hardware configured with windows OS works correctly).
The only common element (me excluded!) is that the same network card type is being used (3Com 590 Combo Boomerang) in each computer but there is no obvious error e.g. plug and play option picks up card and installs driver.
ifconfig -a eth0 gives expected result and there is no IRQ clash.
I have spent a 2 whole days on this and am completely stumped
Help!!!!!
|
|
|
12-04-2004, 01:29 AM
|
#2
|
LQ Newbie
Registered: Nov 2004
Location: Toowoomba, Australia
Distribution: Suse 10.1
Posts: 28
Rep:
|
do you have the host (group name the same and what are the subnet masks set to
can u give us ideas on what program you are trying to network the computers with
ive used samba to network two computers together before and it took me a few gos to get it right
|
|
|
12-04-2004, 02:17 AM
|
#3
|
LQ Newbie
Registered: Dec 2004
Distribution: Suse / Fedora
Posts: 7
Original Poster
Rep:
|
The hostname is just the default 'linuxhost', the other settings regarding networking should be taken care of via DHCP e.g. subnetmask, DNS, Gateway etc.
I understand about Samba, but the problem I am having is related to basic network connectivity.....on boot up the Linux host attempts to get an IP address but fails (system says it is backgrounding - i.e. waiting until a DHCP server can be contacted.
I have a netgear broadband router for Internet access and previously this has worked with linux....I have had Suse 8.2 configured and working 6 months ago but now want to try different versions.
So, I then tried the static IP route and manually input the required info (using the 10.x.x.x range plus 255.0.0.0). I checked the settings are present in the redhat ethernet interface config files, but the end result is the same, I cannot communicate with other devices and they cannot communicate with the linux host (using ping).
What does confuse me is that the IP stack appears to function, I can ping loopack 127.0.0.1 and I can ping the statically assigned IP address e.g. 10.0.0.2 from the linx host command prompt.
What I can't understand is why I have failed with two different computers with different distros on different networks (the common element being me!!!)
Any help appreciated
|
|
|
12-07-2004, 02:05 AM
|
#4
|
LQ Newbie
Registered: Nov 2004
Location: Toowoomba, Australia
Distribution: Suse 10.1
Posts: 28
Rep:
|
is there anything else that could be interfering (eg firewall settings) as the problem sounds like it is being blocked
and how many computers are on the network(s)
Details for a simple network
groupname: needs to be the same eg network
hostname/computer name: is unique for each computer eg A & B
ip address: i find static is easier for networks so using them on the same ip range eg 128.67.52.x is useful for configuration
subnet mask: needs to be the same eg 255.255.255.0
|
|
|
12-07-2004, 10:21 AM
|
#5
|
LQ Newbie
Registered: Dec 2004
Distribution: Suse / Fedora
Posts: 7
Original Poster
Rep:
|
Firewall is off (service is stopped).
Have tried both DHCP and static addressing - no difference is observed either way in so far as neither work.
With static addressing, ifconfig displays correct information, with DHCP, ifconfig shows that an IP address has not be obtained.
What is 'groupname'? Are you referring to Netbios name for workgroup?
Surely I don't need any of this to be configured just to get basic IP (pinging) connectivity between two hosts on a simple (hub based) network?
|
|
|
12-07-2004, 07:24 PM
|
#6
|
Member
Registered: Feb 2004
Location: Outermost mingetty
Distribution: RHEL3,RH4U4,Sol9, Sol10
Posts: 321
Rep:
|
Are you pinging by hostname or address?
|
|
|
12-08-2004, 02:59 AM
|
#7
|
LQ Newbie
Registered: Dec 2004
Distribution: Suse / Fedora
Posts: 7
Original Poster
Rep:
|
Pinging by address
|
|
|
12-09-2004, 01:00 PM
|
#9
|
Member
Registered: Oct 2003
Location: Pakistan
Posts: 59
Rep:
|
try editing rc.local with net configuration
|
|
|
12-10-2004, 06:48 PM
|
#10
|
LQ Guru
Registered: Jun 2001
Location: South Alabama
Distribution: Fedora / RedHat / SuSE
Posts: 7,163
Rep:
|
I had the same issue with my 3com card and just used my linksys card. When I decided to install RHL 9 back on the machine it was working. Looks like a kernel issue to me.
|
|
|
12-17-2004, 07:36 AM
|
#11
|
LQ Newbie
Registered: Dec 2004
Location: Brazil
Distribution: SUSE
Posts: 10
Rep:
|
NewBie versus Internet
Hallo, Can some body help to config my internet. Im im my work, there are about 30 computers connected to a linux server and Im im running linux, with Suse 7.2.
Thank you
Cyrius
Last edited by cyrius; 12-17-2004 at 07:37 AM.
|
|
|
12-18-2004, 12:31 AM
|
#12
|
Member
Registered: Oct 2003
Location: Pakistan
Posts: 59
Rep:
|
if u wanna use linux as a router
Hello
If you wanna use linux as an internet gateway use it as a router...either use zebra or pick the appropriate routing HOWTO from
http://tldp.org/HOWTO/HOWTO-INDEX/ne...tml#NETROUTING
Infact EAT TLDP.. i simply luv it..
least being try editing rc.local in your /etc.
If you don't know how 2 configure rc.local lemme know..in a hurry right now...hope it all helps
Thanks
Fahad
|
|
|
12-18-2004, 12:31 PM
|
#13
|
LQ Newbie
Registered: Dec 2004
Location: Brazil
Distribution: SUSE
Posts: 10
Rep:
|
Ok im going to try it
|
|
|
12-18-2004, 03:16 PM
|
#14
|
LQ Newbie
Registered: Dec 2004
Location: Brazil
Distribution: SUSE
Posts: 10
Rep:
|
Re: if u wanna use linux as a router
So i try to configure my network following the HOWTO that u gave me, but doesn't work...
Look that...
my modules.conf:
------------------------------------------------------------------------------
alias eth0 rtl8139
alias eth1 via-rhine
alias tr0 off
alias scsi_hostadapter off
alias fb0 off
------------------------------------------------------------------------------
but when I try to type:
schon:~ # ifconfig -a
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:16 errors:0 dropped:0 overruns:0 frame:0
TX packets:16 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
schon:~ #
schon:~ # ifconfig eth0
eth0: error fetching interface information: Device not found
schon:~ # ifconfig eth1
eth0: error fetching interface information: Device not found
------------------------------------------------------------------------------
My card is a realtek 8139(A) .... waiting for answers
|
|
|
12-18-2004, 09:11 PM
|
#15
|
LQ Guru
Registered: Jun 2001
Location: South Alabama
Distribution: Fedora / RedHat / SuSE
Posts: 7,163
Rep:
|
try this
modprobe rtl8139
modprobe via-rhine
|
|
|
All times are GMT -5. The time now is 12:27 AM.
|
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
|
Latest Threads
LQ News
|
|