Networking Forums

Networking Forums > Computer Networking > Linux Networking > Can't get Linux to connect to the internet - 2 ethernet boards

Reply
Thread Tools Display Modes

Can't get Linux to connect to the internet - 2 ethernet boards

 
 
Maira Carvalho
Guest
Posts: n/a

 
      05-05-2004, 05:24 PM
Hello all,

I'm new to Linux. I am trying to set up a network using a Conectiva 9
to share internet connection between other windows machines. At this
time, I have this network running using a WinXP with two ethernet
boards, one connected to my cable modem (no authentication needed) and
the other manually assigned the address 192.168.0.1. But when I try to
get Linux to do the same job, I can't ping any outside address. If
anyone could help me... I don't know what kind of information one
would need to figure out what's happening, but here are some of the
outputs I get:

--------- dmesg -------------
8139too Fast Ethernet driver 0.9.26
PCI: Found IRQ 10 for device 00:0a.0
PCI: Sharing IRQ 10 with 00:07.2
PCI: Sharing IRQ 10 with 00:07.3
eth0: RealTek RTL8139 Fast Ethernet at 0xc40f5000, 00:08:54:11:69:20,
IRQ 10
eth0: Identified 8139 chip type 'RTL-8139C'
eth0: Setting 100mbps full-duplex based on auto-negotiated partner
ability 45e1.
VIA Rhine Family Fast Ethernet Adapter Driver Ver. 4.32
Copyright (c) 2002 VIA Technologies, Inc.
PCI: Found IRQ 12 for device 00:09.0
eth1: VIA Rhine III Fast Ethernet Adapter
eth1: MAC=00:08:54:0A:10:7C IO=0xe800 Mem=0xc4102000 IRQ=12
eth1: failed to detect cable link
eth1: Link autonegation speed 100M bps full duplex
eth1: failed to detect cable link
eth1: Link autonegation speed 100M bps full duplex
eth1: failed to detect cable link
martian source xxx.xx.x.xx from xxx.xx.x.x, on dev eth1
ll header: ff:ff:ff:ff:ff:ff:00:c0:49:25:d1:a0:08:06
eth1: Link autonegation speed 100M bps full duplex
martian source yyy.yyy.yyy.yy from yyy.yyy.yyy.y, on dev eth1
ll header: ff:ff:ff:ff:ff:ff:00:c0:49:25:d1:a0:08:06
(keeps on with several different addresses that are alike the network
my ISP puts me in - I am in xxx.xxx.aaa.b and the addresses are
xxx.xxx.nnn.m. Only the first was a completely different IP)
NET: 345 messages suppressed.
martian source yyy.yyy.yyy.y from 200.196.108.1, on dev eth1
ll header: ff:ff:ff:ff:ff:ff:00:c0:49:25:d1:a0:08:06
NET: 396 messages suppressed.

and goes on.
-----------------------------------

--------- ifconfig ----------------
eth0 Encapsulamento do Link: Ethernet Endereço de HW
00:08:54:11:69:20
inet end.: 192.168.0.100 Bcast:192.168.0.255
Masc:255.255.255.0
UP BROADCASTRUNNING MULTICAST MTU:1500 Métrica:1
RX packets:121 errors:0 dropped:0 overruns:0 frame:0
TX packets:127 errors:0 dropped:0 overruns:0 carrier:0
colisões:0 txqueuelen:100
RX bytes:15687 (15.3 Kb) TX bytes:25577 (24.9 Kb)
IRQ:10 Endereço de E/S:0x5000

lo Encapsulamento do Link: Loopback Local
inet end.: 127.0.0.1 Masc:255.0.0.0
UP LOOPBACKRUNNING MTU:16436 Métrica:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
colisões:0 txqueuelen:0
RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)

-------------------------------------------------

I typed "ifconfig eth1 up" and now I get:

