Dont know why its doing this. Maybe someone with more knowledge than I can finger it out.
On Star Date Monday 20 October 2003 02:50 pm, Brett W Tippet sent this sub-space message. > Hi bill .. > > I got this .. > > [EMAIL PROTECTED] brett]# chkconfig --list > alsa 0:off 1:off 2:on 3:on 4:on 5:on 6:off > dm 0:off 1:off 2:off 3:off 4:off 5:on 6:off > kheader 0:off 1:off 2:on 3:on 4:off 5:on 6:off > keytable 0:off 1:off 2:on 3:on 4:on 5:on 6:off > netfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off > network 0:off 1:off 2:on 3:on 4:on 5:on 6:off > partmon 0:off 1:off 2:off 3:on 4:on 5:on 6:off > random 0:off 1:off 2:on 3:on 4:on 5:on 6:off > rawdevices 0:off 1:off 2:off 3:on 4:on 5:on 6:off > sound 0:off 1:off 2:on 3:on 4:on 5:on 6:off > saslauthd 0:off 1:off 2:on 3:on 4:on 5:on 6:off > syslog 0:off 1:off 2:on 3:on 4:on 5:on 6:off > crond 0:off 1:off 2:on 3:on 4:on 5:on 6:off > portmap 0:off 1:off 2:off 3:on 4:on 5:on 6:off > xinetd 0:off 1:off 2:off 3:on 4:on 5:on 6:off > xfs 0:off 1:off 2:on 3:on 4:on 5:on 6:off > switchprofile 0:off 1:off 2:off 3:on 4:on 5:on 6:off > httpd 0:off 1:off 2:off 3:on 4:on 5:on 6:off > postfix 0:off 1:off 2:on 3:on 4:on 5:on 6:off > named 0:off 1:off 2:off 3:on 4:on 5:on 6:off > linuxconf 0:off 1:off 2:on 3:on 4:on 5:on 6:off > harddrake 0:off 1:off 2:off 3:on 4:on 5:on 6:off > nfslock 0:off 1:off 2:off 3:on 4:on 5:on 6:off > apmd 0:off 1:off 2:on 3:on 4:on 5:on 6:off > atd 0:off 1:off 2:off 3:on 4:on 5:on 6:off > devfsd 0:off 1:off 2:on 3:on 4:on 5:on 6:off > yppasswdd 0:off 1:off 2:on 3:on 4:on 5:on 6:off > lisa 0:off 1:off 2:off 3:on 4:on 5:on 6:off > numlock 0:off 1:off 2:off 3:on 4:on 5:on 6:off > nfs 0:off 1:off 2:off 3:on 4:on 5:on 6:off > sshd 0:off 1:off 2:on 3:on 4:on 5:on 6:off > vncserver 0:off 1:off 2:off 3:off 4:off 5:off 6:off > ypserv 0:off 1:off 2:on 3:on 4:on 5:on 6:off > ypxfrd 0:off 1:off 2:on 3:on 4:on 5:on 6:off > smb 0:off 1:off 2:off 3:on 4:off 5:on 6:off > proftpd 0:off 1:off 2:off 3:on 4:on 5:on 6:off > webmin 0:off 1:off 2:on 3:on 4:on 5:on 6:off > internet 0:off 1:off 2:off 3:on 4:off 5:on 6:off > iptables 0:off 1:off 2:on 3:on 4:on 5:on 6:off > ip6tables 0:off 1:off 2:on 3:on 4:on 5:on 6:off > xinetd based services: > chargen-udp: off > chargen: off > daytime-udp: off > daytime: off > echo-udp: off > echo: off > services: off > servers: off > time-udp: off > time: off > linuxconf-web: off > xadmin: off > fam: on > sshd-xinetd: off > rsync: off > proftpd-xinetd: off > > I stopped iptables and also ip6tables .. restarted the network .. same > thing going on .. > > Another thing to note ... a ping from the machine that's failing with > result in a reply from it's own NIC IP of destination unreachable .. any > help? .. > > Thanks, > Brett. > > > ----- Original Message ----- > From: "Bill" <[EMAIL PROTECTED]> > To: <[EMAIL PROTECTED]> > Sent: Monday, October 20, 2003 5:30 PM > Subject: Re: [expert] ip addressing on lan > > > Man that sure sounds like a firewall issue. Something is teling the card > > to > > > drop all output packets. > > > > You can look and see if you have iptables or shorewall running by logging > > in > > > as root thrrough a terminal and then do a chkcoonfig --list it will show > > you > > > what is running. Look for iptables or shorewall and then use the > > chkconfig command to change that run level to off for that daemon. then > > shutdown > > that > > > daemon by issueing the /etc/rc.d/init.d/(whateverdaemonis running)stop > > > > You may end up doing a /etc/rc.d/init.d/network restart > > > > If you want you can paste the output from chkconfig --list for us to see > > what > > > is running. > > > > There is the internet connections command try as root > > /etc/rc.d/init.d/internet start > > > > > > > > On Star Date Sunday 19 October 2003 10:56 pm, Brett W Tippet sent this > > sub-space message. > > > > > Cool .. > > > > > > I just did that .... > > > > > > The RX and TX didn't increase ... but the "dropped" went up to 300. > > > > > > Still got me confused, because I've tried 3 cards that r doing the same > > > thing. > > > > > > Brett. > > > > > > > > > ----- Original Message ----- > > > From: "Bill" <[EMAIL PROTECTED]> > > > To: <[EMAIL PROTECTED]> > > > Sent: Monday, October 20, 2003 3:49 PM > > > Subject: Re: [expert] ip addressing on lan > > > > > > > Notice the TX and RX packets for eth0 in the output from the ifconfig > > > > command. They show 0. Try pinging 192.168.0.200 and see if they > > increase > > > > or > > > > > > > not. There may be an issue with the card. Check that the link lite is > > on, > > > > on > > > > > > > that card by looking at the rear of your pc. > > > > > > > > On Star Date Sunday 19 October 2003 09:29 pm, Brett W Tippet sent > > > > this sub-space message. > > > > > > > > > Thanks to all who have replied to this issue so far .. > > > > > > > > > > Unfortunatelly, I'm still up the putt. > > > > > > > > > > Here's the output of my configs below. > > > > > > > > > > Someone suggested I may have a config issue with shorewall .. but I > > > > > > don't > > > > > > > > have an /etc/shorewall .. so I assume this isn't going to be a > > cause. > > > > > > This all looks fine to me? ... > > > > > > > > > > To ensure it's not a cable issue, I have ran x-over cable direct to > > the > > > > box > > > > > > > > and the NIC lights up and does all that stuff .. but I can't ping > > > > > or > > > > > > telnet > > > > > > > > to either machine .. help please! > > > > > > > > > > Brett. > > > > > > > > > > [EMAIL PROTECTED] brett]# route -n > > > > > Kernel IP routing table > > > > > Destination Gateway Genmask Flags Metric Ref Use Iface > > > > > 192.168.0.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 > > > > > 0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0 > > > > > [EMAIL PROTECTED] brett]# ifconfig > > > > > eth0 Link encap:Ethernet HWaddr 00:40:95:30:3B:9E > > > > > inet addr:192.168.0.200 Bcast:192.168.0.255 Mask:255.255.255.0 > > > > > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > > > > > RX packets:0 errors:0 dropped:0 overruns:0 frame:0 > > > > > TX packets:0 errors:0 dropped:0 overruns:0 carrier:0 > > > > > collisions:0 txqueuelen:100 > > > > > RX bytes:0 (0.0 b) TX bytes:0 (0.0 b) > > > > > Interrupt:18 Base address:0x1000 > > > > > 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:321 errors:0 dropped:0 overruns:0 frame:0 > > > > > TX packets:321 errors:0 dropped:0 overruns:0 carrier:0 > > > > > collisions:0 txqueuelen:0 > > > > > RX bytes:28032 (27.3 Kb) TX bytes:28032 (27.3 Kb) > > > > > [EMAIL PROTECTED] brett]# > > > > > > > > > > > > > > > > > > > > ----- Original Message ----- > > > > > From: "KevinO" <[EMAIL PROTECTED]> > > > > > To: <[EMAIL PROTECTED]> > > > > > Sent: Friday, October 17, 2003 9:09 PM > > > > > Subject: Re: [expert] ip addressing on lan > > > > > > > > > > > -----BEGIN PGP SIGNED MESSAGE----- > > > > > > Hash: SHA1 > > > > > > > > > > > > Bill wrote: > > > > > > > You may also have a net mask wrong on one of the units. > > > > > > > > > > > > > > A little more info would be helpful. From a term screen type > > > > > > > the command ifconfig and paste the info you get as well as the > > results > > > > from > > > > > > > > > > the > > > > > > > > > > route -n > > > > > > > > > > > > command to the email. > > > > > > > > > > > > It would be good to also see the contents of the following files: > > > > > > > > > > > > /etc/sysconfig/network > > > > > > /etc/sysconfig/network-scripts/ifcfg-eth0 > > > > > > > > > > > > This is where the network settings are stored. The GATEWAY > > > > > > setting > > is > > > > in > > > > > > > > the > > > > > > > > > > > first file, the IP address, netmask, broadcast etc. are in > > > > > > ifcfg-eth0. > > > > > > It > > > > > > > > is > > > > > > > > > > > often easier and more reliable to just edit these files manually > > > > > > instead > > > > > > > > of > > > > > > > > > > > using a wizard. > > > > > > > > > > > > Doing a: > > > > > > > > > > > > # service network restart > > > > > > > > > > > > should make your changes take effect. > > > > > > > > > > > > Use ifconfig to make sure the NIC is up and has the right IP, > > etc.. > > > > > > > - -- > > > > > > KevinO > > > > > > > > > > > > If Microsoft built cars, If you were involved in a crash, you > > would > > > > have > > > > > > > > > no idea what happened. > > > > > > -----BEGIN PGP SIGNATURE----- > > > > > > Version: GnuPG v1.0.7 (GNU/Linux) > > > > > > Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org > > > > > > > > > > > > iD8DBQE/j83QWOfRC7Rnmv8RAvANAJ0SJV7zmdbpM4xldLNJCOzpvpD1EgCfXKAX > > > > > > I0HJ3TIVyor091idCfuxZ+4= > > > > > > =BeR0 > > > > > > -----END PGP SIGNATURE----- > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > Want to buy your Pack or Services from MandrakeSoft? > > > > > > Go to http://www.mandrakestore.com > > > > ------------------------------------------------------------------------- > >- > > - > > > >- ---- > > > > > > > Want to buy your Pack or Services from MandrakeSoft? > > > > Go to http://www.mandrakestore.com > > > > Want to buy your Pack or Services from MandrakeSoft? > > Go to http://www.mandrakestore.com
Want to buy your Pack or Services from MandrakeSoft? Go to http://www.mandrakestore.com
