Juniper SSL VPN Does not pass packets on kernel 3.19

[Tim Bathras]

When booting kernel 3.19, the Juniper SSL VPN client will connect, but not pass any packets after initial connection.

When booting kernel 3.16, the VPN client behaves as expected and VPN traffic is passed.

The same bug seems to have been addressed in Fedora/RedHat: https://bugzilla.redhat.com/show_bug.cgi?id=1204512

ProblemType: Bug
DistroRelease: Ubuntu 15.04
Package: linux-image-3.19.0-15-generic 3.19.0-15.15
ProcVersionSignature: Ubuntu 3.16.0-34.47-generic 3.16.7-ckt8
Uname: Linux 3.16.0-34-generic x86_64
NonfreeKernelModules: wl
ApportVersion: 2.17.2-0ubuntu1
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: tbathras 1950 F.... pulseaudio
CurrentDesktop: GNOME
Date: Mon Apr 27 12:46:13 2015
HibernationDevice: RESUME=UUID=cf135c23-504b-4f8c-acba-dc762a67af55
InstallationDate: Installed on 2015-04-05 (21 days ago)
InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
MachineType: Hewlett-Packard HP EliteBook 8460p
ProcFB: 0 inteldrmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.16.0-34-generic root=UUID=20807c9b-0ad2-409f-a09f-bf7356801b7e ro quiet splash vt.handoff=7
RelatedPackageVersions:
 linux-restricted-modules-3.16.0-34-generic N/A
 linux-backports-modules-3.16.0-34-generic N/A
 linux-firmware 1.143
SourcePackage: linux
UpgradeStatus: Upgraded to vivid on 2015-04-24 (3 days ago)
dmi.bios.date: 05/10/2011
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: 68SCF Ver. F.04
dmi.board.name: 161C
dmi.board.vendor: Hewlett-Packard
dmi.board.version: KBC Version 97.41
dmi.chassis.asset.tag: 11452
dmi.chassis.type: 10
dmi.chassis.vendor: Hewlett-Packard
dmi.modalias: dmi:bvnHewlett-Packard:bvr68SCFVer.F.04:bd05/10/2011:svnHewlett-Packard:pnHPEliteBook8460p:pvrA0001D02:rvnHewlett-Packard:rn161C:rvrKBCVersion97.41:cvnHewlett-Packard:ct10:cvr:
dmi.product.name: HP EliteBook 8460p
dmi.product.version: A0001D02
dmi.sys.vendor: Hewlett-Packard

[Brad Figg (brad-figg)]

This change was made by a bot.

[Joseph Salisbury (jsalisbury)]

Would it be possible for you to test the latest upstream kernel? Refer to https://wiki.ubuntu.com/KernelMainlineBuilds . Please test the latest v4.0 kernel[0].

If this bug is fixed in the mainline kernel, please add the following tag 'kernel-fixed-upstream'.

If the mainline kernel does not fix this bug, please add the tag: 'kernel-bug-exists-upstream'.

If you are unable to test the mainline kernel, for example it will not boot, please add the tag: 'kernel-unable-to-test-upstream'.
Once testing of the upstream kernel is complete, please mark this bug as "Confirmed".

Thanks in advance.

[0] http://kernel.ubuntu.com/~kernel-ppa/mainline/v4.1-rc1-vivid/

[Tim Bathras (3-tim-l)]

Yes, I can do that later this evening. Will update with the results.

[Tim Bathras (3-tim-l)]

Added 'kernel-fixed-upstream' tag as the issue does not exist in the kernel installed by the linux-image-4.1.0-040100rc1-generic_4.1.0-040100rc1.201504270235_amd64.deb, etc. packages.

[Joseph Salisbury (jsalisbury)]

I believe this is a duplicate of bug 1448942 .

Can you test the kernel posted in comment 19 of that bug?

If it fixes the issue, please mark this bug as a duplicate.

[Tim Bathras (3-tim-l)]

Will test tonight