-------------- ifconfig --------------------------
eth0 Encapsulamento do Link: Ethernet Endereço de HW
00:08:54:11:69:20
inet end.: 192.168.0.100 Bcast:192.168.0.255
Masc:255.255.255.0
UP BROADCASTRUNNING MULTICAST MTU:1500 Métrica:1
RX packets:167 errors:0 dropped:0 overruns:0 frame:0
TX packets:170 errors:0 dropped:0 overruns:0 carrier:0
colisões:0 txqueuelen:100
RX bytes:21706 (21.1 Kb) TX bytes:32886 (32.1 Kb)
IRQ:10 Endereço de E/S:0x5000

eth1 Encapsulamento do Link: Ethernet Endereço de HW
00:08:54:0A:10:7C
UP BROADCASTRUNNING MULTICAST MTU:1500 Métrica:1
RX packets:169 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
colisões:0 txqueuelen:100
RX bytes:7774 (7.5 Kb) TX bytes:684 (684.0 b)
IRQ:12 Endereço de E/S:0xe800

lo Encapsulamento do Link: Loopback Local
inet end.: 127.0.0.1 Masc:255.0.0.0
UP LOOPBACKRUNNING MTU:16436 Métrica:1
RX packets:2 errors:0 dropped:0 overruns:0 frame:0
TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
colisões:0 txqueuelen:0
RX bytes:100 (100.0 b) TX bytes:100 (100.0 b)

-------------------------------------------------

That's it. Any ideas, anyone? I would greatly appreciate.

Thanks,
Maira Carvalho
 
Reply With Quote
 
 
 
 
Ralf Herrmann
Guest
Posts: n/a

 
      05-05-2004, 07:31 PM
Hi,

> I'm new to Linux. I am trying to set up a network using a Conectiva 9
> to share internet connection between other windows machines. At this
> time, I have this network running using a WinXP with two ethernet
> boards, one connected to my cable modem (no authentication needed) and
> the other manually assigned the address 192.168.0.1. But when I try to
> get Linux to do the same job, I can't ping any outside address. If
> anyone could help me... I don't know what kind of information one
> would need to figure out what's happening, but here are some of the
> outputs I get:


First of all you should find out, how the network card attached
to your cable modem gets its IP.
I guess unless your ISP gave you a fix IP address, this interface
is configured via DHCP.

So you should make sure, your eth1 will use DHCP as well
(or give it the static IP in case you have one).

> -------------------------------------------------
>
> I typed "ifconfig eth1 up" and now I get:
>
> -------------- ifconfig --------------------------


>
> eth1 Encapsulamento do Link: Ethernet Endereço de HW
> 00:08:54:0A:10:7C
> UP BROADCASTRUNNING MULTICAST MTU:1500 Métrica:1
> RX packets:169 errors:0 dropped:0 overruns:0 frame:0
> TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
> colisões:0 txqueuelen:100
> RX bytes:7774 (7.5 Kb) TX bytes:684 (684.0 b)
> IRQ:12 Endereço de E/S:0xe800


Obviousely, with this command line your eth1 doesn't get a valid IP
configuration. I don't know anything about the Conectiva distro,
so you should try to get eth1 set up to the same values,
as it's done on your XP box.

Once this is done, you should be able to ping all outer machines
at least on your linux box.
DHCP should add a default route to the unix system, which tells it
to use your ISP's gateway.....
If you don't use DHCP, you have to set up the default gateway yourself,
type "man route" to get started with that.

Ok, let's say, your linux box can access the internet.....
this doesn't mean your other boxes on your LAN can do this, too.
You have to set your linux box (192.168.0.1) as the default gateway
in all your windows boxes and you have to enable
masquerading on your linux box.
That means you have to enable your linux box to be a gateway for the
other machines.
But again, i don't know, how masquerading is done in Conectiva...

Something about cable modem authentification:
you said there is non for you.

Well in some other recent thread of this newsgroup,
someone had a quite similar problem.
He also used a cable modem for internet access.
Well, his ISP had a MAC address mapping at their side,
so that he could not connect with the new linux box
because he used another network card.....

Maybe if you don't get DHCP working, this might be the reason.
Ask your ISP:-)

HTH

Ralf
 
Reply With Quote
 
Maira Carvalho
Guest
Posts: n/a

 
      05-06-2004, 05:20 AM
Hello, Ralf, thanks so much for your answer.

