apm + plip problem

Hello networkers,

I am using plip to connect my desktop PC with my notebook. If I don't start
the apmd on the notebook, everything works fine. If I start apmd on the
notebook, I cannot connect to it any more (even ping does not work). The
routing tables and network settings seem not to not change at all, no
messages in syslog either. However, I can still initiate connections from
the notebook to the desktop. After that, everything works in both
directions again.

I guess that the apmd somehow suspends the parallel port and activates it on
outgoing traffic, but not on incoming traffic. There are no options that
control the parallel port in any of the apm scripts. I am using debian
testing on both machines.

Any suggestions?

Thomas Boehne

On Tue, 13 Apr 2004 13:55:02 +0200, Thomas Boehne <tobox@gmx.de> wrote:
> Hello networkers,
>
> I am using plip to connect my desktop PC with my notebook. If I don't start
> the apmd on the notebook, everything works fine. If I start apmd on the
> notebook, I cannot connect to it any more (even ping does not work). The
> routing tables and network settings seem not to not change at all, no
> messages in syslog either. However, I can still initiate connections from
> the notebook to the desktop. After that, everything works in both
> directions again.
>
> I guess that the apmd somehow suspends the parallel port and activates it on
> outgoing traffic, but not on incoming traffic. There are no options that
> control the parallel port in any of the apm scripts. I am using debian
> testing on both machines.

It depends what you are doing with apmd. If your laptop goes into
suspend it maintains RAM, but cpu goes to low power and may not respond
to network. So it is best to set apmd NOT to suspend when on AC power.

In fact some network devices will not respond at all when reawakening from
suspend. So for pcmcia nics, it is sometimes necessary to configure apmd
to restart pcmcia when it resumes.

--
David Efflandt - All spam ignored http://www.de-srv.com/

David Efflandt wrote:

> It depends what you are doing with apmd. If your laptop goes into
> suspend it maintains RAM, but cpu goes to low power and may not respond
> to network. So it is best to set apmd NOT to suspend when on AC power.

The problem also occurs if the laptop is on AC power all the time. I removed
all apmd-scripts to make sure that apmd is not manipulating the network
devices at all. The problem also occurs if I keep working on the machine
(thus, the CPU should not be in low power mode). It's a 486 which AFAIK
does not even have a low power mode.

Thomas