I have a "Linksys WAG54G" connected to my ethernet card "D-link DFE-530TX".
I am sure that my NIC is working on linux. My distro is FC3. i cant seem to get connected on the net. I am a total so will need to know how to do things

To connect to the internet, of course, you have to set up your ADSL Gateway properly.

In order to do that, of course you have to connect to the linksys box.

Check the default ip address of the linksys box. Set you NIC to a fixed IP address. For example, if the default ip is 192.168.0.1, then set the ip of your FC3 PC to 192.168.0.2 You can do it via the GUI or directly edit the /etc/sysconfig/network-script/ifcfg-eth0

Now, login to the linksys box with the default password and setup all the thing you needed. (ISP login/password etc)

At this point you can consider to turn on DHCP or not. If so, you have to modifiy your FC3 networking setting later to take advantage of that.

That's an outline of steps you need to take

I have 1 pc dualbooting winxp n FC3
How do i do all that? I mean i want instructions.
I know I am acting STUPID but its my first time

OK. Easy. :-)

First thing first. Have you set up the linksys box yet? (Because obviously you can connect to internet now by posting here)

If not yet configure the box, you have to *read* the documentation comes with the box for its default ip, default login name and default password.

In the guides it says how to do it in windows, nothing regarding linux.

On trying to connect to the net, the error it gives:

1)

since this guy 'Linksys WAG54G' will connect to your ISP, you do not need to do the adsl-start in linux at all.

The linksys box will handle the adsl connection

2)

Look at the manual of Linksys WAG54G. See chapter 5? You can configure the linksys box by accessing the web inteface of the box.

The box has a default ip of 192.168.1.1. Login is admin and password is admin

3)

Now. In order to access the box's web interface, your NIC card must have the right ip address.

Can you try ? What did you see?

4)

Assuming that your DLink NIC card is eth0. If eth0 has an IP similar to 192.168.1.x (where 2 <= x < 255) , then you can try out step 2 as mentioned above.

If not, post the result of step 3 and I'll get back to you.

Sorry to BUG you again but where do i say ifconfig? In the TERMINAL?
Its better to chat on msn or yahoo
msn id megadsonic@hotmail.com
yahoo id megadsonic

Yes. ifconfig is a console program.

The following is a typical output:

=====================================================

[usr@test ~]# ifconfig
eth0 Link encap:Ethernet HWaddr 01:50:FD:4A:2B:A4
inet addr:192.168.0.5 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::250:fcff:fe3a:1aa3/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:67385309 errors:0 dropped:0 overruns:0 frame:0
TX packets:119792379 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4156476518 (3.8 GiB) TX bytes:3002719951 (2.7 GiB)
Interrupt:5 Base address:0xa000

===================================================

I want to see what is your inet addr now.

"ifconfig" doesnt work. It gives some kind of error.

Then, what kind of error?

You have to give people more information in order to help...

bash: ifconfig: command not found

It is because usually ifconfig is in /sbin and (most likely) /sbin is not in your PATH envirnoment variable.

try run

OK I finally agree I am a failure.
I tried my best but I couldnt get /sbin/ifconfig running.Whenever I try to open the file, the window just shuts off

Just like picking up any new skill, learning to use linux requires you to acitvely study. I guess you lack the basic of how to get thing done in linux and these information are readily available in a lot of HOW-TO.

And it is not necessarily command line tools (such as ifconfig). If you understand what I am trying to do (as outline in post #6) there is a lot of alternative way to achieve the result. e.g. GUI alternative in GNOME.

Besides, given we are communicate via the forum, it is very important for you to provide as much info as you can. Not just some oneliner. There is no way I can see what is actucally happening to your box, right?

This post was just getting interesting!

I have the same gateway but don't know what information i should be giving to ifconfig and route.

I've tried this script:

route add 192.168.1.0 eth0
ifconfig eth0 gateway
route add default gw gateway

where "gateway" is listed in /etc/hosts as:
192.168.1.1 gateway

This allows me to access the admin server but not the internet through it.
I'm running Debian Sarge and so do not have an /etc/sysconfig/network-script/ifcfg-eth0
file.