Oh, well, I discovered what was the problem. It was something REALLy
silly: While testing both computers, I kept them connected to the hub
at the same time. My Linux box was getting confused because WinXP
still had DHCP running. Oh, well, so many hours testing and testing...
=)

Now that I can access the internet with my Linux box, I am trying to
make the computers in the local network to access the outside world. I
will look out for some tutorials about masquerading now. It's being so
painful to get things to work!!

Again, thank you so much!
Maira Carvalho


Ralf Herrmann <(E-Mail Removed)> wrote in message news:<c7bfbk$n66$(E-Mail Removed)>...
> Hi,
>
> > I'm new to Linux. I am trying to set up a network using a Conectiva 9
> > to share internet connection between other windows machines. At this
> > time, I have this network running using a WinXP with two ethernet
> > boards, one connected to my cable modem (no authentication needed) and
> > the other manually assigned the address 192.168.0.1. But when I try to
> > get Linux to do the same job, I can't ping any outside address. If
> > anyone could help me... I don't know what kind of information one
> > would need to figure out what's happening, but here are some of the
> > outputs I get:

>
> First of all you should find out, how the network card attached
> to your cable modem gets its IP.
> I guess unless your ISP gave you a fix IP address, this interface
> is configured via DHCP.
>
> So you should make sure, your eth1 will use DHCP as well
> (or give it the static IP in case you have one).
>
> > -------------------------------------------------
> >
> > I typed "ifconfig eth1 up" and now I get:
> >
> > -------------- ifconfig --------------------------

>
> >
> > eth1 Encapsulamento do Link: Ethernet Endereço de HW
> > 00:08:54:0A:10:7C
> > UP BROADCASTRUNNING MULTICAST MTU:1500 Métrica:1
> > RX packets:169 errors:0 dropped:0 overruns:0 frame:0
> > TX packets:2 errors:0 dropped:0 overruns:0 carrier:0
> > colisões:0 txqueuelen:100
> > RX bytes:7774 (7.5 Kb) TX bytes:684 (684.0 b)
> > IRQ:12 Endereço de E/S:0xe800

>
> Obviousely, with this command line your eth1 doesn't get a valid IP
> configuration. I don't know anything about the Conectiva distro,
> so you should try to get eth1 set up to the same values,
> as it's done on your XP box.
>
> Once this is done, you should be able to ping all outer machines
> at least on your linux box.
> DHCP should add a default route to the unix system, which tells it
> to use your ISP's gateway.....
> If you don't use DHCP, you have to set up the default gateway yourself,
> type "man route" to get started with that.
>
> Ok, let's say, your linux box can access the internet.....
> this doesn't mean your other boxes on your LAN can do this, too.
> You have to set your linux box (192.168.0.1) as the default gateway
> in all your windows boxes and you have to enable
> masquerading on your linux box.
> That means you have to enable your linux box to be a gateway for the
> other machines.
> But again, i don't know, how masquerading is done in Conectiva...
>
> Something about cable modem authentification:
> you said there is non for you.
>
> Well in some other recent thread of this newsgroup,
> someone had a quite similar problem.
> He also used a cable modem for internet access.
> Well, his ISP had a MAC address mapping at their side,
> so that he could not connect with the new linux box
> because he used another network card.....
>
> Maybe if you don't get DHCP working, this might be the reason.
> Ask your ISP:-)
>
> HTH
>
> Ralf

 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

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 On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
can not connect to internet via my linksys router on fedora linux desktop ihomestore@gmail.com Linux Networking 2 04-09-2006 04:03 AM
Connect Windows to Linux via Internet Jeremy Heersink Linux Networking 3 03-09-2006 06:28 PM
Ethernet Card Issues: Unable to connect to Internet. Please Help. SK Windows Networking 0 03-04-2005 10:07 AM
Using a Linux Server to connect Windows workstations to the internet. JRRadtke Linux Networking 1 08-27-2003 07:28 AM
Linux Box (Red Hat 9 Can't Connect to Internet DavidNoack Linux Networking 0 07-08-2003 01:04 AM



1 2 3 4 5 6 7 8 9 10 11