-
March 1st, 2002, 07:01 PM
#1
Member
LAN configuration on linux
I have a problem with LAN configuration on linux (Red Hat 7.2).
I had applied istruction of my linux guide, but I have note a right result 
I have 1 server and 2 clients for my home LAN.
I had configured manually follows files (on server):
/etc/hosts
#Do not remove the following line, or various program
#that require network functionality will fail.
127.0.0.1 localhost loopback
192.168.1.0 server.riv66.com server
192.168.1.11 pos1.riv66.com pos1
192.168.1.12 pos2.riv66.com pos2
/etc/host.conf
order hosts,bind
multi on
/etc/resolv.conf
domain riv66.com
search riv66.com
name server 192.168.1.0
When I try to ping from server:
[root@server root]# ping -c 3 pos1
PING pos1.riv66.com (192.168.1.11) from 192.168.1.0 : 56(84) bytes of data.
From server.riv66.com (192.168.1.0) : Destination Host Unreachable
From server.riv66.com (192.168.1.0) : Destination Host Unreachable
From server.riv66.com (192.168.1.0) : Destination Host Unreachable
--- pos1.riv66.com ping statistics ---
3 packets trasmitted, 0 packets received, +3 errors, 100% packets loss
I had configured pos1's firewall to receive all ICMP packets.
When i ping from client:
[root@pos1 root]# ping -bc 3 server
WARNING: pinging a broadcast address
PING server.riv66.com (192.168.1.0) from 192.168.1.10 : 56(84) bytes of data.
Warning: time of day goes back, taking countermeasures.
64 bytes from 192.168.1.10: icmp_seq=0 ttl=255 time=1.353 msec
64 bytes from 192.168.1.10: icmp_seq=1 ttl=255 time=84 usec
64 bytes from 192.168.1.10: icmp_seq=2 ttl=255 time=77 usec
--- server.riv66.com ping statistics ---
3 packets trasmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.077/0.504/1.353/0.600 ms
but, when i try to telnet from client to server:
[root@pos1 root]# telnet server
Trying 192.168.1.0 ...
telnet: connect to address 192.168.1.0: Network is unreachable
How is possible?
Please help I cannot configure my LAN.
I have spent many time for that, with bad results.
Thanks
What is essential is invisible
to the eye ...
]ØÐÖ§|-|Å
-
March 1st, 2002, 07:11 PM
#2
Don't use 192.168.1.0 Its an invalid address. The last number cannot be 0 or 255. They are used for other purposes. Reset your server as 192.168.1.1
\"Ignorance is bliss....
but only for your enemy\"
-- souleman
-
March 1st, 2002, 08:03 PM
#3
Member
I have changed in /etc/hosts follow line:
...
192.168.1.1 server.riv66.com server
...
and /etc/resolve.conf:
...
name server 192.168.1.1
...
I have rebooted server and client.
Ping from server:
[root@server root]# ping -c 3 pos1
PING pos1.riv66.com (192.168.1.11) from 192.168.1.0 : 56(84) bytes of data.
From server.riv66.com (192.168.1.0) : Destination Host Unreachable
From server.riv66.com (192.168.1.0) : Destination Host Unreachable
From server.riv66.com (192.168.1.0) : Destination Host Unreachable
--- pos1.riv66.com ping statistics ---
3 packets trasmitted, 0 packets received, +3 errors, 100% packets loss
Server has not changed configuration (report always 192.168.1.0).
Ping form client:
[root@pos1 root] # ping -c 3 server
PING server.riv66.com (192.168.1.1) from 192.168.1.10 : 56(84) bytes of data.
From 192.168.1.10: Destination Host Unreachable
From 192.168.1.10: Destination Host Unreachable
From 192.168.1.10: Destination Host Unreachable
--- server.riv66.com ping statistics ---
3 packets trasmitted, 0 packets received, +3 errors, 100% packets loss
192.168.1.10?!? But i have assigned 192.168.1.11 to client.
I had checked files, but configuration is reported correctly on this post.
Can you help me?
Thanks.
What is essential is invisible
to the eye ...
]ØÐÖ§|-|Å
-
March 1st, 2002, 08:10 PM
#4
Senior Member
check your /etc/sysconfig/network-scripts/ifcfg-ethX (where X is 0,1,2,3....which ever one is connected to your internal network.....it is what controls your actual ip
IPADDR=192.168.1.1 instead of IPADDR=192.168.1.0
SlackWare my first, Debian my second....building my box into the ultimate weapon
-
March 1st, 2002, 08:27 PM
#5
You might want to try giving us the output of 'ifconfig -a' This way, we can see for sure which IP's are assigned where. i am assuming your server has 2 NIC's right??? It looks to me like you have an interface configuration issue still.
But like i said, post the configs and we will help
-
March 1st, 2002, 08:40 PM
#6
Member
Well I had changed configuration in /etc/sysconfig/network-scripts/ifcfg-eth0 ...
it works !!! I can ping from server and from client
But i have another question...
I'd like use NFS, so i had edit /etc/exports:
/database *.riv66.com(rw,insecure,no_root_squash)
from shell...
[root@server root]# /usr/sbin/exportfs -av
exporting *.riv66.com:/database
in client I have created database dir on /mnt and I had edit /etc/fstab for automount of NFS on boot:
...
server:/database /mnt/database nsf rsize=8192,wsize=8192 0 0
from shell:
[root@pos1 etc]# mount /mnt/database
mount: RPC: Unable to receive; errno = Connection refused
Is a server's firewall configuration problem? How can I resolve it?
Thanks
What is essential is invisible
to the eye ...
]ØÐÖ§|-|Å
-
March 1st, 2002, 08:52 PM
#7
Member
Originally posted here by iNViCTuS
You might want to try giving us the output of 'ifconfig -a' This way, we can see for sure which IP's are assigned where. i am assuming your server has 2 NIC's right??? It looks to me like you have an interface configuration issue still.
But like i said, post the configs and we will help
On my server I have 1 NIC.
Anyway:
[root@server root]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:10:A7:06:93:EC
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:39 errors:0 dropped:0 overruns:0 frame:0
TX packets:33 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3200 (3.1 Kb) TX bytes:3152 (3.0 Kb)
Interrupt:5 Base address:0x9000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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
RX bytes:1152 (1.1 Kb) TX bytes:1152 (1.1 Kb)
Thanks.
What is essential is invisible
to the eye ...
]ØÐÖ§|-|Å
-
March 1st, 2002, 09:36 PM
#8
Junior Member
After you have been changed the IP with 192.168.1.1 you still have the problem?
Well, you should look from where you "ping" the 192.168.1.11:
[root@server root]# ping -c 3 pos1
PING pos1.riv66.com (192.168.1.11) from 192.168.1.0 : 56(84) bytes of data.
From server.riv66.com (192.168.1.0) : Destination Host Unreachable
From server.riv66.com (192.168.1.0) : Destination Host Unreachable
From server.riv66.com (192.168.1.0) : Destination Host Unreachable
It seems that you still have the 192.168.1.0 address on your interface.
It helps if you copy/paste the containt of the /etc/hosts, /etc/resolv.conf, a *full*
output of "ifconfig -a" and "route -n" *after* you made the changes.
All the best,
soles
-
March 1st, 2002, 10:03 PM
#9
Member
Well, soles look at this:
Server side:
[root@server root]# ping -c 2 pos1
PING pos1.riv66.com (192.168.1.11) from 192.168.1.1 : 56(84) bytes of data.
64 bytes from pos1.riv66.com (192.168.1.11): icmp_seq=0 ttl=255 time=1.772 msec
64 bytes from pos1.riv66.com (192.168.1.11): icmp_seq=1 ttl=255 time=263 usec
64 bytes from pos1.riv66.com (192.168.1.11): icmp_seq=2 ttl=255 time=285 usec
--- pos1.riv66.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.263/0.773/1.772/0.706 ms
[root@server root]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:10:A7:06:93:EC
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:44 errors:0 dropped:0 overruns:0 frame:0
TX packets:38 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3614 (3.5 Kb) TX bytes:3566 (3.4 Kb)
Interrupt:5 Base address:0x9000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 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
RX bytes:1152 (1.1 Kb) TX bytes:1152 (1.1 Kb)
[root@server root]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
Client side:
[root@pos1 root]# ping -c 3 server
PING pos1.riv66.com (192.168.1.11) from 192.168.1.11 : 56(84) bytes of data.
64 bytes from pos1.riv66.com (192.168.1.11): icmp_seq=0 ttl=255 time=238 usec
64 bytes from pos1.riv66.com (192.168.1.11): icmp_seq=1 ttl=255 time=97 usec
64 bytes from pos1.riv66.com (192.168.1.11): icmp_seq=2 ttl=255 time=76 usec
--- pos1.riv66.com ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max/mdev = 0.076/0.137/0.238/0.071 ms
[root@pos1 root]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:30:4F:0A:5E:33
inet addr:192.168.1.11 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:34 errors:0 dropped:0 overruns:0 frame:0
TX packets:44 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:3326 (3.2 Kb) TX bytes:3614 (3.5 Kb)
Interrupt:10 Base address:0x9000
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:22 errors:0 dropped:0 overruns:0 frame:0
TX packets:22 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1664 (1.6 Kb) TX bytes:1664 (1.6 Kb)
[root@pos1 root]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
Thanks.
What is essential is invisible
to the eye ...
]ØÐÖ§|-|Å
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
|