Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

(ASCEND) P75 syslog filter ??

On Sun, 18 Jan 1998 06:25:26 GMT, you spewed forth the following:

>
>Thanx, I now can get syslog to work, but it keeps the connection permanantly
>active now :-( Do you have a call filter suggestion? Here is the wdDialout debug
>data dump...
>
>>>>
>Cause an attempt to place call to 14082898233
>WD_DIALOUT_DISP: chunk 26AEEE type IP.
>(task: 26B090, time: 1609.31) 44 octets @ 2A9630
>  [0000]: 00 C0 7B 71 BF F5 00 40 05 31 FE F3 08 00 45 00 
>  [0010]: 00 2C 24 19 40 00 20 06 80 EA C0 A8 64 69 CF AB 
>  [0020]: C1 0B 05 52 00 6E 02 0E 23 30 00 00 
>  Date: 01/01/1990.	Time: 00:28:05
>Cause an attempt to place call to 14082898233
>WD_DIALOUT_DISP: chunk 26AEEE type IP.
>(task: 26B090, time: 1685.07) 74 octets @ 2AFAB0
>  [0000]: 00 C0 7B 71 BF F5 00 40 05 31 FE F3 08 00 45 00 
>  [0010]: 00 4A 34 19 00 00 20 11 A1 C1 C0 A8 64 69 CF AB 
>  [0020]: D0 0B 05 57 00 35 00 36 44 24 00 2D 01 00 00 01 
>  [0030]: 00 00 00 00 00 00 03 31 30 30 03 31 30 30 03 31 
>  [0040]: 36 38 03 31 39 32 07 69 6E 2D 
> > wdDialout
>WANDATA dialout display is OFF
> > 
>
>The first entry is legit and the second is apparently caused by syslog because
>it does not happen with syslog disabled.
>

clip from your html attachment...

>Did you reset the Pipe after performing these changes? Or atleast flush the ARP 
>tables? I recall once I had a similar problem, and I _think_ it was related to the 
>ARP tables. 

I am not running ARP so this is not the trouble but I tried it anywaywith no
joy. I have no experience decoding these debug messages. Can you suggest a
resource either printed or otherwise?

>Check out this link for more detail about setting up the configuration we discussed. 
>Perhaps it will have a blurb about call filters. I just wish this page was around 5 
>months ago! ;)

I have looked at pretty much all the filter info on your web site and did a
DejaNews search as well. I can run no filter at all without syslog and no
troubles. Any time syslog messages are being generated AND "syslogd is actively
logging these messages" either in Win95 or Linux the link stays up for good. I
tried to insert a call filter to trap UDP port 514 but that was ineffective as
well?


Mark Moorcroft          sevenup@slip.net        KF6NTD
     Actual home             Silicon Valley
            Virtual home         www.slip.net/~sevenup
++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>
References: