What does the Wireless ISP (WISP) "see" when I'm using VPN from home?

A "fake IP" is no use if you ever want to see a response to your requests. It's like giving a fake Paypal address to someone in order to receive payment.

I and many others use a fake IP when surfing the internet and have no problems getting a response. Don't know how it works just know that it does. Always get my downloads and other stuff that gives me a response. There are several browser addons that will give you a fake IP that the internet sees. I have tested that everyone only sees the fake IP by going to different sites that tells you what your IP is. All of them show the fake IP not the real one. Don't bother testing anymore.

In your case, it /should/ be quite easy. For the sake of argument, assume that the only traffic you see on wlan0 is between you and your default gateway. Kick of a download: all the traffic on wlan0 is going to/from either 198.143.153.42 or 108.178.54.10, or both. The proportion of which is indicated by the length of the bar next to the IP address. There are plenty of other ways you could work this out, but this is the quickest way for this specific task.

If we assume that all tunnels are split to one degree or another, then we need a new name for the commonly used 'split tunnel'. I suggest, in honour of Caver1, that we call these 'tabbed' tunnels.

...

Tip: 'killall vpn1click' may do the trick here and is less cumbersome [you'll need to sudo that if you're not root].

A bug perhaps? Perhaps the last time you ran it, it didn't delete that route, and then the next time you ran it, you connected to a different server of theirs, hence the two static host routes?

You're missing a very basic premise of the concept of VPN.

Right, so you're describing a split tunnel again. None of that applies to a full tunnel, which is what the OP asked about.

What you're saying *ONLY* applies to a split tunnel. The OP asked about a full tunnel. There's some aspect of 'full tunnel' that you're not getting, like the 'fullness' of it.

Hopefully, by now you've seen the corrections. You confuse people when you give bad info.

None of that made sense.

Caver1 is pissing himself laughing at the amount of effort you are putting into earnestly re-explaining VPNs to him. If he didn't get it the first 20 times then it seems unlikely that attempt #21 is going to work.

You're either completely confused or you're simply messing with me. I think I know which it is.

Do you understand what full tunnel means? Why do you keep saying it doesn't matter? Of course it matters.

I think I see where the train left the tracks. You don't send traffic "to a VPN". You establish a VPN connection, and then you simply send traffic. If the VPN is a full tunnel, everything goes into the tunnel. If it's a split tunnel, certain traffic goes into the tunnel and the rest doesn't, based on your routing table. The VPN provider injects routes into your routing table to control what goes into the tunnel and what doesn't.

Again, for clarity: You don't send traffic to a VPN. You simply send traffic, just as you always do.

Nonsense.

Char Jackson wrote, on Sat, 06 Sep 2014 13:30:53 -0500:

I am thoroughly confused by *every* answer from Caver1, almost as if he's trying to confuse me, on purpose.

What his answer seems to be saying is that the ISP, from the ISP's own home (or whatever), can "see" yahoo, google, etc. But, that's a dumb question if that's what he thought I had asked.

I was asking if "I" were on the VPN we've discussed, which appears to be a full-vpn solution (http://216.185.105.35/vpnoneclick/), and then "I" went to google, yahoo, bittorrent, nntp, etc., could the ISP see two things:

1. Could the ISP see that I went to those domains?
2. Could the ISP see what port I was going to?

Caver1 says yet. Char says no. I would hope that Char is right.

Can you confirm if it's yes or no please?

Oh, good grief. You're too much. :-)

Fake IP, indeed. ;-)

You're probably right. Oh well, it was an otherwise slow day and I learned a few things. I now know that there's no such thing as a split tunnel, that a split tunnel and a full tunnel are the same thing and behave exactly the same way, that a VPN is tied to the browser tab that spawned it, and that fake IPs can actually be useful.

It's all a load of crap, of course, but it was new crap, and I always enjoy new things.

That's a distinct possibility. He's using a combination of gibberish, laced with an actual true statement now and then, so it could be intentional. That wouldn't be very nice, but it happens.

You already know my answer. It hasn't changed. :-)

did you have to try hard to be that wrong, or does it come naturally?

it does not, your other posts to date do not esplain how it works, they only make claims about its behaviour that do not match how all the VPS ever ever heard about work.

maybe you are describing a web proxy?

ISTM that Caver1 has, all this time, been talking about a simple https connection for logging into a company's network and calling the company's internal network a VPN. I think that explains the fixation with browsers and tabs and what other software at the local end cannot do under this circumstance.