On Wed, 2002-05-22 at 11:16, Ray Olszewski wrote:
> At 10:39 AM 5/22/02 -0700, Mike Noyes wrote:
> >[...]
> >I think you can stop logging of TOS redirects in network.config by
> >changing the option below to yes. This may open up a possible security
> >hole.
> >
> >ALLIF_ACCEPT_REDIRECTS=NO
>
> I
> >How does one go about unpacking that cryptic message from what looks like
> >Hex to get IP addresses?
>
> It is hex (that's why I prepended the 0x), and if you know enough to
> recognize it, the rest is easy to explain.
>
> >Separated into bytes, the address 42DA4753 becomes 42 DA 47 53
>
>
> N
At 01:14 PM 5/22/02 -0500, Omar D. Samuels wrote:
[...]
>There's just one question I have for MacGyver...
>
> > > > > May 22 02:53:54 NRP-413 kernel: Redirect from D08A145C/eth0 to
>D08A1401
> > > > > ignored.Path = D08A1469 -> 42DA4753, tos 00
> > >
> > > Unpacked, this says that the kernel is
At 10:39 AM 5/22/02 -0700, Mike Noyes wrote:
[...]
>Ray,
>Thanks for jumping in. :-)
>
>Would this account for the Martin messages he is receiving also?
Probably not. The only info I could find in his postings about Martians is
this:
>martian source bd69fea9 for fea9, dev eth1
>ll header: f
On Wed, 2002-05-22 at 10:39, Mike Noyes wrote:
> On Wed, 2002-05-22 at 10:18, Ray Olszewski wrote:
> > > > May 22 02:53:54 NRP-413 kernel: Redirect from D08A145C/eth0 to D08A1401
> > > > ignored.Path = D08A1469 -> 42DA4753, tos 00
> >
> > Unpacked, this says that the kernel is reporting that it
> Ray,
> Thanks for jumping in. :-)
>
> Would this account for the Martin messages he is receiving also?
>
> > If my guess is correct, -AND- if my assumption is correct that there is
no
> > actual service failure associated with these messages, then there are
two
> > courses of action:
> >
> >
On Wed, 2002-05-22 at 10:18, Ray Olszewski wrote:
> Before we keep asking for more and more info, perhaps we should look a bit
> at what we do know and interpret the actual report. As Michael correctly
> pointed out yesterday, the important log line is the one that preceded the
> "NET" line, an
Before we keep asking for more and more info, perhaps we should look a bit
at what we do know and interpret the actual report. As Michael correctly
pointed out yesterday, the important log line is the one that preceded the
"NET" line, and we're finally seeing it.
It reads:
> > May 22 02:53:5
> Omar,
> The whole unmodified contents would be useful. Long messages on a
> technical support list like this are acceptable. More information is
> better than less. Thanks. :-)
>
Ok, here goes:
###
# Brief instruction
On Wed, 2002-05-22 at 09:13, Omar D. Samuels wrote:
> > On Wed, 2002-05-22 at 08:42, Omar D. Samuels wrote:
> > > Hope this is what you were talking about:
> > >
> > > May 22 02:53:54 NRP-413 kernel: NET: 4 messages suppressed.
> > > May 22 02:53:54 NRP-413 kernel: Redirect from D08A145C/eth0 to D
> On Wed, 2002-05-22 at 08:42, Omar D. Samuels wrote:
> > I'm sorry, I just realised that my msgs weren't going thru because I had
> > these msgs as attachments, which I imagine needs to be moderator
approved.
>
> Omar,
> I'm the list admin. Attachments are rejected due to the amount of
> viruses
On Wed, 2002-05-22 at 08:42, Omar D. Samuels wrote:
> I'm sorry, I just realised that my msgs weren't going thru because I had
> these msgs as attachments, which I imagine needs to be moderator approved.
Omar,
I'm the list admin. Attachments are rejected due to the amount of
viruses circulating.
> Omar,
> Please post the diagnostic information requested by Michael. We should
> be able to determine the problem for you. Unfortunately, the information
> you've provided up to now is insufficient to troubleshoot the problem.
>
I also seem to get a lot of martian source messages, I shud prolly
I'm sorry, I just realised that my msgs weren't going thru because I had
these msgs as attachments, which I imagine needs to be moderator approved.
Hope this is what you were talking about:
May 22 02:53:54 NRP-413 kernel: NET: 4 messages suppressed.
May 22 02:53:54 NRP-413 kernel: Redirect from D
On Wed, 2002-05-22 at 08:07, Omar D. Samuels wrote:
> > Either way, as I have been insisting, you need to correct the root cause
> > of these symptomatic messages. What is the underlying cause?
> >
> To tell the truth, I'm not sure exactly what is the underlying cause.
Omar,
Please post the diag
- Original Message -
From: "Erich Titl" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, May 22, 2002 3:24 AM
Subject: Re: [leaf-user] A NET question
Hi
At 16:54 21.05.2002 -0700, you wrote:
>I'm gonna try commenting out the *.emerg l
- Original Message -
From: "Michael D. Schleif" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, May 21, 2002 7:10 PM
Subject: Re: [leaf-user] A NET question
>
> "Omar D. Samuels" wrote:
> >
> > Hey I stopped the sysklogd as w
> >
> > Hey I stopped the sysklogd as well as commented out the *.emerg * line
and
> > I still get those NET messages.
> > Any suggestions?
>
> ps aux | grep sys
>
> Do you have any running process like syslog? If yes, then you can kill
> it.
>
> If not, as I mentioned, these messages are genera
Hi
At 16:54 21.05.2002 -0700, you wrote:
>I'm gonna try commenting out the *.emerg line. Thanks again man.
>I'll definitely keep you posted.
I would not just comment it out but save the data in a file. See
syslog.conf(5) for an explanation of the syslog configuration file format.
Erich
THI
On Tue, 2002-05-21 at 16:10, Omar D. Samuels wrote:
> >
> > [ snip ]
> >
> > > > Bottomline, if you identify the root cause of this message flooding,
> > > > and correct it, then you will no longer witness these 'NET ...
> > > > suppressed' messages.
> >
> > Please, reconsider what I am saying in
"Omar D. Samuels" wrote:
>
> Hey I stopped the sysklogd as well as commented out the *.emerg * line and
> I still get those NET messages.
> Any suggestions?
ps aux | grep sys
Do you have any running process like syslog? If yes, then you can kill
it.
If not, as I mentioned, these mes
"Omar D. Samuels" wrote:
>
[ snip ]
> I think you are THE MAN! I really appreciate this man. I'm gonna give it a
> try. I don't want to really shut off syslog. The thing is I gotta get rid
> of those messages. The box needs to, when it is installed, just sit there,
> running maybe somethi
Hey I stopped the sysklogd as well as commented out the *.emerg * line and
I still get those NET messages.
Any suggestions?
- Original Message -
From: "Michael D. Schleif" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, May 21, 2002 5:51 PM
Subject:
>
> [ snip ]
>
> > > Bottomline, if you identify the root cause of this message flooding,
and
> > > correct it, then you will no longer witness these 'NET ... suppressed'
> > > messages.
>
> Please, reconsider what I am saying in the statement above. IMHO, that
> is really what you want to do . .
"Omar D. Samuels" wrote:
>
> - Original Message -
> From: "Michael D. Schleif" <[EMAIL PROTECTED]>
> >
> > "Omar D. Samuels" wrote:
> > >
> > > Now that I'm over that hurdle and I am getting more the hang of this
> mialing
> > > list, I would like to dare to ask for help with another iss
- Original Message -
From: "Michael D. Schleif" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, May 21, 2002 5:06 PM
Subject: Re: [leaf-user] A NET question
>
> "Omar D. Samuels" wrote:
> >
> > Now that I'm over tha
"Omar D. Samuels" wrote:
>
> Now that I'm over that hurdle and I am getting more the hang of this mialing
> list, I would like to dare to ask for help with another issue... please.
>
> I a using Eigerstein2... does anyone know if there is any way to suppress
> the NET messages? They look like
Now that I'm over that hurdle and I am getting more the hang of this mialing
list, I would like to dare to ask for help with another issue... please.
I a using Eigerstein2... does anyone know if there is any way to suppress
the NET messages? They look like this:
"NET: # messages suppressed"
I
On Tue, 2002-05-21 at 10:05, Omar D. Samuels wrote:
> Hey, guess what? I'm new to this whole LRP thing, I've been really trying
> to follow protocol in seeking help with these hiccups. My apologies if my
> descriptions are not a "distinct" and "exact" as you would like them to be.
> I am really
om: "Ray Olszewski" <[EMAIL PROTECTED]>
To: "Omar D. Samuels" <[EMAIL PROTECTED]>
Cc: <[EMAIL PROTECTED]>
Sent: Tuesday, May 21, 2002 11:50 AM
Subject: Re: [leaf-user] A NET question
> I added the LEAF list back in.
>
> At 11:26 AM 5/21/02 -0500, O
I added the LEAF list back in.
At 11:26 AM 5/21/02 -0500, Omar D. Samuels wrote:
>I'm pretty sure that I have the right cable but it just isn't working out,
>so I dunno if it is the machine's fault... even though the serial port
>initialized okay. Basically everything seems to be in order but
The documents that Mike referred you to do discuss cable issues, though
perhaps briefly enough that you missed it when you read them. To connect 2
computers, you need either a null-modem cable or a regular cable with a
null-modem adapter ... this is not a LEAF or even a Linux issue, but a
stan
have some more specific questions, please ask them...
Joey
Advocate in Training...
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]]On Behalf Of Omar D. Samuels
Sent: Tuesday, May 21, 2002 8:56 AM
To: [EMAIL PROTECTED]
Subject: [leaf-user] A NET question
Could so
On Tue, 2002-05-21 at 06:55, Omar D. Samuels wrote:
> I am trying just about everything I can find in documentation to allow my
> LRP (on a single floppy) to allow me to console into it through a serial
> cable. It is not working for me "echo "hello" > /dev/ttyS0" sends nothing
> to my Hypertermi
Could someone pleeez help me. I would really love some help with two
things:
Is there any way to suppress the "NET: # messages suppressed" messages that
come on my LRP box?
I am trying just about everything I can find in documentation to allow my
LRP (on a single floppy) to allow me to console
35 matches
Mail list logo
