All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 198163] New: vpn pptp protocol did not working properly in new kernel release
Date: Thu, 14 Dec 2017 08:05:56 -0800	[thread overview]
Message-ID: <20171214080556.785d9bf8@xeon-e3> (raw)



Begin forwarded message:

Date: Thu, 14 Dec 2017 09:41:42 +0000
From: bugzilla-daemon@bugzilla.kernel.org
To: stephen@networkplumber.org
Subject: [Bug 198163] New: vpn pptp protocol did not working properly in new kernel release


https://bugzilla.kernel.org/show_bug.cgi?id=198163

            Bug ID: 198163
           Summary: vpn pptp protocol did not working properly in new
                    kernel release
           Product: Networking
           Version: 2.5
    Kernel Version: 4.14.3-300.fc27.x86_64
          Hardware: All
                OS: Linux
              Tree: Mainline
            Status: NEW
          Severity: high
          Priority: P1
         Component: Other
          Assignee: stephen@networkplumber.org
          Reporter: mohammed.okasha.ps@gmail.com
        Regression: No

I have VPN network (PPTP protocol), When established connection to VPN server I
can see VPN network tunnel in output ip command and table route with netstat
command but I cannot access to internet and VPN network unless I disconnect VPN
network in Fedora 27


How reproducible:

Just add new VPN (PPTP) network 

Steps to Reproduce:
1.add gateway
2.add username and password
3.keep another default settings

Note:firewalld off and routing table same and SELinux disabled

When I downgraded kernel to 4.8.6-300.fc25 version everything works fine

this report that i was created contain logs:
https://bugzilla.redhat.com/show_bug.cgi?id=1524212

also see this screenshot:
https://imgur.com/fCDE8U1
https://imgur.com/zUBrdmP

-- 
You are receiving this mail because:
You are the assignee for the bug.

                 reply	other threads:[~2017-12-14 16:06 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=20171214080556.785d9bf8@xeon-e3 \
    --to=stephen@networkplumber.org \
    --cc=netdev@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.