Can't connect to from the Toronto office (also, and much less importantly, can't connect to when VPNed in to MV office VPN)



Infrastructure & Operations
7 years ago
5 years ago


(Reporter: dbaron, Assigned: zandr)





7 years ago
Bug 626122 regressed recently -- sometime in the past few days, I think.  I'm filing this as a clone of that bug instead of reopening since I suspect you'd prefer it that way.

+++ This bug was initially created as a clone of Bug #626122 +++

When I connect to the mountain view office VPN from home (with the "Use this connection only for resources on its network" option in my VPN configuration), I'm unable to connect to .  Being unable to connect to means that won't load.  I've heard reports of the same thing (can't load TBPL over office VPN) from other people.

When I connect to the office VPN, the DNS result I get for changes from what I get when unconnected:
$ host is an alias for has address

to what I get when I'm inside the office:
$ host has address mail is handled by 10 mail is handled by 10

However, when I "Use this connection only for resources on its network", isn't considered a resource on the network at the other end of the VPN, so I can't connect.

(If I uncheck "Use this connection only for resources on its network" and send *all* my traffic through the VPN, then it works, but I'd rather not have to do that...)

Comment 1

7 years ago
Amy has been doing much DNS juggling to get things clean.  This also sounds like a tie in with bug 604688.

In the mean time I suggest you implement your work around.

Assigning to the correct group.
Assignee: network-operations → server-ops-releng
Group: infra
Component: Server Operations: Netops → Server Operations: RelEng
QA Contact: mrz → zandr
I think Ravi is correct in that the problem here is the coupling of the hostname and the service.  Adding dependency.
Group: infra
Depends on: 604688


7 years ago
Duplicate of this bug: 656038
inheriting blocker status from the duped bug.
Severity: normal → blocker

Comment 5

7 years ago
Taking this one, will need netops involvement.
Assignee: server-ops-releng → zandr

Comment 6

7 years ago
Any ETA on the fix, please?

Comment 7

7 years ago

Is the work around not working for you?

Comment 8

7 years ago
I have no idea how to use this workaround.  Would you please advise?


7 years ago
Summary: can't connect to when VPNed in to MV office VPN → Can't connect to from the Toronto office (also, and much less importantly, can't connect to when VPNed in to MV office VPN)

Comment 9

7 years ago
Again, to make things more clear, this is blocking our work from the office.  I'm considering working from home tomorrow if this is not fixed by then.

Comment 10

7 years ago
We've traced this to a failure in the VPN tunnel between Toronto and Mountain View. The Toronto office should now be working.

We are now looking in to the VPN route issue that dbaron reported, which we believe to be entirely separate.

Comment 11

7 years ago
The route has been restored on the VPN concentrator.
Last Resolved: 7 years ago
Resolution: --- → FIXED
The workaround doesn't apply to the Toronto office, because the people there can't disable the VPN.
Gah, sorry - didn't read all my bugmail before replying - ignore my comment!
Component: Server Operations: RelEng → RelOps
Product: → Infrastructure & Operations
You need to log in before you can comment on or make changes to this bug.