[Oragex]

Hi,

I'm a noob in Linux. I've installed Fedora Core 3 on my computer (Laptop ECS g733, p4 2.4, 512 ram, all components SIS). It works great! I still have some problem finding things but it's ok.

The only problem is that I just can't connect on the internet. I have a DSL connection. D-Link 500G mount on a lan with DHCP.

It works fine except on Linux. I can ping the other computers (but I can't see them on the Microsoft Networks folder (why??). I have this configuration :

eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF
inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::fdff:ffff:feff:ffff/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:214 errors:0 dropped:0 overruns:0 frame:0
TX packets:184 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:21582 (21.0 KiB) TX bytes:14079 (13.7 KiB)
Interrupt:9 Base address:0xe000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:9122 errors:0 dropped:0 overruns:0 frame:0
TX packets:9122 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:10483779 (9.9 MiB) TX bytes:10483779 (9.9 MiB)

The first one eth0 seems to work, it's my ip adress from my Gateway but I don't know exactly what is this 'lo' thing cause with windows you only have 1 : the network card.

Someone know the solution to my problem??

Thanks!


Mickael

[Oragex]

I forgot, when i ping on the internet it workd too. I happend to me before with Windows but i forgot what I did to make it works...

Thanks!

Mickael

[danleff]

The "lo" is just your local network interface, don't worry about this.

It seems that there is a problem;

eth0 Link encap:Ethernet HWaddr FF:FF:FF:FF:FF:FF

does not seem right. It should have a valid hardware address.

Is the D-link set up via USB port?

We have a real networking expert onboard. Hopefully he will see this post.

[Oragex]

Hi!

I believe the 'Ethernet HWaddr FF:FF:FF:FF:FF:FF' is the mac address. I found the options where i can inform the mac address of the Ethernet Card but when i look in windows it doesn't tell me the mac at all! How can I discover that?

My Modem is connected to a hub, it has all the router options (with DHCP server), I putted all the firewalls options off, on the modem and in Linux. But still, I have no answers from the web except the package from the ping!

Got an idea?

Mickael

[martouf]

Quote:

I believe the 'Ethernet HWaddr FF:FF:FF:FF:FF:FF' is the mac address.

can't be. sorry. all bits on is the ethernet broadcast address.

Until ifconfig shows the same MAC address as Windows, then you've
got some kind of configuration problem.

Quote:

when i look in windows it doesn't tell me the mac at all! How can I discover that?

(assuming WinXP)
Start->Run-> "cmd" -> then "ipconfig /all"

You'll get full interface information, IP address and MAC address.


In linux, if you check the output of 'dmesg' or the contents
of /var/log/messages, does it say anything interesting about 'eth0'?

[Oragex]

[martouf]

[Oragex]

[Oragex]

[BSchindler]

Sorry I saw this so late.

You asked a couple of questions:

* The HWare address also known as the MAC address is the physical ethernet address of the adapter in your computer. As you know, the ip address you are using 192.168.0.5 is not the same - obviously.

* The translation of MAC <-> IP is done by a facility known as ARP - Address Resolution Protocal. This allows ethernet packets (which really "hold" the TCP/IP packets) to be sent to the correct place. Without getting into too much detail, the address FF:FF:FF:FF:FF:FF is called the "broadcast address" and is NOT a legal node address.

* This explains why when you use /sbin/ifconfig hw ether ... to force the MAC address to be something other than FF:FF... your system works. (By the way, Windows does have a facility to create a dummy MAC address if a probe is not successful in getting the real one.) If you open a command window in Windows and issue:

arp -a

you will see the translation of MAC <-> IP there. It might be interesting if you would post what you see there.

* Ping is a different kind of packet or message on the network. It uses a protocol ICMP and does not have all the connection handshaking that TCP/IP has. When you attempted to access the web you use TCP/IP for http services (port 80). The TCP/IP connection is much more complex than ICMP. ICMP is like throwing a stone in a pond and hoping it bounces off something.

You will find a few things useful on Linux. Many times you can get a lot of information from the "man" pages. Open a terminal window and type

man arp

for instance. You will get a detailed explaination of arp (for instance). Also the "info" command can be useful.

And, do not forget the search engines. Do a google search on TCP/IP and you can get a huge list of links to the protocol (for example).

When you feel more confident, you should put your "ifconfig hw ether" into your system startup script. That way you will always start Linux with your network connection working.

Hope this has been useful.
Bill

[martouf]

under Windows, can you use device manager (Start->Run->"devmgmt.msc" ),
find the SiS network adapter, pull up the properties (right click) and
report the version number of your driver?

according to this article, you need v1.16 or later
before the correct MAC address can be revealed by "ipconfig /all".

also, under Linux, when your network interface driver loads correctly
you will see something that looks like this in /var/log/messages (or via "dmesg" ):

[size:3][tt]sis900.c: v1.07.06 11/07/2000
eth0: SiS 900 PCI Fast Ethernet at 0xd000, IRQ 10, 00:00:e8:83:7f:a4.
eth0: SiS 900 Internal MII PHY transceiver found at address 1.
eth0: Using SiS 900 Internal MII PHY as default[/tt][/color]

Note carefully the first 3 octets of the MAC address.

The MAC address is assigned by SiS (id 0x0000e8) and is unique for the example
network interface (nbr 0x837fa4). Besides the ethernet broadcast address,
there is a whole range of addresses reserved for ethernet multicast which
you should not assign to your network interface.

Instead of trying to reassign your interface's address, I think it would be best
to fix the driver problems so you will end up using the MAC address already
allocated for your interface by SiS.

http://www.sis.com/support/index.htm

what is the full identification string returned by "lspci -v" for the interface?

for Windows, the latest driver appears to be v1.18 and for Linux it's v1.08.

Compare your Windows network driver to the contents of the LAN driver archive from ECS.

[grapepot]

HELP...

I have a similar problem, but I didn't install anything new.. All of a sudden my internet stops working on my older PC. The networking still works between my two PCs. The PC that stopped working is running Win 98 and I can't find anything hardware wise wrong with it. I tried Firefox by Mozilla, because some people told me that IE can get virus that screw it up. But that didn't work either.

Any ideas?

My stuff.
Windows 98 IP Configuration

Host Name . . . . . . . . . : compaq.wowway.com
DNS Servers . . . . . . . . : 64.233.222.2
64.233.222.7
Node Type . . . . . . . . . : Broadcast
NetBIOS Scope ID. . . . . . :
IP Routing Enabled. . . . . : No
WINS Proxy Enabled. . . . . : No
NetBIOS Resolution Uses DNS : Yes

0 Ethernet adapter :

Description . . . . . . . . : SiS NIC SISNIC
Physical Address. . . . . . : 00-D0-09-E8-46-9A
DHCP Enabled. . . . . . . . : No
IP Address. . . . . . . . . : 192.168.1.104
Subnet Mask . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . : 192.168.1.1
Primary WINS Server . . . . :
Secondary WINS Server . . . :
Lease Obtained. . . . . . . :
Lease Expires . . . . . . . :