Re: Using both VPN and non-VPN (default route non-VPN)

2018-12-10 Thread Andrei Borzenkov via networkmanager-list
10.12.2018 21:02, Alexandre Garreau via networkmanager-list пишет:
> On 2018-12-10 at 18:16, Thomas Haller wrote:
>> you need to have the routes configured properly, which depends on your
>> environment.
> 
> Maybe should I ask on debian mailing-lists (not that much active, not
> sure I can get more relevant help than here)?
> 
>> Well, NM should get it right automatically. If it doesn't,
>> then you should look at the routes to understand what's wrong.
>>
>> What gives:
>>
>>   ip route
> 
> Currently I’m not at the needed local network, so doing it at home, with
> normally configured network, I get:
> 
> galex-713@portable:~/doc/comp/src/pharo/opensmalltalk-vm$ ip route
> default dev tun0 proto static scope link metric 50 
> default via 192.168.1.254 dev enp0s25 proto static metric 100 
> 89.234.186.64/27 dev tun0 proto kernel scope link src 89.234.186.82 metric 50 
> 169.254.0.0/16 dev enp0s25 scope link metric 1000 
> 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.38 metric 
> 100 
> 
> When enabling “VPN config > IPv4 Settings > Routes… > Use this
> connection only for resources on its network” checkbox, I get this:
> 
> galex-713@portable:~/doc/comp/src/pharo/opensmalltalk-vm$ ip route
> default via 192.168.1.254 dev enp0s25 proto static metric 100 
> 89.234.186.64/27 dev tun0 proto kernel scope link src 89.234.186.82 metric 50 
> 89.234.186.190 via 192.168.1.254 dev enp0s25 proto static metric 100 
> 169.254.0.0/16 dev enp0s25 scope link metric 1000 
> 192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.38 metric 
> 100 
> 192.168.1.254 dev enp0s25 proto static scope link metric 100 
> 
> I’m under Debian GNU/Linux stable, x86 (32bits).
> 
> Btw ifconfig:
> galex-713@portable:~/doc/comp/src/pharo/opensmalltalk-vm$ /sbin/ifconfig
> enp0s25: flags=4163  mtu 1500
> inet 192.168.1.38  netmask 255.255.255.0  broadcast 192.168.1.255
> inet6 2a01:e0a:54:cb90:dd93:58f3:5591:dc39  prefixlen 64  scopeid 
> 0x0
> inet6 fe80::6a50:6fa8:1bc9:b6d1  prefixlen 64  scopeid 0x20
> ether 00:1f:16:14:45:a9  txqueuelen 1000  (Ethernet)
> RX packets 425383  bytes 300655547 (286.7 MiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 94334  bytes 15010937 (14.3 MiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> device interrupt 20  memory 0xf270-f272  
> 
> lo: flags=73  mtu 65536
> inet 127.0.0.1  netmask 255.0.0.0
> inet6 ::1  prefixlen 128  scopeid 0x10
> loop  txqueuelen 1  (Boucle locale)
> RX packets 1544  bytes 185223 (180.8 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 1544  bytes 185223 (180.8 KiB)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> tun0: flags=4305  mtu 1500
> inet 89.234.186.82  netmask 255.255.255.224  destination 89.234.186.82
> inet6 fe80::918:d4aa:a0ae:2b1d  prefixlen 64  scopeid 0x20
> inet6 2a00:5884:8305::1  prefixlen 112  scopeid 0x0
> unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 
> 100  (UNSPEC)
> RX packets 12  bytes 1476 (1.4 KiB)
> RX errors 0  dropped 0  overruns 0  frame 0
> TX packets 12  bytes 808 (808.0 B)
> TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
> 
> both interfaces are only present, but only tun0 works in the first case,
> and only enps25 works in the second.
> 


You need to explain what "works" means. According to your routing
tables, you should have access to local network 192.168.1.0/24 in both
cases. At least if I interpret your "need local network" correctly, that
is what you need. If this is not what you want, show what does not work
in each case.
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Using both VPN and non-VPN (default route non-VPN)

2018-12-10 Thread Alexandre Garreau via networkmanager-list
On 2018-12-10 at 18:16, Thomas Haller wrote:
> you need to have the routes configured properly, which depends on your
> environment.

Maybe should I ask on debian mailing-lists (not that much active, not
sure I can get more relevant help than here)?

> Well, NM should get it right automatically. If it doesn't,
> then you should look at the routes to understand what's wrong.
>
> What gives:
>
>   ip route

Currently I’m not at the needed local network, so doing it at home, with
normally configured network, I get:

galex-713@portable:~/doc/comp/src/pharo/opensmalltalk-vm$ ip route
default dev tun0 proto static scope link metric 50 
default via 192.168.1.254 dev enp0s25 proto static metric 100 
89.234.186.64/27 dev tun0 proto kernel scope link src 89.234.186.82 metric 50 
169.254.0.0/16 dev enp0s25 scope link metric 1000 
192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.38 metric 100 

When enabling “VPN config > IPv4 Settings > Routes… > Use this
connection only for resources on its network” checkbox, I get this:

galex-713@portable:~/doc/comp/src/pharo/opensmalltalk-vm$ ip route
default via 192.168.1.254 dev enp0s25 proto static metric 100 
89.234.186.64/27 dev tun0 proto kernel scope link src 89.234.186.82 metric 50 
89.234.186.190 via 192.168.1.254 dev enp0s25 proto static metric 100 
169.254.0.0/16 dev enp0s25 scope link metric 1000 
192.168.1.0/24 dev enp0s25 proto kernel scope link src 192.168.1.38 metric 100 
192.168.1.254 dev enp0s25 proto static scope link metric 100 

I’m under Debian GNU/Linux stable, x86 (32bits).

Btw ifconfig:
galex-713@portable:~/doc/comp/src/pharo/opensmalltalk-vm$ /sbin/ifconfig
enp0s25: flags=4163  mtu 1500
inet 192.168.1.38  netmask 255.255.255.0  broadcast 192.168.1.255
inet6 2a01:e0a:54:cb90:dd93:58f3:5591:dc39  prefixlen 64  scopeid 
0x0
inet6 fe80::6a50:6fa8:1bc9:b6d1  prefixlen 64  scopeid 0x20
ether 00:1f:16:14:45:a9  txqueuelen 1000  (Ethernet)
RX packets 425383  bytes 300655547 (286.7 MiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 94334  bytes 15010937 (14.3 MiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
device interrupt 20  memory 0xf270-f272  

lo: flags=73  mtu 65536
inet 127.0.0.1  netmask 255.0.0.0
inet6 ::1  prefixlen 128  scopeid 0x10
loop  txqueuelen 1  (Boucle locale)
RX packets 1544  bytes 185223 (180.8 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 1544  bytes 185223 (180.8 KiB)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

tun0: flags=4305  mtu 1500
inet 89.234.186.82  netmask 255.255.255.224  destination 89.234.186.82
inet6 fe80::918:d4aa:a0ae:2b1d  prefixlen 64  scopeid 0x20
inet6 2a00:5884:8305::1  prefixlen 112  scopeid 0x0
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  txqueuelen 100  
(UNSPEC)
RX packets 12  bytes 1476 (1.4 KiB)
RX errors 0  dropped 0  overruns 0  frame 0
TX packets 12  bytes 808 (808.0 B)
TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

both interfaces are only present, but only tun0 works in the first case,
and only enps25 works in the second.
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


Re: Using both VPN and non-VPN (default route non-VPN)

2018-12-10 Thread Thomas Haller via networkmanager-list
On Mon, 2018-12-10 at 17:34 +0100, Alexandre Garreau via
networkmanager-list wrote:
> Hi,
> I’ve already asked some help on irc: I have a VPN that provides me a
> public IP, which I use to run network servers, but I want to access
> the local network I’m connecting too, without passing through the VPN
> (otherwise stuff accessible only through local network is not
> accessible anywore), while still being able to use the tun0
> interface. It’s a OpenVPN VPN, configured and ran through network-
> manager. I was told to go in IPv4, routes… and check the last
> checkbox.
> But beside routing, when doing that tun0 becomes inaccessible:
> everything ends timeouting, and the other way around while not
> checking the checkbox: the wifi interface is inaccessible, only the
> tun0 answers…
> Why that? is it more an openvpn problem? But if asking openvpn people
> will I find a way to apply that through network-manager?
> Thank you for any help ^^

Hi,

you need to have the routes configured properly, which depends on your
environment. Well, NM should get it right automatically. If it doesn't,
then you should look at the routes to understand what's wrong.

What gives:

  ip route



best,
Thomas


signature.asc
Description: This is a digitally signed message part
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list


Using both VPN and non-VPN (default route non-VPN)

2018-12-10 Thread Alexandre Garreau via networkmanager-list
Hi,

I’ve already asked some help on irc: I have a VPN that provides me a
public IP, which I use to run network servers, but I want to access the
local network I’m connecting too, without passing through the VPN
(otherwise stuff accessible only through local network is not accessible
anywore), while still being able to use the tun0 interface.  It’s a
OpenVPN VPN, configured and ran through network-manager.  I was told to
go in IPv4, routes... and check the last checkbox.

But beside routing, when doing that tun0 becomes inaccessible:
everything ends timeouting, and the other way around while not checking
the checkbox: the wifi interface is inaccessible, only the tun0 answers…

Why that? is it more an openvpn problem?  But if asking openvpn people
will I find a way to apply that through network-manager?

Thank you for any help ^^
___
networkmanager-list mailing list
networkmanager-list@gnome.org
https://mail.gnome.org/mailman/listinfo/networkmanager-list