Rogue Interface Still Showing

Networking & Firewalls
1

Hi Everyone,

I have a rogue interface that is showing and possibly causing issues for my internet connection.

Dec 29 09:40:22 dpinger VPNUNLIMITED_VPNV4 8.8.8.8: Clear latency 27384us stddev 64783us loss 15%
Dec 29 09:39:52 dpinger VPNUNLIMITED_VPNV4 8.8.8.8: Alarm latency 19929us stddev 3767us loss 21%

VPNUNLIMITED was removed quite a while back, but this is still showing in the gateway logs periodically. When it happens, I notice issus with my internet connection, like video conferencing stalling.

Anyone have any suggestions on where I could look to resolve this?

Thanks in advance,
Sean

2

Delete the configuration under OpenVPN related to that interface.

3

Thanks @LTS_Tom. That’s just it. I removed that interface from OpenVPN quite a while ago. It’s no longer showing…

1
12244×956 197 KB
2
21918×824 120 KB

4

I must have later used that same interface to set up my VLAN20. However, something doesn’t jive and I’m getting the above errors.

I’m starting to wonder if I have an issues with my modem, as I’m not only having long latency at times, but also periodic Request timeouts…

64 bytes from 142.250.64.142: icmp_seq=41 ttl=56 time=33.589 ms
64 bytes from 142.250.64.142: icmp_seq=42 ttl=56 time=35.392 ms
64 bytes from 142.250.64.142: icmp_seq=43 ttl=56 time=33.660 ms
64 bytes from 142.250.64.142: icmp_seq=44 ttl=56 time=52.593 ms
64 bytes from 142.250.64.142: icmp_seq=45 ttl=56 time=138.604 ms
64 bytes from 142.250.64.142: icmp_seq=46 ttl=56 time=140.479 ms
64 bytes from 142.250.64.142: icmp_seq=47 ttl=56 time=37.254 ms
64 bytes from 142.250.64.142: icmp_seq=48 ttl=56 time=35.054 ms
64 bytes from 142.250.64.142: icmp_seq=49 ttl=56 time=37.260 ms
64 bytes from 142.250.64.142: icmp_seq=50 ttl=56 time=32.184 ms
64 bytes from 142.250.64.142: icmp_seq=51 ttl=56 time=33.289 ms
64 bytes from 142.250.64.142: icmp_seq=52 ttl=56 time=35.343 ms
64 bytes from 142.250.64.142: icmp_seq=53 ttl=56 time=49.942 ms
64 bytes from 142.250.64.142: icmp_seq=54 ttl=56 time=35.816 ms
64 bytes from 142.250.64.142: icmp_seq=55 ttl=56 time=33.498 ms
64 bytes from 142.250.64.142: icmp_seq=56 ttl=56 time=32.840 ms
64 bytes from 142.250.64.142: icmp_seq=57 ttl=56 time=37.212 ms
64 bytes from 142.250.64.142: icmp_seq=58 ttl=56 time=33.884 ms
64 bytes from 142.250.64.142: icmp_seq=59 ttl=56 time=38.167 ms
64 bytes from 142.250.64.142: icmp_seq=60 ttl=56 time=35.550 ms
64 bytes from 142.250.64.142: icmp_seq=61 ttl=56 time=36.646 ms
64 bytes from 142.250.64.142: icmp_seq=62 ttl=56 time=32.608 ms
64 bytes from 142.250.64.142: icmp_seq=63 ttl=56 time=38.931 ms
64 bytes from 142.250.64.142: icmp_seq=64 ttl=56 time=32.790 ms
64 bytes from 142.250.64.142: icmp_seq=65 ttl=56 time=35.944 ms
64 bytes from 142.250.64.142: icmp_seq=66 ttl=56 time=45.511 ms
64 bytes from 142.250.64.142: icmp_seq=67 ttl=56 time=34.295 ms
64 bytes from 142.250.64.142: icmp_seq=68 ttl=56 time=36.903 ms
Request timeout for icmp_seq 69
64 bytes from 142.250.64.142: icmp_seq=70 ttl=56 time=34.288 ms
64 bytes from 142.250.64.142: icmp_seq=71 ttl=56 time=36.571 ms
64 bytes from 142.250.64.142: icmp_seq=72 ttl=56 time=33.618 ms
64 bytes from 142.250.64.142: icmp_seq=73 ttl=56 time=33.252 ms
64 bytes from 142.250.64.142: icmp_seq=74 ttl=56 time=33.236 ms
64 bytes from 142.250.64.142: icmp_seq=75 ttl=56 time=36.661 ms
64 bytes from 142.250.64.142: icmp_seq=76 ttl=56 time=36.846 ms
64 bytes from 142.250.64.142: icmp_seq=77 ttl=56 time=38.380 ms
64 bytes from 142.250.64.142: icmp_seq=78 ttl=56 time=34.752 ms
64 bytes from 142.250.64.142: icmp_seq=79 ttl=56 time=38.120 ms
64 bytes from 142.250.64.142: icmp_seq=80 ttl=56 time=44.656 ms

I did set up Codel per Tom’s recommendations, so see if that helped, but alas, it does not, for my situation.