What's new
By:
Filters
Roleplay UK

Join the UK's biggest roleplay community on FiveM and experience endless new roleplay opportunities!

Weird thought for the *month.

lionel

lionel

Destroyer of Shit Tech Advice
Location
South East UK
Right don't ask me how I got here (long and boring and quite daft) but I did.

Who reckons if you soldered a coax aerial cable to a wireless USB device, and did the same at the other end. From a living room to the loft.

would it work???? 
What packet loss would you get???
WTF WHY !!! are you a retard why not buy a powerline adaptor.

has anybody got a couple of old usb wireless adapters for me to try this out on ?
*disclaimer weird thoughts happen on a much more frequent basis, due to government monitoring I am unable to specify beyond the term weird.

 
lionel said:
Right don't ask me how I got here (long and boring and quite daft) but I did.

Who reckons if you soldered a coax aerial cable to a wireless USB device, and did the same at the other end. From a living room to the loft.

would it work???? 
What packet loss would you get???
WTF WHY !!! are you a retard why not buy a powerline adaptor.

has anybody got a couple of old usb wireless adapters for me to try this out on ?
*disclaimer weird thoughts happen on a much more frequent basis, due to government monitoring I am unable to specify beyond the term weird.
Click to expand...
You know i wondered myself if i could do the same with a coax lead on an old Sky dish to see if i could do long-range wifi.

It'd be easier to get a Coax-SMA(or whatever) coupling though to join the cables.

 
Zeito said:
You know i wondered myself if i could do the same with a coax lead on an old Sky dish to see if i could do long-range wifi.

It'd be easier to get a Coax-SMA(or whatever) coupling though to join the cables.
Click to expand...
ahh the connection isn't the big issue for me, just not sure if the signal would be be passed through or would it just fry the receiver, or would it just fail to run completely.

