Re: syslog problems
On Fri, 15 Aug 2003, Andrew Haskell wrote: I'm having an odd problem with the syslog. I'm trying to log messages from a cisco 2600 series router. I'm already logging messages from a PIX and that works fine. Using a packet sniffer I can see the upd packets going from the router to the linux box, but once they hit the linux box they just vanish. In a week I've had 1 entry into the 2600.log file. To check that the 2600.log actually logs data i've used *.* /var/log/2600.log and it logs entries as expected, well everything but the 2600 messages. syslog.conf entries of the two cisco devices local4.* /var/log/PIX.log local5.* /var/log/2600.log I've set the 2600 to use faciltiy local5 and using a syslog on another machine I can recieve the log messages that I'm expecting. But I get nothing on the linux machine. I know the udp packet are getting their, and that syslog is setup to listen on port 514/udp and it is listening (the pix.log entry works). Has anyone ever experienced anything similar? or does anyone have an idea on whats going wrong? If you've not had an answer to this yet then... Have you tried applying -r to syslog when it starts? In /etc/sysconfig/syslog ___ Seawolf-list mailing list [EMAIL PROTECTED] https://www.redhat.com/mailman/listinfo/seawolf-list
Re: unsubscribe
On Tue, 8 Oct 2002, Michael Tiernan wrote: I used to run a set of mailing lists. I always find it very disheartening when supposedly smart people can't figure out the most basic concept of mailinglist operation. Much less, this guy's supposed to be the CTO of this food company. Wow. I think your attribution is one level removed, but no matter. Take a look at the shark tank to see some more real examples of CTO's. Warning, the website can be somewhat addicting. http://www.computerworld.com/departments/opinions/sharktank/ ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: ssh closing down connection immediately
Another arbitrary guess. Does the remote user have a valid shell? ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: ssh closing down connection immediately
On 11 Dec 2001, Oleg Goldshmidt wrote: Keith Morse [EMAIL PROTECTED] writes: Another arbitrary guess. Does the remote user have a valid shell? # grep oleg /etc/passwd oleg:x:500:500:Oleg Goldshmidt:/home/oleg:/bin/bash # /bin/bash --version GNU bash, version 2.04.21(1)-release (i386-redhat-linux-gnu) Copyright 1999 Free Software Foundation, Inc. Egad, Oleg. You may forced to sacrifice these systems to the Gods of Binary and Silicon. For your comparision also, a tail of a ssh -v -v -v remotehost with dsa key. Yours continues at the line: debug1: channel 0: open confirm rwindow 0 rmax 32768 where mine just dumps to the shell. Maybe its time to go talk to the openssh developers? --- debug1: ssh-userauth2 successful: method publickey debug3: clear hostkey 0 debug3: clear hostkey 1 debug3: clear hostkey 2 debug1: channel 0: new [client-session] debug1: channel_new: 0 debug1: send channel open 0 debug1: Entering interactive session. debug2: callback start debug1: client_init id 0 arg 0 debug2: tty_make_modes: ospeed 38400 debug2: tty_make_modes: ispeed 38400 debug2: tty_make_modes: 1 3 debug2: tty_make_modes: 2 28 debug2: tty_make_modes: 3 127 debug2: tty_make_modes: 4 21 debug2: tty_make_modes: 5 4 debug2: tty_make_modes: 6 0 debug2: tty_make_modes: 7 0 debug2: tty_make_modes: 8 17 debug2: tty_make_modes: 9 19 debug2: tty_make_modes: 10 26 debug2: tty_make_modes: 12 18 debug2: tty_make_modes: 13 23 debug2: tty_make_modes: 14 22 debug2: tty_make_modes: 18 15 debug2: tty_make_modes: 30 0 debug2: tty_make_modes: 31 0 debug2: tty_make_modes: 32 0 debug2: tty_make_modes: 33 0 debug2: tty_make_modes: 34 0 debug2: tty_make_modes: 35 0 debug2: tty_make_modes: 36 1 debug2: tty_make_modes: 37 0 debug2: tty_make_modes: 38 1 debug2: tty_make_modes: 39 0 debug2: tty_make_modes: 40 0 debug2: tty_make_modes: 41 0 debug2: tty_make_modes: 50 1 debug2: tty_make_modes: 51 1 debug2: tty_make_modes: 52 0 debug2: tty_make_modes: 53 1 debug2: tty_make_modes: 54 1 debug2: tty_make_modes: 55 1 debug2: tty_make_modes: 56 0 debug2: tty_make_modes: 57 0 debug2: tty_make_modes: 58 0 debug2: tty_make_modes: 59 1 debug2: tty_make_modes: 60 1 debug2: tty_make_modes: 61 1 debug2: tty_make_modes: 62 0 debug2: tty_make_modes: 70 1 debug2: tty_make_modes: 71 0 debug2: tty_make_modes: 72 1 debug2: tty_make_modes: 73 0 debug2: tty_make_modes: 74 0 debug2: tty_make_modes: 75 0 debug2: tty_make_modes: 90 1 debug2: tty_make_modes: 91 1 debug2: tty_make_modes: 92 0 debug2: tty_make_modes: 93 0 debug1: Requesting X11 forwarding with authentication spoofing. debug1: channel request 0: shell debug2: callback done debug1: channel 0: open confirm rwindow 0 rmax 32768 debug2: channel 0: rcvd adjust 16384 Last login: Wed Dec 11 11:50:54 2024 from remotehost.domainname.com sh: /usr/X11R6/bin/xauth: No such file or directory ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: ssh closing down connection immediately
On 10 Dec 2001, Oleg Goldshmidt wrote: Just in case it might help, here is the (not commented part of) /etc/ssh/sshd_config on the problematic server: You've certainly got my interest now. The parameters in sshd_config you posted appear to match my stock one on RH7.2 box (sans commented lines). Looking at your dump (ssh -v) from a previous message, I noticed that the session appears to be authenticating via RSA. I'm also guessing you use ssh-agent as the auth method was public key. So based on that You might try the ssh -v -v -v host and post it's dump to the list. and you might try deleting the RSA key pair and generating a new one and push the public key back to the server. even better generate a DSA key pair and push it's public key to the server. ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: question about mkpasswd
On Sat, 17 Nov 2001, Aaron Konstam wrote: Would anyone confirm that the command: mkpasswd usrid will not change the passwd on a server using NIS to distribute passwords? I will take denials or any advice also. Aaron, did you ever find the answer to this question? ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: question about mkpasswd
On Sat, 17 Nov 2001, Aaron Konstam wrote: Would anyone confirm that the command: mkpasswd usrid will not change the passwd on a server using NIS to distribute passwords? I will take denials or any advice also. AFAIK, mkpasswd is only a generator of random strings of text, 9 characters in length. Oops, just took a look at the man page. Didn't know you change the user's password too. Hmmm. No references to NIS in the man page either. Looks like you'd have to use yppasswd to update NIS password, but it also might depend on the actual NIS password map file. If it's /etc/passwd, I would suspect of being updated if mkpasswd is run on the NIS master. Hopefully an NIS guru will confirm/deny these allegations. ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: x-win ...
On Sun, 18 Nov 2001, Jan Carlson wrote: On Sun, Nov 18, 2001 at 01:30:18AM +0200, zpetar wrote: off-topic ... bu what X-win emulator/program to use with NT 4.0 to connect RH 7.2 X-win ... Starnet X is good, from www.starnet.com. It used to have a free demo version too. Come, come, people. www.cygwin.com's cygwin and using XFree86 freely available and owned by the same company as this list. ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: Routing problem with RH 7.1
On Wed, 17 Oct 2001, Jesus Enciso wrote: Hi friends, i´ve the follow network: || (private ip´s) || (private ip´s ) INTERNET -||//...---||-|--| eth0| 1 |eth1 wireless eth1| 2 |eth0 | |. || connection || |--| Linux withLinux PC´s NAT and Masq. ip forward enabled ip forward enabled route add default gw(eth1 from linux 1) ifconfig and netstat -rn go along way to helping you with this situation. Does Linux1 know about the ip subnet attached to Linux2's eth0? ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: REdhat 7.2
On Tue, 9 Oct 2001, J. Dow wrote:
From: Bill Crawford [EMAIL PROTECTED]
Hey Trond,
Do you have this set up as an automated responce based on certain phrases
in the body or the subject of the message? Just a thought. Might save
you some typing. :-)
Easy way to find out ...
--- BEGIN teg script detection trigger block v0.1 ---
When ... Red Hat ... 7.2 ... or 8 or whatever ... release ... name ...
END teg script detection trigger block v0.1
It's more sophisticated than that. It happens once a day with a random
delay after passing 24 hours since the last posting. You think Trond is
an amateur or something?
{O,o}
Snicker, snicker, snort. Every time I see the post I reminded of the
Navy's stock disclaimer when I was stationed aboard the submarine. We
neither confirm nor deny the presence of nuclear weapons aboard this
vessel.
___
Seawolf-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: Strange SSHd issue
On Mon, 24 Sep 2001, Trevor Antczak wrote: [major snippage] Could you report the ssh versions on both hosts? And a ssh -v username@hostname would be helpful. ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: PCMCIA troubles
On Fri, 14 Sep 2001, gogi m wrote: hy all, i got BIG problems to gettng work my ISA-PCMCiA card Wavelan Silver Card. On my old RH6.2 work ok (ISA-PCMCIA) but here on my new R7.1 were is (PCI-PCMCIA) kernel 2.4.2 or 2.4.3 doesnt work. Got troubles with modules. here are mine logs: i dont have kernel-pcmcia-cs packet installed! I got new pcmcia-cs and compiled in. Sorry can't make sense out of the above. I's suggest getting the pcmcia-cs package (tarball) from sourceforge.net that matches the instance on your redhat distribution. For RH 7.1 I believe its 3.1.24. Then if have not already. go to www.agere.com and retrieve the newest linux driver, again it is a gzipped tarball (WLLI610.TGZ) I tend to do this stuff in /usr/src. So: cd /usr/src tar zxvf ~/pcmcia-cs-3.1.24.tar.gz mkdir wavelan cd wavelan tar zxvf ~/WLLI610.TGZ cd .. less README.wavelan2_cs and this really a case of RTFM. The README.wavelan2_cs is quite good at getting you thru the process of building the wavelan2_cs.o. Which I believe is your problem below. BTW, where did you get the wavelan2_cs.o used below? I try insmod wavelan2_cs and i get: /lib/modules/2.4.3-12/pcmcia/wavelan2_cs.o: unresolved symbol register_pccard_driver /lib/modules/2.4.3-12/pcmcia/wavelan2_cs.o: unresolved symbol unregister_pccard_driver Note: /etc/module.conf is more recent than /lib/modules/2.4.3-12/module.dep /lib/modules/2.4.3-12/pcmcia/wavelan2_cs.o: insmod /lib/modules/2.4.3-12/pcmcia/wavelan2_cs.o ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: Announcing a beta release of Red Hat Linux: Roswell
On Fri, 3 Aug 2001, Jack Bowling wrote: ** Reply to message from Keith Morse [EMAIL PROTECTED] on Fri, 3 Aug 2001 12:39:39 -0700 (PDT) On Fri, 3 Aug 2001, Glen Lee Edwards wrote: Wow, I just tried to check into this non-existent release - Roswell, and my browser crashed. Yikes! Glen Yeah, and none of my posts to roswell-list make it, weird. Do you have ECN turned on? I imagine most redhat servers are now ECN enabled. jack Jack Bowling mailto: [EMAIL PROTECTED] Uuu, I was just having fun. You know Roswell, things you don't see happen. Things you see aren't acknowledged. It was in spirit of the original posting by Mr. Nottingham. A bit too subtle perhaps. ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Using a different boot image when installing from cd
An odd question, certainly. Is it possible to use a different image when booting from an install cd than the one that is defaulted. I'm assuming that boot.img is the stock kernel image utilized by the cd on a cdrom installation. Can you specify at the lilo : prompt a different such as bootnet.img. It is on the cd, in /images. The reason I ask is I'm stuck without a floppy currently and the second cd looks like it has stress patterns in it and won't mount when anaconda asks for the second disk during the packages installation. I do have access to a anonymous ftp server which contains the complete seawolf installation. ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: Announcing a beta release of Red Hat Linux: Roswell
On Fri, 3 Aug 2001, Glen Lee Edwards wrote: Wow, I just tried to check into this non-existent release - Roswell, and my browser crashed. Yikes! Glen Yeah, and none of my posts to roswell-list make it, weird. ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: ntp setup for a local server and a few clients to that server
On Mon, 30 Jul 2001, Christopher Keller wrote: On 30 Jul 2001 20:43:37 -0500, Charles R. Tersteeg wrote: I've read over the ntp howto and a few other articles about ntp and i'm confused as LL. To setup ntp on a 7.1 box...funny i just did this on my home machine yesterday. $ chkconfig ntpd on $ echo -e clock.isc.org\nclock.via.net\ngpstime.trimble.com /etc/ntp/step-tickers $ service ntpd start That's it. I just chose these three servers because of proximity. Here is a list of level 1 NTP public servers; jsut pick a couple near you. If DNS doesn't work, you should use IP's instead. http://www.eecis.udel.edu/~mills/ntp/clock1.htm --Chris A couple o' nits that I've developed whilst watching messages about setting up ntp. I would hesitate recommending level 1 servers. Personally I try to find level 2 or 3 servers for service. Also you might ask your ISP if you can point to their time server, assuming they maintain one. Geographically, (or rather network topoligically) close is bestest. Traceroute can help you there. Three servers is what I remember being recommended. Somewhat GPS, the more sources you have, the more accurate the time and redundancy will be assured. ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
Re: AW: openssh problem
On Wed, 25 Jul 2001, Rolf Trinoga wrote: I just noticed that the remote computer was not configured with OpenSSH. I removed the version and installed openssh - the result is the same: You'll need to post your sshd_config. ___ Seawolf-list mailing list [EMAIL PROTECTED] https://listman.redhat.com/mailman/listinfo/seawolf-list
