"Local Port 0" causes trouble with firewalls

Bug #995366 reported by Konstantin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
network-manager-vpnc (Ubuntu)
Triaged
Medium
Unassigned

Bug Description

When fixing #513166, it was introduced that the "Local Port 0" option is always sent to vpnc. This however causes problems as some access point do not accept traffic other than from the default port 500.

There is no possibility in networkmanager to change this behaviour.

Since there seems to be a need for bothe, the default port 500 and random port selection as demanded in #513166, this should be made into a GUI option.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: network-manager-vpnc 0.9.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-24.37-generic 3.2.14
Uname: Linux 3.2.0-24-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu7
Architecture: amd64
Date: Sun May 6 16:24:48 2012
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120328)
SourcePackage: network-manager-vpnc
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
Konstantin (list-kseiler) wrote :
Revision history for this message
Mathieu Trudel-Lapierre (cyphermox) wrote :

So you're saying your firewall blocks traffic coming from a random source port to port 500? It seems unlikely, but I guess some spectacularly bad implementations of state engines could do that.

There's a fix to that effect in 0.9.8.0, which I'll upload to raring shortly (providing a way to choose the source port). Following that point we may want to provide the updated package via a PPA.

Changed in network-manager-vpnc (Ubuntu):
status: New → Triaged
importance: Undecided → Medium
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.