<html> <body> The example is for Linksys however similar rules apply for other brand names. For starters reinstalling RH9 will only put you where you are now. Configuring RH9 is what you need to do. RH9 is not winodws. Without going into the weeds, look at the simple solutions first without making any assumptions. If you have a Linsys Broadband DSL or Ethernet Hub/Switch that you can access via a web browser typically by opening the browser to 192.168.0.1 and logging into the administrative tools area. [ check you appropriate owners manual ] Under the first tab called Home, if Linksys, click the left hand side button called LAN. In here you setup your systems to be exposed to the network through the router by port number. If your router has a internal IP address of 192.168.0.1 then that IP is your gateway, all the other systems would be 192.169.0.xxx with a netmask that is the same, doesn't matter what, as long as they are the same, I'd use 255.255.255.0 . So lets recap ... your router is 192.168.0.1 from inside your LAN and it is whatever your IP address is from outside the LAN. Your first RHL system should be IP 192.168.0.100 - netmask 255.255.255.0 - gateway 192.168.0.1 and don't worry about the broadcast. Use "netconfig" at the command line as root to set the IP of your RHL system. Then go into your router, 192.168.0.1 username / password and in the section where you define the systems exposed to the network, add your first system, 192.168.0.100 and if you wish to run this system as a web server you would then expose port 80 and either schedule a time it is exposed or make it exposed at all times. In a setup like this, the RHL system is not the system that holds the IP address, rather your router is the IP address that exposes just ports on your other systems. Even if you only have one system, the router is still the holder of the IP. [ check you appropriate manual for router configuration information, typically your router must be setup first ] If your not using a router or switch of any type, but rather just connecting your RHL system directly to your RJ connection at the wall, then configure it as the IP, netmask and the gateway of the switch/hub/router that controls the LAN. Typically those switches have "ping" disabled to protect other systems on the LAN from denial of service attacks like "ping floods". Instead of using "ping" to find other systems, use "traceroute" like this: [you@yoursystem]$ traceroute yahoo.com . There are many more details but this should help hopefully. Steve Larsen At 02:01 PM 3/26/2004 +0000, shatam bhattacharya wrote: <blockquote type=cite class=cite cite>Hi, The original problem was that I am not able to connect my rhl 9 box to my college LAN. I am including the following trouble shooting info and the clarification for the subnet mask (after consulting the NA) is that it is actually 255.255.0.0 for our hostel. I regret the mistake of giving the wrong data. The college server is based on rhl 9. I can ping only my system with ip 172.31.65.21 (local) and not even the systems connected through my switch ( on the same floor) . Please take a look at the following. And by the way ping is not disabled as it working on other systems. One important question is that if I make up my mind of reinstalling rhl 9 what factors should I keep in mind to avoid such problems in future ?Please suggest ! the needfull. with thanks and regards shatam uname -a Linux gomti 2.4.20-8smp #1 SMP Thu Mar 13 17:45:54 EST 2003 i686 i686 i386 GNU/Linux lspci output<?xml:namespace prefix = o ns = "urn:schemas-microsoft-com:office:office" /> 00:00.0 Host bridge: Intel Corp. 82845G/GL [Brookdale-G] <?xml:namespace prefix = st1 ns = "urn:schemas-microsoft-com:office:smarttags" />Chipset Host Bridge (rev 01) 00:02.0 VGA compatible controller: Intel Corp. 82845G/GL [Brookdale-G] Chipset Integrated Graphics Device (rev 01) 00:1d.0 USB Controller: Intel Corp. 82801DB USB (Hub #1) (rev 01) 00:1d.1 USB Controller: Intel Corp. 82801DB USB (Hub #2) (rev 01) 00:1d.2 USB Controller: Intel Corp. 82801DB USB (Hub #3) (rev 01) 00:1d.7 USB Controller: Intel Corp. 82801DB USB EHCI Controller (rev 01) 00:1e.0 PCI bridge: Intel Corp. 82801BA/CA/DB PCI Bridge (rev 81) 00:1f.0 ISA bridge: Intel Corp. 82801DB ISA Bridge (LPC) (rev 01) 00:1f.1 IDE interface: Intel Corp. 82801DB ICH4 IDE (rev 01) 00:1f.3 SMBus: Intel Corp. 82801DB SMBus (rev 01) 00:1f.5 Multimedia audio controller: Intel Corp. 82801DB AC'97 Audio (rev 01) 01:02.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10) ifconfig output eth0 Link encap:Ethernet HWaddr 00:08:A1:32:E1:7E inet addr:172.31.65.21 Bcast:172.31.67.255 Mask:255.255.252.0 UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:1 errors:1286 dropped:0 overruns:0 frame:0 TX packets:52 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:60 (60.0 b) TX bytes:3120 (3.0 Kb)Interrupt:9 Base address:0xcc00 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:375 errors:0 dropped:0 overruns:0 frame:0 TX packets:375 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:26209 (25.5 Kb) TX bytes:26209 (25.5 Kb) Netstat -rn Kernel IP routing table Destination Gway Genmask Flags MSS Window irtt Iface 172.31.64.0 0.0.0.0 255.255.252.0 U 0 0 0 eth0 169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0 127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo 0.0.0.0 172.31.65.21 0.0.0.0 UG0 0 0 eth0 >The default route is normally contained in >the /etc/sysconfig/network >file as the "GATEWAY=" equate. Here's an example: >NETWORKING=yes >HOSTNAME=prophead.corp.publichost.com >GATEWAY=192.168.0.1 >If you don't have a default route, you can add one using this command: >route add -default gw ip-addr-of-your-gateway >For example, to set up the default route as if it were in the network >file: >route add -default gw 192.168.0.1 contents of /etc/syconfig/network NETWORKING=yes HOSTNAME=ginie GATEWAY=172.31.65.21 >This is starting to sound like a firewall issue, >innit? >What's the output of 'iptables -L'? >If you get an error because iptables isn't running, >make sure that >that ugly chains crud isn't in the way by running >'lokkit' and taking >appropriate steps. >Andy iptables -L Chain INPUT (policy ACCEPT) target prot opt source destination RH-Lokkit-0-50-INPUT all -- anywhere anywhere Chain FORWARD (policy ACCEPT) target prot opt source destination RH-Lokkit-0-50-INPUT all -- anywhere anywhere Chain OUTPUT (policy ACCEPT) target prot opt source destination Chain RH-Lokkit-0-50-INPUT (2 references) target prot opt source destination ACCEPT udp -- 172.31.100.8 anywhere udp spt:domain dpts:1025:65535 ACCEPT udp -- 172.31.100.6 &nbs! p; anywhere udp spt:domain dpts:1025:65535 ACCEPT tcp -- anywhere anywhere tcp dpt:smtp flags:SYN,RST,ACK/SYN ACCEPT tcp -- anywhere anywhere tcp dpt:h! ttp flags:SYN,RST,ACK/SYN ACCEPT tcp -- anywhere anywhere tcp dpt:ftp flags:SYN,RST,ACK/SYN ACCEPT tcp -- anywhere anywhere tcp dpt:ssh flags:SYN,RST,ACK/SYN ACCEPT tcp -- anywhere anywhere tcp dpt:telnet flags:SYN,RST,ACK/SYN ACCEPT udp -- anywhere anywhere udp spts:bootps:bootpc dpts:bootps:bootpc ACCEPT udp -- anywh! ere anywhere udp spts:bootps:bootpc dpts:bootps:bootpc ACCEPT all -- anywhere anywhere ACCEPT all -- anywhere anywhere REJECT tcp -- anywhere anywhere tcp dpts:0:1023 flags:SYN,RST,ACK/SYN reject-with icmp-port-unreachable REJECT tcp -- anywhere anywhere tcp dpt:nfs flags:SYN,RST,ACK/SYN reject-with icmp-port-unreachable REJECT udp -- anywhere anywhere udp dpts:0:1023 reject-with icmp-port-unreachable REJECT udp -- anywhere anywhere udp dpt:nfs reject-with icmp-port-unreachable REJECT tcp -- anywhere anywhere tcp dpts:x11:6009 flags:SYN,RST,ACK/SYN reject-with icmp-port-unreachable REJECT tcp -- anywhere anywhere tcp dpt:xfs flags:SYN,RST,ACK/SYN reject-with icmp-port-unreachable <a href="http://in.rd.yahoo.com/specials/mailtg/*http://pepsizone.yahoo.co.in/pepsi3/cktkipyaas/">Win an evening</a> with the Indian cricket captain: <a href="http://in.rd.yahoo.com/specials/mailtg2/*http://pepsizone.yahoo.co.in/pepsi3/cktkipyaas/">Yahoo! India Promos</a>. _______________________________________________ Redhat-install-list mailing list Redhat-install-list@redhat.com <a href="https://www.redhat.com/mailman/listinfo/redhat-install-list" eudora="autourl">https://www.redhat.com/mailman/listinfo/redhat-install-list</a> To Unsubscribe Go To ABOVE URL or send a message to: redhat-install-list-request@redhat.com Subject: unsubscribe </blockquote></body> </html>