[j-nsp] Strange MPLS behaviour
Alexander Arsenyev (GU/ETL)
alexander.arsenyev at ericsson.com
Tue Dec 21 19:17:02 EST 2004
Hello,
It is indeed very interesting scenario.
I actually labbed this up and source IP address of locally generated ping packets depends on:
a) whether lo0.0 has a valid (non-127/8) IP address assigned
(if not then fxp0.0 IP address is used as source IP)
b) whether ICMP ping or MPLS PING (UDP dport 3503) is used
(MPLS PING packets use lo0.0 or fxp0.0 IP address as source IP,
while ICMP ping packets use lo0.0 or outgoing interface' IP address as source IP)
c) whether "default-address-selection" is configured
(if configured then lo0.0 IP address is used as source IP)
I used JUNOS 5.6 in my tests, what is Your JUNOS version?
HTH,
Cheers
Alex
-----Original Message-----
From: juniper-nsp-bounces at puck.nether.net
[mailto:juniper-nsp-bounces at puck.nether.net]
Sent: 21 December 2004 08:32
To: sthaug at nethelp.no
Cc: juniper-nsp at puck.nether.net
Subject: Re: [j-nsp] Strange MPLS behaviour
> set system default-address-selection
>
> Steinar Haug, Nethelp consulting, sthaug at nethelp.no
Thats a good idea but if i do not want/cant use that option, i'd like to
have the router actually use the ip address on the interface the lsp is
running on. Also i have to/from statements in the lsp config so i dont
understand why the router still uses completly different (fxp0)
addresses. This doesnt make sense.
Regards,
Jonas
_______________________________________________
juniper-nsp mailing list juniper-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/juniper-nsp
More information about the juniper-nsp
mailing list