Very Computer

This may not be the most appropriate newsgroup, please let me know if
there's a better choice.  I know it's not a Linux question.

I've got an Ascend Pipeline 25 ISDN router.  The last couple of days I
have noticed a strange kind of activity on it.  When nothing should be
going on (no Netscape, no sendmail daemon, no lost ping command
running away), the WAN status window shows a constant stream of
packets going in and out, about one per second.  The Ether status
window shows no activity.  It's as if someone is pinging my router.
Naturally enough the darned ISDN line stays connected, running up my
meter.  Disconnecting the Ethernet line to the computer has no effect,
as I expected, but disconnect the ISDN line stops the process, and it
does not resume once the ISDN side reinits.

1.  Does anybody have any experience with a similar aituation?

2.  Other than bringing a packet sniffer home from work, is there any
way to find out what is in these packets?

--
     ... _._. ._ ._. . _._. ._. ___ .__ ._. . .__. ._ .. ._.

     PGP = 9D 93 1E 78 5B D7 42 1C   95 4E 9E DD 3F 6F 21 98
I've found a solution to Fermat's Last Theorem but I see I've run out of room o

Quote:>This may not be the most appropriate newsgroup, please let me know if
>there's a better choice.  I know it's not a Linux question.

>I've got an Ascend Pipeline 25 ISDN router.  The last couple of days I
>have noticed a strange kind of activity on it.  When nothing should be
>going on (no Netscape, no sendmail daemon, no lost ping command
>running away), the WAN status window shows a constant stream of
>packets going in and out, about one per second.  The Ether status
>window shows no activity.  It's as if someone is pinging my router.
>Naturally enough the darned ISDN line stays connected, running up my
>meter.  Disconnecting the Ethernet line to the computer has no effect,
>as I expected, but disconnect the ISDN line stops the process, and it
>does not resume once the ISDN side reinits.

>1.  Does anybody have any experience with a similar aituation?

>2.  Other than bringing a packet sniffer home from work, is there any
>way to find out what is in these packets?

Debug option to display packets that cause unwanted dial-outs
Display packets as an aid to writing filters. Anew debug option captures and
displays packets that cause the Ascend unit to dial out when a connection is
not needed. You can then get the information you need to write a filter that
prevents the packet from bringing up a connection.

This enhancement adds the wan-data dial-out (wdDialout) option to the debug
monitor. This option enables you to display a packet that caused an unwanted
dial-out session. When packets are not captured If a dial-out is initiated for
any of the following reasons, the wdDialout option does not capture a
packet:Dial-out caused by the Ctrl-D user commandDial-out caused by callback
securityDial-out on nailed channelsDial-out caused by NAT (Network Access
Translation) acquiring an IP addressDial-out initiated for IP over X.25, when
the X.25 internet profile changes to active and there is data waiting for X.25
to bring up the connectionDial-out caused by IGMP (Internet Group Management
Protocol) multicast forwardingDial-out to acquire a DNS address during PPP
negotiationsDial-out in response to a DHCP Discover messageDial-out caused by
the Ascend unit sending a DHCP packet for DHCP client processingDial-out caused
in response to an APP (Ascend Password Protocol) Connect Request message.

Turning on the debug option
1 Enter the debug mode by quickly typing:
Esc [ Esc =
2 At the ">" prompt type:
help ascend
you should see the wdDialout option listed. By default, the option is turned
off.
3 To turn the option on, type:
wdDialout
WANDATA dialout display is ON
This is a toggle command. Typing it again turns the option off. See the next
section for details on how packets are displayed in the debug monitor.
4 To exit the debug mode and return to the VT-100 interface, type quit.
Displaying packets
You can view wdDialout displays in the debug monitor. This section shows
several examples.

Quote:>>I've got an Ascend Pipeline 25 ISDN router.  The last couple of days I
>>have noticed a strange kind of activity on it.  When nothing should be
>>going on (no Netscape, no sendmail daemon, no lost ping command
>>running away), the WAN status window shows a constant stream of
>>packets going in and out, about one per second.  The Ether status
>>window shows no activity.  It's as if someone is pinging my router.
>>Naturally enough the darned ISDN line stays connected, running up my
>>meter.  Disconnecting the Ethernet line to the computer has no effect,
>>as I expected, but disconnect the ISDN line stops the process, and it
>>does not resume once the ISDN side reinits.

Read in your Pipeline manual the section on filters, and set up their sample
one (which simply filters out broadcasts).  I don't have my Pipeline manual at

numbers.  The WAN light IS real, and you're running up phone charges.