[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

technical contact at ATT Wireless

Subject: technical contact at ATT Wireless
From: jof at thejof.com (Jonathan Lassoff)
Date: Thu, 28 Jun 2012 18:21:15 -0700
In-reply-to: <CAL9jLaYXretnz0_yg+gjr6_9f0dB+4tqW6HxUfetLExMkcBjdA@mail.gmail.com>
References: <CAJbq31Ht1dTmxa=m7VPvcULKr9z3qp47665XKGSkBXhBmy+-_Q@mail.gmail.com> <CAJAdsD=HfyTLG15nE8+UMzMTOXAPKB2iPPSoOAZXV3h6rADAwA@mail.gmail.com> <CAL9jLaazvGAHj+KoSMJ3yZXc9JFPV8S-XcULryuVL07D2epF9w@mail.gmail.com> <CAJAdsDnwpHEJSHnZyG7XLegeT3RdR6n=J-P=U8Cv1N7jv-edqQ@mail.gmail.com> <CAL9jLaYXretnz0_yg+gjr6_9f0dB+4tqW6HxUfetLExMkcBjdA@mail.gmail.com>

On Thu, Jun 28, 2012 at 1:50 PM, Christopher Morrow
<morrowc.lists at gmail.com> wrote:
> of course, but you aren't supposed to be doing that on their network
> anyway... so says the nice man from sprint 4 nanogs ago.

That, and if you are tunneling in, it's good practice to forward over
any DNS traffic as well (or all, depending on the application).

That way, if you have internal names or special resolvers setup,
you'll hit that as well.

Cheers,
jof

References:
- technical contact at ATT Wireless
  - From: mdevlin at aisle10.net (Mike Devlin)
- technical contact at ATT Wireless
  - From: paul4004 at gmail.com (PC)
- technical contact at ATT Wireless
  - From: morrowc.lists at gmail.com (Christopher Morrow)
- technical contact at ATT Wireless
  - From: paul4004 at gmail.com (PC)
- technical contact at ATT Wireless
  - From: morrowc.lists at gmail.com (Christopher Morrow)

Prev by Date: Constant low-level attack
Next by Date: technical contact at ATT Wireless
Previous by thread: technical contact at ATT Wireless
Next by thread: technical contact at ATT Wireless
Index(es):
- Date
- Thread