headers
Paul Mackerras | 7 Sep 2008 08:40
Picon
Favicon

ppp-2.4.5 release imminent

I'm planning to release ppp-2.4.5 shortly.  What is in the release
will be what is in the master branch of the ppp git repository at

git://ozlabs.org/~paulus/ppp.git

(except I'll leave out the .gitignore files).

The changes are mostly bugfixes.  The new features are the ability to
operate without an IP address for the peer under Linux, and the
pppol2tp plugin.

Now would be a good time to try it out and let me know about any bugs.

Paul.
--
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 1 comment |
headers
James Chapman | 7 Sep 2008 22:58

Re: ppp-2.4.5 release imminent

Paul Mackerras wrote:
> I'm planning to release ppp-2.4.5 shortly.  What is in the release
> will be what is in the master branch of the ppp git repository at
> 
> git://ozlabs.org/~paulus/ppp.git
> 
> (except I'll leave out the .gitignore files).
> 
> The changes are mostly bugfixes.  The new features are the ability to
> operate without an IP address for the peer under Linux, and the
> pppol2tp plugin.
> 
> Now would be a good time to try it out and let me know about any bugs.

I just tested it in some L2TP test setups - looks good.

> 
> Paul.

--

-- 
James Chapman
Katalix Systems Ltd
http://www.katalix.com
Catalysts for your Embedded Linux software development

--
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lie Arne | 11 Sep 2008 09:35
Picon
Picon
Favicon

Packet drop with PPP and tty-driver

Hi,

We are using our custom tty-driver for communicating between an embedded
Linux processor and a DSP running modem software. 

The pppd is started by typing "pppd /dev/our_driver0". pppd opens this
driver in non-blocking mode. At write, when our write queue is full, we
return -EAGAIN. With low traffic there is no problem, but when load
increases above PPP-link capacity, the ppp subsystem begins to throw
packets. Still the communication link is working, but this situation
poses two problems:

1. If using PPP compression, packets drops inside PPP causes performance
drop because the compression algorithm has the be resynchronized.

2. The Linux networking code output queuing system sees the ppp0
interface as a very fast interface (instead of a slow one), preventing
Linux queue backlog to happen, and thus makes it impossible to have
prioritized queuing (e.g. PRIO/TBF or HTB supporting DiffServ) in front
of the ppp interface. 

We want the PPP-link to be reliable, and relying on the Linux network
code output queue to take care of traffic overload situations (with FIFO
tail drop or QoS supported drops, e.g.).

We would appreciate any help / suggestions for what could be wrong with
our implementation: what are we doing wrong?

Best regards,
(Continue reading)

Permalink | Reply | 0 comments |
headers
Lie Arne | 12 Sep 2008 16:44
Picon
Picon
Favicon

ppp XMIT_WAKEUP flag: who sets it?


 Hi,

We have now found a workaround for our problems with PPP dropping
packets:
1. Our tty driver now returns "0" to ppp_async_push() instead og
"-EAGAIN"
2. We had to modify the line 
"if (test_bit(XMIT_WAKEUP, &ap->xmit_flags) && ppp_async_push(ap)) { "
in ppp_async_process() to become:
"if (ppp_async_push(ap)) { "

since apparently no process/function in our system sets the XMIT_WAKEUP.
Can anybody tell us who is / should be responsible for setting this
flag?

Our workaround seems working stable though. :-) 

Best regards

Arne Lie
SINTEF ICT, Dept. of Communication Systems

e-mail: arne.lie <at> sintef.no 
--
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
(Continue reading)

Permalink | Reply | 0 comments |
headers
Joakim Wennergren | 17 Sep 2008 21:23
Picon

pppd creates route without "gateway" flag

I just looked at my routing table, and the route pppd created does not
have the "G" flag like I'm used to, is there a reason for this?

This is output from route:

# route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
10.64.64.64     0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 br0
0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 ppp0

It seems to work, I'm just wondering why? And can it affect something
in the future?
--
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 4 comments |
headers
Bill Unruh | 17 Sep 2008 23:15
Picon
Picon

Re: pppd creates route without "gateway" flag

On Wed, 17 Sep 2008, Joakim Wennergren wrote:

> I just looked at my routing table, and the route pppd created does not
> have the "G" flag like I'm used to, is there a reason for this?

PPP is Peer to Peer Protocol. Ie, it is from one peer to another. It has
nothing whatsoever to do with gateways, etc. 
Now you CAN use the peer as your gateway if you wish, but there is no need
to. 
In your output the default route is delivered to the ppp interface and
since there is only one thing, the remote peer, connected to that
interface, all traffic is sent out to that remote peer. 
A gateway says "if you get traffic for this range of addresses send it to
this IP". In your case it says "In the default case just dump it onto the
ppp interface"

>
> This is output from route:
>
> # route -n
> Kernel IP routing table
> Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
> 10.64.64.64     0.0.0.0         255.255.255.255 UH    0      0        0 ppp0
> 192.168.2.0     0.0.0.0         255.255.255.0   U     0      0        0 eth1
> 192.168.0.0     0.0.0.0         255.255.255.0   U     0      0        0 br0
> 0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 ppp0
>
> It seems to work, I'm just wondering why? And can it affect something
> in the future?
> --
(Continue reading)

Permalink | Reply | 3 comments |
headers
James Carlson | 17 Sep 2008 23:31

Re: pppd creates route without "gateway" flag

Bill Unruh writes:
> On Wed, 17 Sep 2008, Joakim Wennergren wrote:
> 
> > I just looked at my routing table, and the route pppd created does not
> > have the "G" flag like I'm used to, is there a reason for this?
> 
> PPP is Peer to Peer Protocol. Ie, it is from one peer to another. It has
> nothing whatsoever to do with gateways, etc. 

I think the original poster is talking about the default route
inserted by the "defaultroute" option.  As he rightly notes, it's
missing the "G" flag:

> > 0.0.0.0         0.0.0.0         0.0.0.0         U     0      0        0 ppp0

And that is in fact a gateway route.  The issue is whether that flag
actually matters on Linux.

--

-- 
James Carlson         42.703N 71.076W         <carlsonj <at> workingcode.com>
--
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 2 comments |
headers
Mr Andrewwong | 27 Sep 2008 06:04

Reply Me!!!

Hello, I want to solicit your attention to recieve money on my behalf.
I will send you the full details about the funds.
My personal email is: andrewwong2088 <at> yahoo.com.hk Thank you. Andrew Wong.

--
To unsubscribe from this list: send the line "unsubscribe linux-ppp" in
the body of a message to majordomo <at> vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Permalink | Reply | 0 comments |

Gmane