I blocked Google, now they block me.
-
Sorry for the odd title. First post, so be easy on me. I access my camera system remotely via my private IP address and port forwarding. I know, not the best way to do it, but I am getting there. I started noticing on my logs some strange IP addresses. In fact if I sit there with my phone on cell service, I can watch the log and it will show my Verizon IP, then flip to a Google IP address. They all come back to bc.googleusercontent.com.
So I would set up pfBlockerNG to block each one of these addresses. This would work for a while, and then they would find me again via another IP address. This led me to block out their entire IP segment. This worked for a day. Now I can't access my BI server remotely at all. As if Google got wise to me blocking them, and then turned around and blocked me. If I kill pfBlockerNG, I can get in. Turn it back on, and I can't get in. I was able to access my system remotely for a few weeks without this happening, so I know this googleusercontent isn't "required" for me to access it.
I know a VPN is the way to do this. I'm getting there slowly but surely. Has anyone else had to deal with this?
-
@obxjeepguy said in I blocked Google, now they block me.:
bc.googleusercontent.com
Had to look, the up.
Here it is : what is bc.googleusercontent.comso everybody that has a written a 'whatever script' can put it on "googleusercontent.com" and let it do it's work.
Yeah, spot on : block that one. If you can grab the IPs used. As you said, behind that host name, there will be many IPs.But blocking these IPs will not block you. It it would mean that the device your are using to connect to your WZAN IP¨is using an IP that is on some list you use in pfBlockerNG-devel.
So, note down the IP you use when your out, try to connect to the camera @home - and when you come back home, there will be a trace in the pfBlockerNG logs - IP logs probably, as these are normally used on the WAN side.
If you do not find your IP, it was not pfBlockerNG that blocked you.Google, or .googleusercontent.com. can not stop your device connected to your cell operator from connecting to your home. Google is not your ISP, right ? Neither your cell operator.
And yeah, I know, and you know, VPN was invented a long time ago to secure these kind of activities. Since a a year or two billions are using VPN to connect to home or work, so it's the "thing to have" these days. If you have something you want to access at home or work when your out in the wiki, you use VPN (ipsec, wiregard, whatever) you should consider reserving your place in the queue at the local police station so you can deposit a compliant for "house or worked hacked - all gone situation" and you will designate half of India, sorry : Chinese, no wait : the Russian ! or who ever. Anonymous doesn't care about cameras, as far as I know.
Later on you will probably hear that it was actually your neighbor, but that's another story. -
@gertjan I do know my work (and sometimes my Verizon Wireless) IP addresses. I will look in the logs for that. Thanks for the heads up, as it didn’t even occur to me to look there. I was becoming highly annoyed with Google’s shenanigans as it has nothing to do with what I’m doing. I’ll see what I can figure out this afternoon when I get home.
I just thought of something. I did also add a United States repository to pfBlockerNG. I’m betting if I turn that off, it’ll go away.
-
Removing PFB_NorthAmerica_v4 did the trick.
-
Euh, that's a lol case.
What is in that list according to you ?
DNSBL are not only bad guys, there are all kind of lists, like lists with known localized IP networks for all ISPs and also IPs from phone companies for a country.
If you use that DNSBL on the inbound interface, your WAN, then yes, pfBlockerNG was alerting you that it was blocking your phone or outside IP coming into your WAN.
Anyway, now you know ^^ -
I'm quite confused when I saw your title
have you tried accessing with another device? Maybe Google just blocked the ip address on that device -
@jsporer said in I blocked Google, now they block me.:
I'm quite confused when I saw your title
But you've read all the posts, and found out that the initial subject isn't the real subject, and not even close.
