make sure nordvpn is main route for ethernet and wlan0
by LinuxNub1 from LinuxQuestions.org on (#5BK2S)
hello,
when using airdump-ng and airplay-ng
how do i know if kali linux is using nord vpn ip and making sure my real internet ip is safe? i know over ethernet when loading browser it shows nord ip
but when i use my ac realtek wifi usb in monitor mode.. and use airdump airplay how do i know its hidden behind nordvpn also whether enabled as managed or monitored?
here is what i get with traceroute and ifconfig.. is it already working correctly or no? If not how can i make sure no matter what Nord vpn will be default gateway or make it so my wifi usb isnt going to expose my real ip?
here ill paste my input below. im new to linux and this is just for fun ! It's practice. just being safe. trying to learn since im going into cyber sec field
nord vpn on kali linux with usb realtek wifi on m0nitor mode
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.8.0.1 128.0.0.0 UG 0 0 0 tun0
default 192.168.1.1 0.0.0.0 UG 100 0 0 eth0
10.8.0.0 0.0.0.0 255.255.255.0 U 0 0 0 tun0
128.0.0.0 10.8.0.1 128.0.0.0 UG 0 0 0 tun0
152.89.204.174 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0
with nord vpn on and wlan0 realtek wifi usb off and put to"down"
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.8.0.1 128.0.0.0 UG 0 0 0 tun0
default 192.168.1.1 0.0.0.0 UG 100 0 0 eth0
10.8.0.0 0.0.0.0 255.255.255.0 U 0 0 0 tun0
128.0.0.0 10.8.0.1 128.0.0.0 UG 0 0 0 tun0
152.89.204.174 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0
if config with wlan0 on up & monitor mode with nordvpn on
$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.158 netmask 255.255.255.0 broadcast 192.168.1.255
ether d8:cb:8a:bf:de:97 txqueuelen 1000 (Ethernet)
RX packets 38421 bytes 28114338 (26.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 30729 bytes 6050917 (5.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xfb300000-fb320000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1000 (Local Loopback)
RX packets 77 bytes 5321 (5.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 77 bytes 5321 (5.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.8.0.2 netmask 255.255.255.0 destination 10.8.0.2
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC)
RX packets 36819 bytes 25332933 (24.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 30409 bytes 3862650 (3.6 MiB)
TX errors 0 dropped 495 overruns 0 carrier 0 collisions 0
wlan0: flags=803<UP,BROADCAST,NOTRAILERS,PROMISC,ALLMULTI> mtu 2312
unspec 4A-D3-2E-50-87-9F-00-8D-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 74543 bytes 0 (0.0 B)
RX errors 0 dropped 70462 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
thanks!


when using airdump-ng and airplay-ng
how do i know if kali linux is using nord vpn ip and making sure my real internet ip is safe? i know over ethernet when loading browser it shows nord ip
but when i use my ac realtek wifi usb in monitor mode.. and use airdump airplay how do i know its hidden behind nordvpn also whether enabled as managed or monitored?
here is what i get with traceroute and ifconfig.. is it already working correctly or no? If not how can i make sure no matter what Nord vpn will be default gateway or make it so my wifi usb isnt going to expose my real ip?
here ill paste my input below. im new to linux and this is just for fun ! It's practice. just being safe. trying to learn since im going into cyber sec field
nord vpn on kali linux with usb realtek wifi on m0nitor mode
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.8.0.1 128.0.0.0 UG 0 0 0 tun0
default 192.168.1.1 0.0.0.0 UG 100 0 0 eth0
10.8.0.0 0.0.0.0 255.255.255.0 U 0 0 0 tun0
128.0.0.0 10.8.0.1 128.0.0.0 UG 0 0 0 tun0
152.89.204.174 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0
with nord vpn on and wlan0 realtek wifi usb off and put to"down"
$ route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
0.0.0.0 10.8.0.1 128.0.0.0 UG 0 0 0 tun0
default 192.168.1.1 0.0.0.0 UG 100 0 0 eth0
10.8.0.0 0.0.0.0 255.255.255.0 U 0 0 0 tun0
128.0.0.0 10.8.0.1 128.0.0.0 UG 0 0 0 tun0
152.89.204.174 192.168.1.1 255.255.255.255 UGH 0 0 0 eth0
192.168.1.0 0.0.0.0 255.255.255.0 U 100 0 0 eth0
if config with wlan0 on up & monitor mode with nordvpn on
$ ifconfig
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.1.158 netmask 255.255.255.0 broadcast 192.168.1.255
ether d8:cb:8a:bf:de:97 txqueuelen 1000 (Ethernet)
RX packets 38421 bytes 28114338 (26.8 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 30729 bytes 6050917 (5.7 MiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
device interrupt 20 memory 0xfb300000-fb320000
lo: flags=73<UP,LOOPBACK,RUNNING> mtu 65536
inet 127.0.0.1 netmask 255.0.0.0
loop txqueuelen 1000 (Local Loopback)
RX packets 77 bytes 5321 (5.1 KiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 77 bytes 5321 (5.1 KiB)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
tun0: flags=4305<UP,POINTOPOINT,RUNNING,NOARP,MULTICAST> mtu 1500
inet 10.8.0.2 netmask 255.255.255.0 destination 10.8.0.2
unspec 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 txqueuelen 100 (UNSPEC)
RX packets 36819 bytes 25332933 (24.1 MiB)
RX errors 0 dropped 0 overruns 0 frame 0
TX packets 30409 bytes 3862650 (3.6 MiB)
TX errors 0 dropped 495 overruns 0 carrier 0 collisions 0
wlan0: flags=803<UP,BROADCAST,NOTRAILERS,PROMISC,ALLMULTI> mtu 2312
unspec 4A-D3-2E-50-87-9F-00-8D-00-00-00-00-00-00-00-00 txqueuelen 1000 (UNSPEC)
RX packets 74543 bytes 0 (0.0 B)
RX errors 0 dropped 70462 overruns 0 frame 0
TX packets 0 bytes 0 (0.0 B)
TX errors 0 dropped 0 overruns 0 carrier 0 collisions 0
thanks!