1. Linuxconf is a Linux administration/configuration tool...as such any Linux distribution can run it (see http://www.solucorp.qc.ca/linuxconf/).
2. Whoa...2 (I repeat 2) gateways...and 2 routers....so which box acts as gateway for which network..confusing isn't it and it may be the cause of those collisions you see on the Debian box .I suggest one box be used as a router and another be used as the gateway (and firewall) to the external network.. HTH Regards. Patrick Cheong Information Systems Assurance Measat Broadcast Network Systems e-mail: mailto:[EMAIL PROTECTED] Visit us at: http://www.astro.com.my > -----Original Message----- > From: Saran [SMTP:[EMAIL PROTECTED] > Sent: Tuesday, September 12, 2000 2:50 PM > To: CHEONG, Shu Yang [Patrick]; debian-user@lists.debian.org > Subject: RE: Network Configuration > > Hi, > > I thought linuxconf is only available on RedHat ? > > Yes, the RH box is acting as the gateway for the network also. > > Dunno about the kernel version, but I'll try it later. > > As for the collisions, I'm not sure, but there has been no problems. > Could > this be the issue ? Both the RH server and my colleague's RH PC can > connect > to the network, but my Debian can't. When I boot up my PC, there are no > conflict errors generated. How do I check whether there are any conflicts > other than this method ? > > Note that I have not included the ifconfig and route info of my Debian PC > here. But basically, I configured as the ones below, with the IP address > being the only difference. > > Thanks in advance > Saranjit Singh. > > > -----Original Message----- > From: CHEONG, Shu Yang [Patrick] [mailto:[EMAIL PROTECTED] > Sent: Tuesday, September 12, 2000 2:41 PM > To: debian-user@lists.debian.org > Subject: RE: Network Configuration > > > See below.... > > Patrick Cheong > Information Systems Assurance > Measat Broadcast Network Systems > e-mail: mailto:[EMAIL PROTECTED] > Visit us at: http://www.astro.com.my > > > -----Original Message----- > > From: Saran [SMTP:[EMAIL PROTECTED] > > Sent: Tuesday, September 12, 2000 2:05 PM > > To: debian-user@lists.debian.org > > Subject: Network Configuration > > Importance: High > > > > Hi Guys, > > > > I just subscribed to this list to get more information regarding the > > Debian > > Linux, which kind of lacks a lot of information resources. Most sites > are > > about RedHat Linux and as much as Debian is giving me problems, I still > > like > > to stick to this distribution instead of moving to RedHat. I have > several > > questions that I'd like to ask namely : > > 1. Does Debian have any administrative tools akin to IBM AIX > > smitty, smit, > > wsm (Web System Management) whereby it allows me to administer and > manage > > the system without having to edit files and typing in complex commands > > every > > time ? > [CHEONG, Shu Yang (Patrick)] Have you tried linuxconf? > > > 2. This is critical and I am about to start banging my head on the > > wall, > > except that I still holding on to the hope that you guys can help me out > > here. Well, currently there is a system within my environment which is > > running RedHat 6.x and it has two ethernet adapter (3Com) installed on > the > > system. This system is running Masquarading (Sp ???), whereby there are > > two > > networks, one is running on 100.100.100.x and the other is running on > > 255.255.255.x. This system is also acting as the gateway. > [CHEONG, Shu Yang (Patrick)] Is the RH box acting as a gateway, > too? > > A colleague of mine also runs his system on Redhat 6.x and is able to > view > > two networks on his system also having two ethernet adapters (Generic, > > dunno > > what brand they are). > > What I can't understand and which is giving me pain is that my system > > configured with Debian 2.1 cannot view the two networks. I have two > > ethernet adapters (3Com) installed and if I configure both the cards > with > > one pointing to the 100.100.100.x network and the other with the > > 255.255.255.x network, the system will not be able to ping any host out > > there (I have already configured the ifconfig and route similar to the > RH > > 6.x systems). But if I disable the 255.255.255.x network, I can ping > and > > view the other systems. If I do it the other way round, the system > cannot > > detect any host whatever (Disable 100.100.100.x and enable > 255.255.255.x). > > > > I have checked the connections to the ethernet adapters and they are > > functioning. > > > > I have updated my kernel to the 2.2.16 enabling masquarading but am > still > > unable to detect any host when both the ethernet adapters are enabled. > > > [CHEONG, Shu Yang (Patrick)] I suggest you use the 2.2.17 kernel > instead (even the 2.2.17-preX-X which includes Alan Cox's patches) as > IICR, > there were problems with the 2.2.16 kernel. Can't reccall whether the > problem was in relation to security or some other issue. > > > What could be the problem here ? > > > > I've included the ifconfig and route info for the gateway system and > also > > my > > colleague's system for your info. My system route and ifconfig > > information > > is as the ones below, but I still can't detect both networks. > > > > $ /sbin/ifconfig > > eth0 Link encap:Ethernet HWaddr 00:60:97:C4:FB:97 > > inet addr:202.190.130.195 Bcast:202.190.130.199 > > Mask:255.255.255.248 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:12722 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:12388 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:1 txqueuelen:100 > > Interrupt:5 Base address:0xe400 > > > > eth1 Link encap:Ethernet HWaddr 00:60:08:91:B1:C5 > > inet addr:100.100.100.150 Bcast:100.100.100.255 > > Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:16211 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:17041 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:712 txqueuelen:100 > > Interrupt:9 Base address:0xe800 > > > [CHEONG, Shu Yang (Patrick)] Something wrong here...there are too > many collisions. Have you checked to ensure there are no boxes on network > sharing the same ip address? Also you mentioned that you can "see" one > network if you disable the other?! This could mean that there is a > conflict > between the ethernet cards... > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:3924 Metric:1 > > RX packets:2494 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:2494 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > > > $ > > $ /sbin/route > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref Use > > Iface > > tiger.first.com * 255.255.255.255 UH 0 0 0 > > eth0 > > 100.100.100.150 * 255.255.255.255 UH 0 0 0 > > eth1 > > 202.190.130.192 * 255.255.255.248 U 0 0 0 > > eth0 > > 100.100.100.0 * 255.255.255.0 U 0 0 0 > > eth1 > > 127.0.0.0 * 255.0.0.0 U 0 0 0 > lo > > default 202.190.130.193 0.0.0.0 UG 0 0 0 > > eth0 > > $ > > > > > > --->>> Colleague's system > > > > [EMAIL PROTECTED] jeffrey]$ /sbin/ifconfig > > eth0 Link encap:Ethernet HWaddr 00:80:C8:FB:17:4B > > inet addr:202.190.130.196 Bcast:202.190.130.199 > > Mask:255.255.255.248 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:30323 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:4938 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:100 > > Interrupt:10 Base address:0xec80 > > > > eth1 Link encap:Ethernet HWaddr 00:60:97:C2:D3:DA > > inet addr:100.100.100.111 Bcast:100.100.100.255 > > Mask:255.255.255.0 > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > RX packets:69983 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:11276 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:6 txqueuelen:100 > > Interrupt:11 Base address:0xef00 > > > > lo Link encap:Local Loopback > > inet addr:127.0.0.1 Mask:255.0.0.0 > > UP LOOPBACK RUNNING MTU:3924 Metric:1 > > RX packets:32 errors:0 dropped:0 overruns:0 frame:0 > > TX packets:32 errors:0 dropped:0 overruns:0 carrier:0 > > collisions:0 txqueuelen:0 > > > > [EMAIL PROTECTED] jeffrey]$ > > > > [EMAIL PROTECTED] jeffrey]$ /sbin/route > > Kernel IP routing table > > Destination Gateway Genmask Flags Metric Ref Use > > Iface > > penguin.first.c * 255.255.255.255 UH 0 0 0 > > eth0 > > 100.100.100.111 * 255.255.255.255 UH 0 0 0 > > eth1 > > 202.190.130.192 * 255.255.255.248 U 0 0 0 > > eth0 > > 100.100.100.0 * 255.255.255.0 U 0 0 0 > > eth1 > > 127.0.0.0 * 255.0.0.0 U 0 0 0 > lo > > default 202.190.130.193 0.0.0.0 UG 0 0 0 > > eth0 > > [EMAIL PROTECTED] jeffrey]$ > > > > > > Thanks in advance. > > > > Saranjit Singh, > > > > > > > > -- > > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < > > /dev/null > > > -- > Unsubscribe? mail -s unsubscribe [EMAIL PROTECTED] < > /dev/null
