> 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
I'm assuming you'd like this behavior on EdgeOS changed? I know a guy...
On Jun 5, 2016 8:41 PM, "Randy Bush" wrote:
> > is anyone seeing the dreaded rfc1812 behavior in a citable fashion? how
> > common is it?
>
> we verified that the juniper and cisco platforms we tested replied with
> the sou
> is anyone seeing the dreaded rfc1812 behavior in a citable fashion? how
> common is it?
we verified that the juniper and cisco platforms we tested replied with
the source address being the ingress interface. this is, imiho, good.
a kind soul actually sent citable tests
> At least my MikroTik
>>.-.
>>| |
>>| B |- D
>> S -| A R|
>>| C |- (toward S)
>>| |
>>`-'
>>
I'm not saying anyone is wrong here. I merely want to point out eventual
incompatabilities.
So please don't get me wrong.
Regards,
Marc
> On 1 juin 2016, at 23:46, William Herrin wrote:
>
> On Wed, Jun 1, 2016 at 3:16 PM, Marc Storck wrote:
>>> .-.
>>>
On Wed, Jun 1, 2016 at 3:16 PM, Marc Storck wrote:
>> .-.
>> | |
>> | B |- D
>>S -| A R|
>> | C |- (toward S)
>> |
On Wed, Jun 1, 2016 at 5:03 PM, Octavio Alvarez wrote:
> On 05/31/2016 11:22 AM, William Herrin wrote:
>>> I'm not sure if you mean that, if sent through C it should have the
>>> source addres of A, or that it should actually be sent through A
>>> regardless of the routing table (which sounds bett
On 05/31/2016 09:52 AM, Hugo Slabbert wrote:
>> I'm not sure if you mean that, if sent through C it should have the
>> source addres of A, or that it should actually be sent through A
>> regardless of the routing table (which sounds better to me).
>
> How is the latter better? What guarantees are
On Wed 2016-Jun-01 14:03:41 -0700, Octavio Alvarez
wrote:
On 05/31/2016 11:22 AM, William Herrin wrote:
I'm not sure if you mean that, if sent through C it should have the
source addres of A, or that it should actually be sent through A
regardless of the routing table (which sounds better to
On 05/31/2016 11:22 AM, William Herrin wrote:
>> I'm not sure if you mean that, if sent through C it should have the
>> source addres of A, or that it should actually be sent through A
>> regardless of the routing table (which sounds better to me).
>
> That doesn't make sense. There may be multipl
With BCP38 in mind, could therre be situations where Router R is not allowed to
source packets with address A out of intergace C?
I think that the possibility does exist.
E.g. If interface A and C are upstream interfaces, router R may use an IP
address from ISP A on interface A and an address f
On Tue, May 31, 2016 at 12:08 PM, Octavio Alvarez
wrote:
>>.-.
>>| |
>>| B |- D
>> S -| A R|
>>| C |- (toward S)
>>|
On Tue 2016-May-31 09:08:42 -0700, Octavio Alvarez
wrote:
On 05/30/2016 10:03 PM, Randy Bush wrote:
rfc1812 says
4.3.2.4 ICMP Message Source Address
Except where this document specifies otherwise, the IP source address
in an ICMP message originated by the router MUST be one of the
On 05/30/2016 10:03 PM, Randy Bush wrote:
> rfc1812 says
>
>4.3.2.4 ICMP Message Source Address
>
>Except where this document specifies otherwise, the IP source address
>in an ICMP message originated by the router MUST be one of the IP
>addresses associated with the physical inter
On Tue, May 31, 2016 at 1:03 AM, Randy Bush wrote:
>.-.
>| |
>| B |- D
> S -| A R|
>| C |- (toward S)
>|
It seems to me that a plain text reading of RFC-1812 is as Randy describes
undesirable. It also seems that the violation of this text is commonplace in
actual implementations because of yet another time where operators have made it
clear to developers that the IETF is silly.
I like the Linux s
On Mon, May 30, 2016 at 10:03:33PM -0700, Randy Bush wrote:
>.-.
>| |
>| B |- D
> S -| A R|
>| C |- (toward S)
>|
I am completely innocent of rfc1812, and have been out of the game for a
long time, but I am pretty sure I was taught (and in turn taught) that a
router would reply using the address of the interface that originated
the reply unless that interface was unnumbered, in which case it would
reply
On Mon, 30 May 2016, Randy Bush wrote:
of course, simpletons such as i would desire the source of the time
exceeded message to be A. after all, this is the interface to which i
sent the icmp with the TTL to expire.
I agree 100%, and I'd venture to guess that most of the people running
networ
rfc1812 says
4.3.2.4 ICMP Message Source Address
Except where this document specifies otherwise, the IP source address
in an ICMP message originated by the router MUST be one of the IP
addresses associated with the physical interface over which the ICMP
message is transmitted. If
20 matches
Mail list logo
