As I mentioned above, we can already disable the VPN DNS servers, by choosing
the 'addresses only' method.
That leaves the MTU setting and the debug option.
--
intrepid network-manager-pptp does not have essential options
https://bugs.launchpad.net/bugs/278309
You received this bug notification
Mozg,
Both of those options are present, but they are not obvious.
As we have been discussing, if you create a specific route definition, it
implies "nodefaultroute".
The second is implemented by the "Method" pull-down. If you choose "Automatic
(VPN) addresses only", it will not pick up the DNS
I understand, but other the implied criticism of "could be better organised",
it was not meant to be a suggestion for improvement.
I was mainly trying to answer JazzyPenguin's question about the routing table,
which provides a workaround for the originally reported problem, which was the
lack of
It is true that the routing table could be better organised. The Prefix
is the number of bits in the subnet prefix. E.g., for subnet
192.168.20.0/24, the prefix is 24.
In this example, you would populate the first two columns of the table
with "192.168.20.0" and "24", leaving the last two defaul
I discovered that, if you add specific routes to the VPN definition, it
preserved the existing default.
So, click "Routes" and add the VPN's subnet information to the table.
You only need to fill in the IP and prefix.
I would still prefer to see this option explicitly exposed.
--
intrepid netwo