Also, have you had any experience with IPv4 routing, NIC weighting and windows 10 not giving a shit about any of that ? (I know should technically be a new thread but what the hell) I am seriously struggling to try and get windows 10 to ignore all routing for the VPN and run all traffic over the Local NIC :( :( 

 
lionel said:
ahh the connection isn't the big issue for me, just not sure if the signal would be be passed through or would it just fry the receiver, or would it just fail to run completely.

Also, have you had any experience with IPv4 routing, NIC weighting and windows 10 not giving a shit about any of that ? (I know should technically be a new thread but what the hell) I am seriously struggling to try and get windows 10 to ignore all routing for the VPN and run all traffic over the Local NIC :( :( 
Click to expand...
Hmmmm I mean in theory it should work. Even attached at one end and all the sheilding stripped away from the other and wrapped tightly around the receiving it should act as an antenna and conductor right? You need to find out.

Nic Weighting yes - though again windows didnt give a fuck what the metic weight was, or the Nic preference. What about just a static route for 0.0.0.0 to the default gateway of local nic?

 
Zeito said:
Nic Weighting yes - though again windows didnt give a fuck what the metic weight was, or the Nic preference. What about just a static route for 0.0.0.0 to the default gateway of local nic?
Click to expand...
already have the default route ....

One sec ....

===========================================================================
Interface List
19...00 1c c0 99 b5 5d ......Intel(R) 82566DC Gigabit Network Connection
1...........................Software Loopback Interface 1
16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
9...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
10...00 ff 76 ae 46 35 ......TAP-Windows Adapter V9
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.123 20
64.145.79.25 255.255.255.255 192.168.1.254 192.168.1.123 10
89.238.132.41 255.255.255.255 192.168.1.254 192.168.1.123 10
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.1.0 255.255.255.0 On-link 192.168.1.123 266
192.168.1.123 255.255.255.255 On-link 192.168.1.123 266
192.168.1.255 255.255.255.255 On-link 192.168.1.123 266
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.123 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.123 266
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.1.123 255.255.255.0 192.168.1.254 1
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
19 266 fe80::/64 On-link
16 306 fe80::/64 On-link
16 306 fe80::82:1d27:9264:dacc/128
On-link
19 266 fe80::2542:1c71:eb76:987e/128
On-link
1 306 ff00::/8 On-link
19 266 ff00::/8 On-link
16 306 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
PS C:\WINDOWS\system32>


So as you can see I deleted (remotely (balls out)!!!!) the default route (after creating my own:p ) and forced all traffic onto the local card, yet when I fire up the VPN all traffic jumps onto the virtual NIC.

Here is the same with the VPN fired up.

===========================================================================
Interface List
19...00 1c c0 99 b5 5d ......Intel(R) 82566DC Gigabit Network Connection
1...........................Software Loopback Interface 1
16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
9...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
8...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
10...00 ff 76 ae 46 35 ......TAP-Windows Adapter V9
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.123 20
0.0.0.0 128.0.0.0 172.21.30.1 172.21.29.231 60
0.0.0.0 128.0.0.0 172.21.28.1 172.21.29.231 60
64.145.79.25 255.255.255.255 192.168.1.254 192.168.1.123 10
89.238.132.41 255.255.255.255 192.168.1.254 192.168.1.123 10
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
128.0.0.0 128.0.0.0 172.21.20.1 172.21.29.231 60
128.0.0.0 128.0.0.0 172.21.26.1 172.21.29.231 60
128.0.0.0 128.0.0.0 172.21.28.1 172.21.29.231 60
128.0.0.0 128.0.0.0 172.21.30.1 172.21.29.231 60
172.21.28.0 255.255.254.0 On-link 172.21.29.231 316
172.21.29.231 255.255.255.255 On-link 172.21.29.231 316
172.21.29.255 255.255.255.255 On-link 172.21.29.231 316
192.168.1.0 255.255.255.0 On-link 192.168.1.123 266
192.168.1.123 255.255.255.255 On-link 192.168.1.123 266
192.168.1.255 255.255.255.255 On-link 192.168.1.123 266
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 172.21.29.231 316
224.0.0.0 240.0.0.0 On-link 192.168.1.123 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 172.21.29.231 316
255.255.255.255 255.255.255.255 On-link 192.168.1.123 266
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.1.123 255.255.255.0 192.168.1.254 1
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
19 266 fe80::/64 On-link
19 266 fe80::2542:1c71:eb76:987e/128
On-link
1 306 ff00::/8 On-link
19 266 ff00::/8 On-link
===========================================================================
Persistent Routes:
None


And the IP reported by Edge is "89.238.132.42".

Weird huh !!! 

 
Last edited by a moderator:
lionel said:
already have the default route ....

One sec ....

===========================================================================
Interface List
19...00 1c c0 99 b5 5d ......Intel(R) 82566DC Gigabit Network Connection
1...........................Software Loopback Interface 1
16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
9...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
10...00 ff 76 ae 46 35 ......TAP-Windows Adapter V9
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.123 20
64.145.79.25 255.255.255.255 192.168.1.254 192.168.1.123 10
89.238.132.41 255.255.255.255 192.168.1.254 192.168.1.123 10
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
192.168.1.0 255.255.255.0 On-link 192.168.1.123 266
192.168.1.123 255.255.255.255 On-link 192.168.1.123 266
192.168.1.255 255.255.255.255 On-link 192.168.1.123 266
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 192.168.1.123 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 192.168.1.123 266
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.1.123 255.255.255.0 192.168.1.254 1
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
19 266 fe80::/64 On-link
16 306 fe80::/64 On-link
16 306 fe80::82:1d27:9264:dacc/128
On-link
19 266 fe80::2542:1c71:eb76:987e/128
On-link
1 306 ff00::/8 On-link
19 266 ff00::/8 On-link
16 306 ff00::/8 On-link
===========================================================================
Persistent Routes:
None
PS C:\WINDOWS\system32>


So as you can see I deleted (remotely (balls out)!!!!) the default route (after creating my own:p ) and forced all traffic onto the local card, yet when I fire up the VPN all traffic jumps onto the virtual NIC.

Here is the same with the VPN fired up.

===========================================================================
Interface List
19...00 1c c0 99 b5 5d ......Intel(R) 82566DC Gigabit Network Connection
1...........................Software Loopback Interface 1
16...00 00 00 00 00 00 00 e0 Teredo Tunneling Pseudo-Interface
9...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #2
8...00 00 00 00 00 00 00 e0 Microsoft ISATAP Adapter #3
10...00 ff 76 ae 46 35 ......TAP-Windows Adapter V9
===========================================================================

IPv4 Route Table
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.1.254 192.168.1.123 20
0.0.0.0 128.0.0.0 172.21.30.1 172.21.29.231 60
0.0.0.0 128.0.0.0 172.21.28.1 172.21.29.231 60
64.145.79.25 255.255.255.255 192.168.1.254 192.168.1.123 10
89.238.132.41 255.255.255.255 192.168.1.254 192.168.1.123 10
127.0.0.0 255.0.0.0 On-link 127.0.0.1 306
127.0.0.1 255.255.255.255 On-link 127.0.0.1 306
127.255.255.255 255.255.255.255 On-link 127.0.0.1 306
128.0.0.0 128.0.0.0 172.21.20.1 172.21.29.231 60
128.0.0.0 128.0.0.0 172.21.26.1 172.21.29.231 60
128.0.0.0 128.0.0.0 172.21.28.1 172.21.29.231 60
128.0.0.0 128.0.0.0 172.21.30.1 172.21.29.231 60
172.21.28.0 255.255.254.0 On-link 172.21.29.231 316
172.21.29.231 255.255.255.255 On-link 172.21.29.231 316
172.21.29.255 255.255.255.255 On-link 172.21.29.231 316
192.168.1.0 255.255.255.0 On-link 192.168.1.123 266
192.168.1.123 255.255.255.255 On-link 192.168.1.123 266
192.168.1.255 255.255.255.255 On-link 192.168.1.123 266
224.0.0.0 240.0.0.0 On-link 127.0.0.1 306
224.0.0.0 240.0.0.0 On-link 172.21.29.231 316
224.0.0.0 240.0.0.0 On-link 192.168.1.123 266
255.255.255.255 255.255.255.255 On-link 127.0.0.1 306
255.255.255.255 255.255.255.255 On-link 172.21.29.231 316
255.255.255.255 255.255.255.255 On-link 192.168.1.123 266
===========================================================================
Persistent Routes:
Network Address Netmask Gateway Address Metric
192.168.1.123 255.255.255.0 192.168.1.254 1
===========================================================================

IPv6 Route Table
===========================================================================
Active Routes:
If Metric Network Destination Gateway
1 306 ::1/128 On-link
19 266 fe80::/64 On-link
19 266 fe80::2542:1c71:eb76:987e/128
On-link
1 306 ff00::/8 On-link
19 266 ff00::/8 On-link
===========================================================================
Persistent Routes:
None


And the IP reported by Edge is "89.238.132.42".

Weird huh !!! 
Click to expand...
Routing tables are just not my thing, but can you remove these routes?

0.0.0.0 128.0.0.0 172.21.30.1 172.21.29.231 60
0.0.0.0 128.0.0.0 172.21.28.1 172.21.29.231 60

hey it gave it fancy colouring when i quoted you

 
Zeito said:
Routing tables are just not my thing, but can you remove these routes?

0.0.0.0 128.0.0.0 172.21.30.1 172.21.29.231 60
0.0.0.0 128.0.0.0 172.21.28.1 172.21.29.231 60


hey it gave it fancy colouring when i quoted you
Click to expand...
Only problem if I do that when it changes to another VPN endpoint (it hops every few hours for security), then it will recreate the routing tables, as you can see the metric for the VPN is 60 so even higher than LAN  and local loopback !!! 

I am presuming If I remove those routes and pick another VPN Endpoint It will just recreate the routes no ?

 
Last edited by a moderator:
lionel said:
Only problem if I do that when it changes to another VPN endpoint, then it will recreate the routing tables, as you can see the metric for the VPN is 60 so even higher than LAN  and local loopback !!! 

I am presuming If I remove those routes and pick another VPN Endpoint It will just recreate the routes no ?
Click to expand...
Hmm I'm really not sure mate. Sorry :(

 
Zeito said:
Hmm I'm really not sure mate. Sorry :(
Click to expand...
no worries thanks for looking into it, I will try removing the default ip4 routes tonight pointed at the tap9 adapter and see if it helps. Will update ya :)

 
No joy after removing those routing tables :(

Anybody else got skills with routing tables ?

 
I just want to say, I FUCKING HATE IPV4 ROUTING TABLES !!! FUCK FUCK FUCKITY FUCK.

I am now asking for help on this proper !!!

 
You must log in or register to reply here.
Back
Top