Your message dated Tue, 24 Jun 2008 22:51:19 +0200
with message-id <[EMAIL PROTECTED]>
and subject line Re: Bug#487883: network/interfaces should support multi-link 
ppp
has caused the Debian Bug report #487883,
regarding network/interfaces should support multi-link ppp
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [EMAIL PROTECTED]
immediately.)


-- 
487883: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487883
Debian Bug Tracking System
Contact [EMAIL PROTECTED] with problems
--- Begin Message ---
Package: ppp
Version: 2.4.4

ppp network interface configuration scripts should support multi-link
ppp. Multilink ppp is achieved by created two peers files, and starting
both, including multilink in their file. The daemons communicate and
join the same multilink group.

network/interfaces should probably support this by including multiple
"providers" lines, or multiple names per provider line. Each of these
would then be started in order, perhaps waiting for a successful
connection on both before proceeding.

As of now, pon is invoked with two arguments, the second of which
becomes an argument to the first pppd instance. This might also be
solved by making pon accept a compound first argument:  pon "peer1
peer2" <args>, and having the provider line parsed to accomplish this.

There are a few ways to skin this cat. Suggestions?




--- End Message ---
--- Begin Message ---
On Jun 24, Jerome Haltom <[EMAIL PROTECTED]> wrote:

> network/interfaces should probably support this by including multiple
Not my package, anyway.

> There are a few ways to skin this cat. Suggestions?
iface ... inet ppp
        ...
        up pon whatever

-- 
ciao,
Marco

Attachment: signature.asc
Description: Digital signature


--- End Message ---

Reply via email to