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

rfc 1812 third party address on traceroute

Subject: rfc 1812 third party address on traceroute
From: randy at psg.com (Randy Bush)
Date: Sun, 05 Jun 2016 21:03:32 -0700
In-reply-to: <CAC6=tfY=qETmOpf8z0+m+gy_prWeR0dm6PeHYLiSRk0CftRfHw@mail.gmail.com>
References: <m2r3cihl96.wl%[email protected]> <[email protected]> <[email protected]> <m27fe385a8.wl%[email protected]> <CAC6=tfY=qETmOpf8z0+m+gy_prWeR0dm6PeHYLiSRk0CftRfHw@mail.gmail.com>

> I'm assuming you'd like this behavior on EdgeOS changed?

no, the opposite.  j & c got it right.  microtik did not.  vyatta seems
to have.

randy

References:
- rfc 1812 third party address on traceroute
  - From: randy at psg.com (Randy Bush)
- rfc 1812 third party address on traceroute
  - From: josh at kyneticwifi.com (Josh Reynolds)

Prev by Date: Netflix VPN detection - actual engineer needed
Next by Date: Netflix VPN detection - actual engineer needed
Previous by thread: rfc 1812 third party address on traceroute
Next by thread: Google GeoIP issue
Index(es):
- Date
- Thread