connecting fedora 13 to D-Link router for online access

[settingsun]

My goal is to have two computers online through D-Link router. One runs windows xp and the other fedora 13. I want xp/firefox to be able to go online ( it can right now) and see fedora index file ( by typing in server ip behind router) so I can see my work through firefox as I build the server and go online with both.

I connected both computers with a crossover cable (offline), and I was able to see my index file thru firefox. Now I'm trying to connect both to internet thru router with cat5 cable.

xp is connected. Trying to add fedora. Connected fedora to router with cat 5 cable. Used ifconfig eth0 192.168.1.2 netmask 255.255.255.0 up to bring up interface.

Tried to add routers ip address as default gateway to routing table with command: route add default gw 192.168.0.1 (ip for manual router web config) netmask 255.255.255.0

Bash response: SIOCADDRT: No such process.

cat /etc/sysconfig/network returns:

Networking=yes
Hostname=localhost.localdomain


cat /etc/sysconfig/network-scripts/ifcfg-eth0 returns:


DEVICE=eth0
ONBOOT=yes
HWADDR=2C3...
BOOTPROTO=none
IPADDR=192.168.1.2
NETMASK=255.255.255.0
TYPE=Ethernet


Does anyone know how to connect fedora to router for online access?

[glennzo]

Plug an Ethernet cable into the router and plug the other end into the Fedora box.

[stevea]

Originally Posted by settingsun

Tried to add routers ip address as default gateway to routing table with command:
route add default gw 192.168.0.1 (ip for manual router web config) netmask 255.255.255.0

Bash response: SIOCADDRT: No such process.

First - you need to be root to set a route.
The SIOCADDRRT message just means the socket/stack ioctl to the stack failed.

The OLD DEPRECATED command is like .....
route add default gw 192.168.0.1
or
route add default gw 192.168.0.1 netmask 255.255.255.0
which are identical.

Note that DEFAULT and netmask are not meaningful together.


The modern correct way to do this is ....
ip route add default via 192.168.0.1 proto static
or
ip route add default via 192.168.0.1 dev eth0 proto static
Change 'eth0' to the interface you intend the route to apply to.

[settingsun]

I typed in: ip route add default via 192.168.0.1 proto static

Bash returned: RTNETLINK answers: No such process.

I typed which iproute

No iproute. I'll have to download that when I get connected.


How do I find the right name for the router so I can place it where eth0 is in the route command?

Thank you

[stevea]

It's
ip route

not
iproute


I should have read your first post closer ...
Here is the problem

...
IPADDR=192.168.1.2
NETMASK=255.255.255.0
...

So that interface CAN'T access the gateway at 192.168.0.1

You want both of your system to be on the same LAN right ?
So both need addresses like 192.168.0.*

CHANGE it to
IPADDR=192.168.0.2

[settingsun]

I went in the the GUI network utility and now everything pings and I can see my fedora index page by typing the ip into firefox. Everything behind the router works if I use ip addresses only.

I still want to learn how to do this on the command line.


I typed: which ip route.

Bash returned:

/sbin/ip
/sbin/route



Not sure from that response if I have the iproute binary. Also, I need to learn how to set up DNS resolution, so I can ping urls out side my network, and use yum.


The router's WAN configuration shows 2 DNS ip addresses. Do I put those in the DNS fields of the of the network GUI utility, or do I put the router's private ip address there? In other words, since the DNS ip's are part of the WAN addressing of the router (it's public side), does fedora's yum utility need them ( can it see them?) from behind the router? Or does yum need to see the router's private ip so the router itself can forward DNS resolution requests to those public facing DNS server ip addresses?

Thank you

---------- Post added at 06:52 PM ---------- Previous post was at 03:45 PM ----------

Got it. It works. Thank you.

I did it through the network GUI. I want to learn to do it through the command line. The strange thing is I went to /etc/resolv.conf and entered the keyword nameserver, then the DNS ip my router showed me, twice.

It didn't work. I did it again through the GUI ( using the same keyword, ip's and format) and it did work. I cat the /etc/resolv.conf file after I got it to work and it shows me exactly what I put in it when it didn't work. I'm obviously still missing details somewhere.

At least now I have a set up that works that I can use to learn more from.


Thank you!

[bob]

A bit delayed, but moved to EOL (F13's history now)