The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Jeroen van Ingen <jeroen@zijndomein.nl>
To: linux-kernel@vger.kernel.org
Subject: Routing problem on PTPP server since kernel 2.6.39
Date: Wed, 16 Nov 2011 17:14:59 +0100	[thread overview]
Message-ID: <1321460099.3366.49.camel@icts-sp-039> (raw)

Hi,

We're in the process of upgrading our Linux-based (Ubuntu) VPN servers
and running into a problem with PPTP connections.

So far, we have been able to narrow it down to the following:


Problem:

* First PPTP client connects successfully, consecutive PPTP clients
can't connect. Cause seems to be: RADIUS authentication times out
because DHCP address allocation fails, because somehow the DHCPDISCOVER
to 255.255.255.255 is routed out ppp0 and not out of eth0.

* Routing tables look fine, both before and after first PPTP client is
connected.

* Route cache however shows an entry for 255.255.255.255. pointing
towards ppp0 and we can't explain how it got there. After flushing the
route cache this entry quickly reappears.


Last kernel working OK:
* 2.6.38

Kernels where we hit this issue:
* First: 2.6.39
* Most recent one tested: 3.1.1
* All tested kernels are from Ubuntu repository.


Questions:

* Is this the correct list to assist in troubleshooting / narrowing down
the cause? If not, which one is? Netdev or some other?

* What specific info is needed? Already gathered is output from "ip rule
list", "ip route show table" for the various tables and "ip route show
cache", both with kernel 2.6.38 and kernel 2.6.39.


Thanks in advance for any advice, insights or assistance.


Regards,

Jeroen van Ingen
ICT Service Centre
University of Twente, P.O.Box 217, 7500 AE Enschede, The Netherlands
Telephone +31 53 489 2526, Fax +31 53 489 2383
J.vanIngenSchenau@utwente.nl; http://www.utwente.nl/icts


                 reply	other threads:[~2011-11-16 16:55 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1321460099.3366.49.camel@icts-sp-039 \
    --to=jeroen@zijndomein.nl \
    --cc=linux-kernel@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox