[j-nsp] Strange MPLS behaviour

Josef Buchsteiner josefb at juniper.net
Wed Dec 22 09:36:14 EST 2004


in all cases the 'source' knob should override the default primary
address source selection for icmp or lsping. The primary address
does not need to be lo0 or fpx0 however after a reboot it is the
first interface.

Josef

Wednesday, December 22, 2004, 7:51:06 AM, you wrote:

  
AAGE> Hello Jonas,

AAGE>  I see Your point. However, fxp0 is just one of router
AAGE> interfaces and is perfectly eligible of being selected as
AAGE> "primary", see
AAGE> http://www.juniper.net/techpubs/software/junos/junos64/swconfig64-interfaces/html/interfaces-family-config11.html#1014302
AAGE> and
AAGE> http://www.juniper.net/techpubs/software/junos/junos64/swconfig64-interfaces/html/interfaces-family-config12.html#1014326
AAGE> . However, my tests show me that "primary" does not work for
AAGE> locally generated MPLS PING (UDP dport 3503) traffic - see my
AAGE> email below.

AAGE>  HTH,
AAGE>  Cheers
AAGE>  Alex


AAGE>  -----Original Message-----
AAGE>  From: Jonas Frey [mailto:jf at probe-networks.de]
AAGE>  Sent: 22 December 2004 06:20
AAGE>  To: Alexander Arsenyev (GU/ETL)
AAGE>  Cc: juniper-nsp at puck.nether.net
AAGE>  Subject: RE: [j-nsp] Strange MPLS behaviour


AAGE>  Hello Alex,

AAGE>  thats exactly what i observed, we were only using 127/8 ip addresses on
AAGE>  lo0 before. To fix all this we added "real" ip addresses to lo0 and now
AAGE>  things work. However i dont think its a good idea to send out packets
AAGE>  sourced from fxp0 anyway.

AAGE>  Running 6.4R2.4 here.

AAGE>  Regards,
AAGE>  Jonas

AAGE>  On Wed, 2004-12-22 at 01:17, Alexander Arsenyev (GU/ETL) wrote:
 >> 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
 >> _______________________________________________
 >> juniper-nsp mailing list juniper-nsp at puck.nether.net
 >> http://puck.nether.net/mailman/listinfo/juniper-nsp


AAGE>  _______________________________________________
AAGE>  juniper-nsp mailing list juniper-nsp at puck.nether.net
AAGE> http://puck.nether.net/mailman/listinfo/juniper-nsp
  
  

 



More information about the juniper-nsp mailing list