Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Traffic on both Eth0 and Tun0? #19

Open
Ansem93 opened this issue Apr 15, 2021 · 3 comments
Open

Traffic on both Eth0 and Tun0? #19

Ansem93 opened this issue Apr 15, 2021 · 3 comments

Comments

@Ansem93
Copy link

Ansem93 commented Apr 15, 2021

Hi,
I'm using this container for a while. I just noticed that a lot of traffic is passing throught the eth0 and not tun0.
Is it normal? Does it mean that this traffic is not passing through nordvpn?

@azinchen
Copy link
Owner

Hi,

The following traffic is bypassed thru eth0, even when tun0 is available:

  1. Download ovpn config files from https://downloads.nordcdn.com - during first start of newly created container.
  2. Get status of servers from https://api.nordvpn.com - during start of the container and by reconnect cron.
  3. Get recommended server from https://nordvpn.com - when no server selected after filtering (very rare occasion).

If you observe traffic to another url - let me know.

@Ansem93
Copy link
Author

Ansem93 commented Apr 16, 2021

This are the counter when the container is started:

eth0      Link encap:Ethernet  HWaddr 02
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:3693 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2293 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:4446172 (4.2 MiB)  TX bytes:199421 (194.7 KiB)
tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:300 errors:0 dropped:0 overruns:0 frame:0
          TX packets:555 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:75632 (73.8 KiB)  TX bytes:63981 (62.4 KiB)

And this after downloading a random file:


eth0      Link encap:Ethernet  HWaddr 02
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:575195 errors:0 dropped:0 overruns:0 frame:0
          TX packets:429264 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:443519793 (422.9 MiB)  TX bytes:50455201 (48.1 MiB)


tun0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00  
          UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
          RX packets:434590 errors:0 dropped:0 overruns:0 frame:0
          TX packets:426997 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:500 
          RX bytes:404933904 (386.1 MiB)  TX bytes:21382832 (20.3 MiB)

@gpherber
Copy link

gpherber commented Feb 1, 2022

This would be normal. As the tun0 interface must send all its packets over the physical network connected to the eth0 interface, the packet count will always be higher for the eth0 interface than the count on the tun0 interface.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants