mpls-linux-general — Mailing list for general discussion about MPLS for Linux

[mpls-linux-general] Cross Compiling of MPLS and LDP?

[Markus P. <mp...@gi...>]

Has anybody experience in Cross Compiling the Code of MPLS and LDP.

My Archtecture will be a IBM PPC 405 Walnut Board.

My Problem will be that the PPC has a big endian structure.

--=20
Mit freundlichen Gr=FC=DFen / Best Regards

Markus Prison

GIGA STREAM UMTS - TECHNOLOGIES GMBH
Konrad Zuse Stra=DFe 7

66115 Saarbr=FCcken

Tel: +49 681 / 959 16 - 212
Fax: +49 681 / 959 16 - 100
Mobil: +49 170 / 77 30 961
E-Mail: mp...@gi...

[mpls-linux-general] the quesion about traffic balancing

[Folke A. <aeo...@ho...>]

hi, all :)

   i got a problem in balancing my traffic through
my network.

   see the following network topology:
      +------+      +------+     +------+   |
      |      |eth1  |      |     |      |   |10.0.0.0/24
      |      +------+ CORE +-----+      |   +-------
eth0 |      |      |      |     |      |   |
------+ LSR1 |      +------+     | LSR2 +---+
      |      |eth2               |      |   |
      |      +-------------------+      |
      +------+       LINK0       +------+

   all three PCs are running kernel-2.4.19 with a
mpls patch 1.160.

   on lsr1 , i have three ethether net adaptors.

     eth0 is the ingress device
     eth1 has an outgoing label 1
     eth2 has an outgoing label 2

   and two tunnels created by using 'mplsadm -T':

     mpls12 : bind to eth2
     mpls1c : bind to eth1

   and its routing table contains the following
entry:

   10.0.0.0/24 dev mpls12 proto kernel
   core dev mpls1c proto kernel

  now , i want to make a flow with a certain
dst ip address , say , 10.0.0.111, to go throught
this network by balancing the traffic loading
onto eth1 and eth2 on demand.

  e.g. when the direct link between lsr1 and
lsr2 (for convenience we named it LINK0 )are
lighted loaded, the traffic destined to
11.0.0.111 goes out using mpls12 with a label 2.

  when sometimes later, the loading on LINK0
became heavier, i want to shift the traffic
destined to 11.0.0.111 to go out using mpls1c
with label 1.

  can i achieve this ?
  if i can , what should i do then ?

  by the way , i am not using LDP currently.

thanks in advance.

Folke.

_________________________________________________________________
Join the world’s largest e-mail service with MSN Hotmail. 
http://www.hotmail.com

[mpls-linux-general] mplsd crash problem

[craig <cr...@at...>]

hi  James ,

I use kernel 2.4.18 , mpls-linux 1.170 , ldp-portable 0.200 on redhat =
7.2
and I'm sure that zebra , ospfd or ripd works well.

But when I turn on the mpls ldp  on  both  interface  eth1  step-by-step =
,=20
the mplsd crash  on both machine.
=20
It also happen when I use older version mpls-linux and ldp portable.

Could you tell me  what/s wrong ?

                                                                         =
   craig

                +----------+                               +----------+
          eth0|               |  eth1                eth1 |              =
 |  eth0=20
           ----|               | ----------------------- |               =
|  ---
               +-----------+                              +-----------+  =
  192.168.2.1
 140.117.164.26     192.168.3.2          192.168.3.1

all NIC is based on Realtek 8139 chip.


The following is my tracing result ,

2002/10/07 22:12:45 MPLS: MPLSd (0.93a) starts
2002/10/07 22:12:45 MPLS: interface add lo index 1 flags 73 metric 1 mtu =
16436
ENTER: _ldp_global_ifmgr_callback
EXIT: _ldp_global_ifmgr_callback
2002/10/07 22:12:45 MPLS: connected address 127.0.0.1/8 is added
2002/10/07 22:12:45 MPLS: interface add eth0 index 2 flags 4163 metric 1 =
mtu 1500
ENTER: _ldp_global_ifmgr_callback
EXIT: _ldp_global_ifmgr_callback
2002/10/07 22:12:45 MPLS: connected address 192.168.2.1/24 is added
2002/10/07 22:12:45 MPLS: interface add eth1 index 3 flags 4163 metric 1 =
mtu 1500
ENTER: _ldp_global_ifmgr_callback
EXIT: _ldp_global_ifmgr_callback
2002/10/07 22:12:45 MPLS: connected address 192.168.3.1/24 is added
2002/10/07 22:12:45 MPLS: router-id update 192.168.2.1
ENTER: ldp_cfg_global_set
ENTER: ldp_global_shutdown
EXIT: ldp_global_shutdown
EXIT: ldp_cfg_global_set
ENTER: ldp_cfg_global_set
EXIT: ldp_cfg_global_set
ENTER: ldp_cfg_global_set
ENTER: ldp_global_startup
EXIT: ldp_global_startup
EXIT: ldp_cfg_global_set
ENTER: _ldp_global_fib_callback
ENTER: Recognize_New_Fec
EXIT: Recognize_New_Fec
EXIT: _ldp_global_fib_callback
ENTER: _ldp_global_fib_callback
ENTER: Recognize_New_Fec
EXIT: Recognize_New_Fec
EXIT: _ldp_global_fib_callback
ENTER: _ldp_global_fib_callback
ENTER: Recognize_New_Fec
EXIT: Recognize_New_Fec
EXIT: _ldp_global_fib_callback
ENTER: ldp_cfg_if_set
EXIT: ldp_cfg_if_set
ENTER: ldp_cfg_entity_set
PRT: ldp_cfg_entity_set: entity not ready

EXIT: ldp_cfg_entity_set
ENTER: ldp_cfg_entity_set
ENTER: ldp_entity_startup
ENTER: ldp_if_startup
OUT: Interface update received for lo: Interface update received for =
eth0: Interface update received for eth1: Hello Send: entity(1)
OUT: LPD Header : protocolVersion =3D 1
OUT:  pduLength =3D 30
OUT:  lsrAddress =3D c0a80201
OUT:  labelSpace =3D 0
OUT: HELLO MSG ***START***:
OUT:  baseMsg : uBit =3D 0
OUT:     msgType =3D 100
OUT:     msgLength =3D 20
OUT:     msgId =3D 1
OUT:   chpTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 400
OUT:     length =3D 4
OUT:   chpTlv data: holdTime =3D 15
OUT:   chpTlv Flags:  target =3D 0
OUT:    request =3D 0
OUT:    res =3D 0
OUT:  Hello msg does not have TrAdr TLV
OUT:   csnTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 402
OUT:     length =3D 4
OUT:   csnTlv data: value =3D 9
OUT: HELLO MSG ***END***:
EXIT: ldp_if_startup
EXIT: ldp_entity_startup
EXIT: ldp_cfg_entity_set
ENTER: ldp_event
ENTER: ldp_session_create_passive
OUT: ldp_session_create_passive: (1) changed to NON_EXIST
EXIT: ldp_session_create_passive
ENTER: ldp_state_machine
OUT: FSM: state 1, event 1
ENTER: ldp_state_connect
OUT: ldp_state_connect: (1) changed to INITIALIZED
EXIT: ldp_state_connect
EXIT: ldp_state_machine
EXIT: ldp_event
ENTER: ldp_event
ENTER: ldp_buf_process
ENTER: ldp_decode_header
OUT: 00 01 00 20 00 00 00 00 00 00=20
EXIT: ldp_decode_header
ENTER: ldp_decode_one_mesg
OUT: Found type 200
OUT: 02 00 00 16 00 00 00 02 05 00 00 0e 00 01 00 2d=20
OUT: 00 00 10 00 c0 a8 02 01 00 00=20
OUT: decodedSize for Init msg =3D 26
OUT: LPD Header : protocolVersion =3D 1
OUT:  pduLength =3D 32
OUT:  lsrAddress =3D 0
OUT:  labelSpace =3D 0
OUT: INIT MSG ***START***:
OUT:  baseMsg : uBit =3D 0
OUT:     msgType =3D 200
OUT:     msgLength =3D 22
OUT:     msgId =3D 2
OUT:  CSP:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 500
OUT:     length =3D 14
OUT:  csp        : protocolVersion =3D 1
OUT:   holdTime =3D 45
OUT:   maxPduLen =3D 4096
OUT:   rcvLsrAddress =3D c0a80201
OUT:   rcvLsId =3D 0
OUT:  CSP Flags: lad =3D 0, ld =3D 0, pvl =3D 0, res =3D 0
OUT:  INIT msg does NOT have ASP
OUT:  INIT msg does NOT have FSP
OUT:=20
INIT MSG ***END***
OUT: Mesg size: 26 (36)
EXIT: ldp_decode_one_mesg
ENTER: ldp_state_machine
OUT: FSM: state 2, event 2
ENTER: ldp_state_recv_init
PRT: ldp_state_recv_init: cannot find adj

EXIT: ldp_state_recv_init-error
EXIT: ldp_state_machine
EXIT: ldp_buf_process
OUT: ldp_event: FAILURE executing a CLOSE
ENTER: ldp_state_machine
OUT: FSM: state 2, event 7
ENTER: ldp_state_close
ENTER: ldp_session_shutdown
OUT: ldp_session_shutdown: (1) changed to NONE
session delete
EXIT: ldp_session_shutdown
EXIT: ldp_state_close
EXIT: ldp_state_machine
EXIT: ldp_event
ENTER: ldp_event
ENTER: ldp_buf_process
ENTER: ldp_decode_header
OUT: 00 01 00 1e 00 00 00 00 00 00=20
EXIT: ldp_decode_header
ENTER: ldp_decode_one_mesg
OUT: Found type 100
OUT: 01 00 00 14 00 00 00 01 04 00 00 04 00 0f 00 00=20
OUT: 04 02 00 04 00 00 00 06=20
OUT: decodedSize for Hello msg =3D 24
OUT: LPD Header : protocolVersion =3D 1
OUT:  pduLength =3D 30
OUT:  lsrAddress =3D 0
OUT:  labelSpace =3D 0
OUT: HELLO MSG ***START***:
OUT:  baseMsg : uBit =3D 0
OUT:     msgType =3D 100
OUT:     msgLength =3D 20
OUT:     msgId =3D 1
OUT:   chpTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 400
OUT:     length =3D 4
OUT:   chpTlv data: holdTime =3D 15
OUT:   chpTlv Flags:  target =3D 0
OUT:    request =3D 0
OUT:    res =3D 0
OUT:  Hello msg does not have TrAdr TLV
OUT:   csnTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 402
OUT:     length =3D 4
OUT:   csnTlv data: value =3D 6
OUT: HELLO MSG ***END***:
OUT: Mesg size: 24 (34)
EXIT: ldp_decode_one_mesg
ENTER: ldp_state_machine
OUT: FSM: state 0, event 0
ENTER: ldp_state_new_adjacency
ENTER: ldp_hello_process
OUT: Hello Recv: entity(1)
OUT: ldp_hello_process: PASSIVE(1)
ENTER: ldp_adj_backoff_stop
EXIT: ldp_adj_backoff_stop
EXIT: ldp_hello_process
ENTER: ldp_adj_startup
EXIT: ldp_adj_startup
EXIT: ldp_state_new_adjacency
EXIT: ldp_state_machine
EXIT: ldp_buf_process
ENTER: ldp_buf_process
OUT: ldp_event: LDP_EVENT_UDP_DATA errno =3D 11
EXIT: ldp_buf_process
EXIT: ldp_event
OUT: Hello Send fired: entity(1)
OUT: Hello Send: entity(1)
OUT: LPD Header : protocolVersion =3D 1
OUT:  pduLength =3D 30
OUT:  lsrAddress =3D c0a80201
OUT:  labelSpace =3D 0
OUT: HELLO MSG ***START***:
OUT:  baseMsg : uBit =3D 0
OUT:     msgType =3D 100
OUT:     msgLength =3D 20
OUT:     msgId =3D 1
OUT:   chpTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 400
OUT:     length =3D 4
OUT:   chpTlv data: holdTime =3D 15
OUT:   chpTlv Flags:  target =3D 0
OUT:    request =3D 0
OUT:    res =3D 0
OUT:  Hello msg does not have TrAdr TLV
OUT:   csnTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 402
OUT:     length =3D 4
OUT:   csnTlv data: value =3D 9
OUT: HELLO MSG ***END***:
ENTER: ldp_event
ENTER: ldp_buf_process
ENTER: ldp_decode_header
OUT: 00 01 00 1e 00 00 00 00 00 00=20
EXIT: ldp_decode_header
ENTER: ldp_decode_one_mesg
OUT: Found type 100
OUT: 01 00 00 14 00 00 00 01 04 00 00 04 00 0f 00 00=20
OUT: 04 02 00 04 00 00 00 06=20
OUT: decodedSize for Hello msg =3D 24
OUT: LPD Header : protocolVersion =3D 1
OUT:  pduLength =3D 30
OUT:  lsrAddress =3D 0
OUT:  labelSpace =3D 0
OUT: HELLO MSG ***START***:
OUT:  baseMsg : uBit =3D 0
OUT:     msgType =3D 100
OUT:     msgLength =3D 20
OUT:     msgId =3D 1
OUT:   chpTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 400
OUT:     length =3D 4
OUT:   chpTlv data: holdTime =3D 15
OUT:   chpTlv Flags:  target =3D 0
OUT:    request =3D 0
OUT:    res =3D 0
OUT:  Hello msg does not have TrAdr TLV
OUT:   csnTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 402
OUT:     length =3D 4
OUT:   csnTlv data: value =3D 6
OUT: HELLO MSG ***END***:
OUT: Mesg size: 24 (34)
EXIT: ldp_decode_one_mesg
ENTER: ldp_state_machine
OUT: FSM: state 1, event 0
ENTER: ldp_state_maintainance
ENTER: ldp_hello_process
OUT: Hello Recv: entity(1)
OUT: ldp_hello_process: PASSIVE(1)
ENTER: ldp_adj_backoff_stop
EXIT: ldp_adj_backoff_stop
EXIT: ldp_hello_process
ENTER: ldp_adj_maintain_timer
EXIT: ldp_adj_maintain_timer
EXIT: ldp_state_maintainance
EXIT: ldp_state_machine
EXIT: ldp_buf_process
ENTER: ldp_buf_process
OUT: ldp_event: LDP_EVENT_UDP_DATA errno =3D 11
EXIT: ldp_buf_process
EXIT: ldp_event
OUT: Hello Send fired: entity(1)
OUT: Hello Send: entity(1)
OUT: LPD Header : protocolVersion =3D 1
OUT:  pduLength =3D 30
OUT:  lsrAddress =3D c0a80201
OUT:  labelSpace =3D 0
OUT: HELLO MSG ***START***:
OUT:  baseMsg : uBit =3D 0
OUT:     msgType =3D 100
OUT:     msgLength =3D 20
OUT:     msgId =3D 1
OUT:   chpTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 400
OUT:     length =3D 4
OUT:   chpTlv data: holdTime =3D 15
OUT:   chpTlv Flags:  target =3D 0
OUT:    request =3D 0
OUT:    res =3D 0
OUT:  Hello msg does not have TrAdr TLV
OUT:   csnTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 402
OUT:     length =3D 4
OUT:   csnTlv data: value =3D 9
OUT: HELLO MSG ***END***:
ENTER: ldp_event
ENTER: ldp_buf_process
ENTER: ldp_decode_header
OUT: 00 01 00 1e 00 00 00 00 00 00=20
EXIT: ldp_decode_header
ENTER: ldp_decode_one_mesg
OUT: Found type 100
OUT: 01 00 00 14 00 00 00 01 04 00 00 04 00 0f 00 00=20
OUT: 04 02 00 04 00 00 00 06=20
OUT: decodedSize for Hello msg =3D 24
OUT: LPD Header : protocolVersion =3D 1
OUT:  pduLength =3D 30
OUT:  lsrAddress =3D 0
OUT:  labelSpace =3D 0
OUT: HELLO MSG ***START***:
OUT:  baseMsg : uBit =3D 0
OUT:     msgType =3D 100
OUT:     msgLength =3D 20
OUT:     msgId =3D 1
OUT:   chpTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 400
OUT:     length =3D 4
OUT:   chpTlv data: holdTime =3D 15
OUT:   chpTlv Flags:  target =3D 0
OUT:    request =3D 0
OUT:    res =3D 0
OUT:  Hello msg does not have TrAdr TLV
OUT:   csnTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 402
OUT:     length =3D 4
OUT:   csnTlv data: value =3D 6
OUT: HELLO MSG ***END***:
OUT: Mesg size: 24 (34)
EXIT: ldp_decode_one_mesg
ENTER: ldp_state_machine
OUT: FSM: state 1, event 0
ENTER: ldp_state_maintainance
ENTER: ldp_hello_process
OUT: Hello Recv: entity(1)
OUT: ldp_hello_process: PASSIVE(1)
ENTER: ldp_adj_backoff_stop
EXIT: ldp_adj_backoff_stop
EXIT: ldp_hello_process
ENTER: ldp_adj_maintain_timer
EXIT: ldp_adj_maintain_timer
EXIT: ldp_state_maintainance
EXIT: ldp_state_machine
EXIT: ldp_buf_process
ENTER: ldp_buf_process
OUT: ldp_event: LDP_EVENT_UDP_DATA errno =3D 11
EXIT: ldp_buf_process
EXIT: ldp_event
ENTER: ldp_event
ENTER: ldp_session_create_passive
OUT: ldp_session_create_passive: (2) changed to NON_EXIST
EXIT: ldp_session_create_passive
ENTER: ldp_state_machine
OUT: FSM: state 1, event 1
ENTER: ldp_state_connect
OUT: ldp_state_connect: (2) changed to INITIALIZED
EXIT: ldp_state_connect
EXIT: ldp_state_machine
EXIT: ldp_event
ENTER: ldp_event
ENTER: ldp_buf_process
ENTER: ldp_decode_header
OUT: 00 01 00 20 00 00 00 00 00 00=20
EXIT: ldp_decode_header
ENTER: ldp_decode_one_mesg
OUT: Found type 200
OUT: 02 00 00 16 00 00 00 03 05 00 00 0e 00 01 00 2d=20
OUT: 00 00 10 00 c0 a8 02 01 00 00=20
OUT: decodedSize for Init msg =3D 26
OUT: LPD Header : protocolVersion =3D 1
OUT:  pduLength =3D 32
OUT:  lsrAddress =3D 0
OUT:  labelSpace =3D 0
OUT: INIT MSG ***START***:
OUT:  baseMsg : uBit =3D 0
OUT:     msgType =3D 200
OUT:     msgLength =3D 22
OUT:     msgId =3D 3
OUT:  CSP:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 500
OUT:     length =3D 14
OUT:  csp        : protocolVersion =3D 1
OUT:   holdTime =3D 45
OUT:   maxPduLen =3D 4096
OUT:   rcvLsrAddress =3D c0a80201
OUT:   rcvLsId =3D 0
OUT:  CSP Flags: lad =3D 0, ld =3D 0, pvl =3D 0, res =3D 0
OUT:  INIT msg does NOT have ASP
OUT:  INIT msg does NOT have FSP
OUT:=20
INIT MSG ***END***
OUT: Mesg size: 26 (36)
EXIT: ldp_decode_one_mesg
ENTER: ldp_state_machine
OUT: FSM: state 2, event 2
ENTER: ldp_state_recv_init
ENTER: ldp_init_process
OUT: Init Recv: session(2)
EXIT: ldp_init_process
OUT: ldp_state_recv_init: (2) changed to OPENREC
ENTER: ldp_init_send
ENTER: ldp_init_create
EXIT: ldp_init_create
OUT: Init Send: session(2)
OUT: LPD Header : protocolVersion =3D 1
OUT:  pduLength =3D 32
OUT:  lsrAddress =3D c0a80201
OUT:  labelSpace =3D 0
OUT: INIT MSG ***START***:
OUT:  baseMsg : uBit =3D 0
OUT:     msgType =3D 200
OUT:     msgLength =3D 22
OUT:     msgId =3D 2
OUT:  CSP:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 500
OUT:     length =3D 14
OUT:  csp        : protocolVersion =3D 1
OUT:   holdTime =3D 45
OUT:   maxPduLen =3D 4096
OUT:   rcvLsrAddress =3D 00000000
OUT:   rcvLsId =3D 0
OUT:  CSP Flags: lad =3D 0, ld =3D 0, pvl =3D 0, res =3D 0
OUT:  INIT msg does NOT have ASP
OUT:  INIT msg does NOT have FSP
OUT:=20
INIT MSG ***END***
EXIT: ldp_init_send
OUT: Keepalive Send: session(2)
OUT: LPD Header : protocolVersion =3D 1
OUT:  pduLength =3D 14
OUT:  lsrAddress =3D c0a80201
OUT:  labelSpace =3D 0
OUT: KEEP ALIVE MSG ***START***:
OUT:  baseMsg : uBit =3D 0
OUT:     msgType =3D 201
OUT:     msgLength =3D 4
OUT:     msgId =3D 3
OUT: KEEP ALIVE MSG ***END***:
EXIT: ldp_state_recv_init
EXIT: ldp_state_machine
EXIT: ldp_buf_process
ENTER: ldp_buf_process
OUT: ldp_event: LDP_EVENT_TCP_DATA errno =3D 11
EXIT: ldp_buf_process
EXIT: ldp_event
OUT: Hello Send fired: entity(1)
OUT: Hello Send: entity(1)
OUT: LPD Header : protocolVersion =3D 1
OUT:  pduLength =3D 30
OUT:  lsrAddress =3D c0a80201
OUT:  labelSpace =3D 0
OUT: HELLO MSG ***START***:
OUT:  baseMsg : uBit =3D 0
OUT:     msgType =3D 100
OUT:     msgLength =3D 20
OUT:     msgId =3D 1
OUT:   chpTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 400
OUT:     length =3D 4
OUT:   chpTlv data: holdTime =3D 15
OUT:   chpTlv Flags:  target =3D 0
OUT:    request =3D 0
OUT:    res =3D 0
OUT:  Hello msg does not have TrAdr TLV
OUT:   csnTlv:
OUT:   Tlv:
OUT:   BaseTlv: uBit =3D 0
OUT:     fBit =3D 0
OUT:     type =3D 402
OUT:     length =3D 4
OUT:   csnTlv data: value =3D 9
OUT: HELLO MSG ***END***:
ENTER: ldp_event
ENTER: ldp_buf_process
ENTER: ldp_decode_header
OUT: 00 01 00 0e 00 00 00 00 00 00=20
EXIT: ldp_decode_header
ENTER: ldp_decode_one_mesg
OUT: Found type 201
OUT: 02 01 00 04 00 00 00 04=20
OUT: decodedSize for KeepAlive msg =3D 8
OUT: LPD Header : protocolVersion =3D 1
OUT:  pduLength =3D 14
OUT:  lsrAddress =3D 0
OUT:  labelSpace =3D 0
OUT: KEEP ALIVE MSG ***START***:
OUT:  baseMsg : uBit =3D 0
OUT:     msgType =3D 201
OUT:     msgLength =3D 4
OUT:     msgId =3D 4
OUT: KEEP ALIVE MSG ***END***:
OUT: Mesg size: 8 (18)
EXIT: ldp_decode_one_mesg
ENTER: ldp_state_machine
OUT: FSM: state 4, event 3
ENTER: ldp_state_finish_init
ENTER: ldp_session_startup
ENTER: ldp_adj_backoff_stop
EXIT: ldp_adj_backoff_stop
OUT: ldp_session_startup: (2) changed to OPERATIONAL

Re: [mpls-linux-general] LDP config... confused!

[James R. L. <jl...@mi...>]

The default behavior for zebra-ldp is to only distribute labels for
the LSR-ID (this can be changed, but only programitically).  The LSR-ID
must be attached to a directly connected interface and must show up as
a /32 in the routing table (this is probably a little too strict, I need to
tweak these rules).  So the easiest way is to use a 'dummy' interface.
Compile your kernel with support for it, then assign a /32 to it through zebra.
Configure OSPF to run passive on the dummy interface.  You should then see
that LDP distruibutes labels for the /32s.

Jim

On Mon, Oct 07, 2002 at 01:50:15PM +0100, Sameer Gharat wrote:
> Hello James and everybody,
> 
> I've managed to set up static LSPs successfully and
> have now moved over to setting up of dynamic LSPs
> using ldp-portable-0.2.
> 
> For this, I'm working with a simple setup of two
> hosts. Host A ==> 10.3.9.87 and Host B ==> 10.3.9.92.
> I have setup and configured zebra, ospfd and mplsd on
> both these machines. My config files are:
> --------------zebra.conf--------------------
> !
> hostname zebra
> password root
> enable password root
> !
> interface eth0
>  ip address 10.3.9.92/0
> !
> log file zebra.log
> 
> --------------ospfd.conf--------------------
> !
> hostname ospfd
> password root
> enable password root
> !
> router ospf
>   network 10.3.0.0/20 area 0
> !
> log stdout
> 
> --------------mplsd.conf--------------------
> !
> hostname mplsd
> password root
> enable password root
> !
> interface eth0
>  mpls ldp
> !
> router zebra
>  mpls ldp
> !
> log file ./mplsd.log
> !
> line vty
> !
> 
> Having done this, when I check up the command "show
> ldp neighbor" after telnetting to mplsd, I can see
> that it has recognized the other machine as the
> neighbor and is exchanging HELLO messages.
> But when, I try to run the command "show ldp
> database", all I get is "no label info has been
> exchanged".
> 
> I am guessing that this means that the LSPs haven't
> been set up since no label info was exchanged.
> 
> Is there something wrong in my config files? ...
> alternatively could you direct me as to how to ensure
> that the label info is exchanged between the two
> hosts.
> 
> Any help would be greatly appreciated.
> 
> Thanking in advance!
> 
> Cheers,
> Sameer
> 
> ________________________________________________________________________
> Missed your favourite TV serial last night? Try the new, Yahoo! TV.
>        visit http://in.tv.yahoo.com
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] LDP config... confused!

[<sam...@ya...>]

Hello James and everybody,

I've managed to set up static LSPs successfully and
have now moved over to setting up of dynamic LSPs
using ldp-portable-0.2.

For this, I'm working with a simple setup of two
hosts. Host A ==> 10.3.9.87 and Host B ==> 10.3.9.92.
I have setup and configured zebra, ospfd and mplsd on
both these machines. My config files are:
--------------zebra.conf--------------------
!
hostname zebra
password root
enable password root
!
interface eth0
 ip address 10.3.9.92/0
!
log file zebra.log

--------------ospfd.conf--------------------
!
hostname ospfd
password root
enable password root
!
router ospf
  network 10.3.0.0/20 area 0
!
log stdout

--------------mplsd.conf--------------------
!
hostname mplsd
password root
enable password root
!
interface eth0
 mpls ldp
!
router zebra
 mpls ldp
!
log file ./mplsd.log
!
line vty
!

Having done this, when I check up the command "show
ldp neighbor" after telnetting to mplsd, I can see
that it has recognized the other machine as the
neighbor and is exchanging HELLO messages.
But when, I try to run the command "show ldp
database", all I get is "no label info has been
exchanged".

I am guessing that this means that the LSPs haven't
been set up since no label info was exchanged.

Is there something wrong in my config files? ...
alternatively could you direct me as to how to ensure
that the label info is exchanged between the two
hosts.

Any help would be greatly appreciated.

Thanking in advance!

Cheers,
Sameer

________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
       visit http://in.tv.yahoo.com

[mpls-linux-general] ldp with ip unnumbered

[Anjaneya P. <anj...@ya...>]

hi ,
the current ldp make it imperative for all the interfaces in a router to have 
an unique ip address. can we have an ldp which can even run even if the 
interfaces are unnumbered....as in ospf. Thus we would not waste ip addresses 
for point-to-point links. 

thnx in advance
anjaneya

Re: [mpls-linux-general] a question about the ldp-portable-0.2

[James R. L. <jl...@mi...>]

You gotta give me more then that.  What is you setup (ascii drawing)
exactly what did you type, exactly what command line did you use
to the processes, etc.  Are you sure your running a MPLS kernel
(did you try and setup static LSPs to test this out).   Try turning
on tracing:

conf t
mpls ldp
trace all
end

The trace output goes to mplsd stdout.

I can't help unless you give me more info.  Your goinna get more of a
response out of me (and learn a heck of a lot more) if you atleast do
some looking around yourself.  (for starters searching the mailing list
and doing packet dumps).

Jim

On Thu, Oct 03, 2002 at 10:16:27PM -0700, Paresh Patil wrote:
> I did this on both the PCs connected by croos-cable
> and issued show ldp neighbor
> But I got reply as "No Discovered neighbor"
> 
> How to get it working?
> 
> Paresh
> 
> --- "James R. Leu" <jl...@mi...> wrote:
> > Currently ldp-portable has a bug which will not
> > allow it to correctly read
> > a config file.  You will need to start mplsd then
> > configure it by hand.
> > 
> > In you setup below, you would telnet to port 1025
> > then login and execute
> > the following commands:
> > 
> > enable
> > <password>
> > conf t
> > mpls ldp
> > exit
> > int eth1
> > mpls ldp
> > end
> > 
> > Then you can issue show commands: show ldp, show ldp
> > neighbor,
> > show ldp database
> > 
> > Good luck.
> > 
> > On Thu, Sep 26, 2002 at 02:26:40PM +0800, Folke Aeon
> > wrote:
> > > hi, all
> > > 
> > >   i am new commr of this community. :)
> > > 
> > >   i am trying to use ldp-portable packet to setup
> > > a lsp .
> > > 
> > >   i did all according to the README.zebra-ldp and
> > > all things happened seemed to be proper:
> > >   patched the zebra cleanly without error notice;
> > >   compiled all the components correctly;
> > >   i have a kernel-2.4.19 patched with mpls patch
> > 1.160;
> > >   i can use mplsadm to setup a static lsp through
> > > my linux systems.
> > > 
> > >   but after i run:
> > >      zebra -f /etc/zebra.conf -P 1023 -d
> > >      ospdd -f /etc/ospfd.conf -P 1024 -d
> > >      mplsd -f /etc/mplsd.conf -P 1025
> > >   as directed in the README.zebra-ldp shipped with
> > > ldp-portable-0.200.tar.gz, nothing happened.i
> > cannot
> > > see anything by 'cat /proc/net/mpls*', and there
> > is
> > > no packets going through between my computers
> > seems
> > > to be a hello message or label request message of
> > > the LDP defined in RFC3036
> > > 
> > >   i think ,maybe i did't write the *.conf file
> > > properly. will anyone here help me to write
> > > the correct config file for mplsd?
> > > 
> > >   my network topology is :
> > > 
> > > #
> > > #   11.0.0.0/24
> > > # -+--------------
> > > #  |             eth0
> > > #  |               +--------+
> > > #  +---------------+ host A +                     
> >    13.0.0.0/8 |
> > > #  |   11.0.0.18/24+--------+                    
> > ---------------+
> > > #  |                                              
> >               |
> > > #  |           eth0                        eth0   
> >               |
> > > #  | 11.0.0.80/24+-------+       
> > 12.0.0.2/8+-------+            |
> > > #  +-------------+ 11-12 +------------------+
> > 12-13 +------------+
> > > #  |             +-------+12.0.0.1/8       
> > +-------+13.0.0.1/8  |
> > > # -+---                 eth1                      
> > eth1          |
> > > #                                                 
> >               |
> > > #   15.0.0.0/8                                    
> >               |
> > > # -+---------------                               
> >               |
> > > #  |           eth1                        eth1   
> >               |
> > > #  |  15.0.0.1/8+--------+       
> > 14.0.0.1/8+-------+            |
> > > #  +------------+ host B +------------------+
> > 13-14 +------------+
> > > #  |            +--------+14.0.0.2/8       
> > +-------+13.0.0.2/8  |
> > > #  |                    eth0                     
> > eth0           |
> > > # -+---
> > > 
> > >      how to write the proper mplsd.conf on host
> > 12-13
> > > and host 13-14 ?
> > > 
> > >   any help is appreciated :)
> > > 
> > >
> >
> _________________________________________________________________
> > > MSN Photos is the easiest way to share and print
> > your photos: 
> > > http://photos.msn.com/support/worldwide.aspx
> > > 
> > > 
> > > 
> > >
> >
> -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > mpls-linux-general mailing list
> > > mpl...@li...
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > 
> > -- 
> > James R. Leu
> > 
> > 
> >
> -------------------------------------------------------
> > This sf.net email is sponsored by: DEDICATED SERVERS
> > only $89!
> > Linux or FreeBSD, FREE setup, FAST network. Get your
> > own server 
> > today at http://www.ServePath.com/indexfm.htm
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> 
> __________________________________________________
> Do you Yahoo!?
> New DSL Internet Access from SBC & Yahoo!
> http://sbc.yahoo.com
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] unsubscribe me

[shanmugam g. <sha...@re...>]

please unsubscribe me
             thanking you

Re: [mpls-linux-general] a question about the ldp-portable-0.2

[Paresh P. <par...@ya...>]

I did this on both the PCs connected by croos-cable
and issued show ldp neighbor
But I got reply as "No Discovered neighbor"

How to get it working?

Paresh

--- "James R. Leu" <jl...@mi...> wrote:
> Currently ldp-portable has a bug which will not
> allow it to correctly read
> a config file.  You will need to start mplsd then
> configure it by hand.
> 
> In you setup below, you would telnet to port 1025
> then login and execute
> the following commands:
> 
> enable
> <password>
> conf t
> mpls ldp
> exit
> int eth1
> mpls ldp
> end
> 
> Then you can issue show commands: show ldp, show ldp
> neighbor,
> show ldp database
> 
> Good luck.
> 
> On Thu, Sep 26, 2002 at 02:26:40PM +0800, Folke Aeon
> wrote:
> > hi, all
> > 
> >   i am new commr of this community. :)
> > 
> >   i am trying to use ldp-portable packet to setup
> > a lsp .
> > 
> >   i did all according to the README.zebra-ldp and
> > all things happened seemed to be proper:
> >   patched the zebra cleanly without error notice;
> >   compiled all the components correctly;
> >   i have a kernel-2.4.19 patched with mpls patch
> 1.160;
> >   i can use mplsadm to setup a static lsp through
> > my linux systems.
> > 
> >   but after i run:
> >      zebra -f /etc/zebra.conf -P 1023 -d
> >      ospdd -f /etc/ospfd.conf -P 1024 -d
> >      mplsd -f /etc/mplsd.conf -P 1025
> >   as directed in the README.zebra-ldp shipped with
> > ldp-portable-0.200.tar.gz, nothing happened.i
> cannot
> > see anything by 'cat /proc/net/mpls*', and there
> is
> > no packets going through between my computers
> seems
> > to be a hello message or label request message of
> > the LDP defined in RFC3036
> > 
> >   i think ,maybe i did't write the *.conf file
> > properly. will anyone here help me to write
> > the correct config file for mplsd?
> > 
> >   my network topology is :
> > 
> > #
> > #   11.0.0.0/24
> > # -+--------------
> > #  |             eth0
> > #  |               +--------+
> > #  +---------------+ host A +                     
>    13.0.0.0/8 |
> > #  |   11.0.0.18/24+--------+                    
> ---------------+
> > #  |                                              
>               |
> > #  |           eth0                        eth0   
>               |
> > #  | 11.0.0.80/24+-------+       
> 12.0.0.2/8+-------+            |
> > #  +-------------+ 11-12 +------------------+
> 12-13 +------------+
> > #  |             +-------+12.0.0.1/8       
> +-------+13.0.0.1/8  |
> > # -+---                 eth1                      
> eth1          |
> > #                                                 
>               |
> > #   15.0.0.0/8                                    
>               |
> > # -+---------------                               
>               |
> > #  |           eth1                        eth1   
>               |
> > #  |  15.0.0.1/8+--------+       
> 14.0.0.1/8+-------+            |
> > #  +------------+ host B +------------------+
> 13-14 +------------+
> > #  |            +--------+14.0.0.2/8       
> +-------+13.0.0.2/8  |
> > #  |                    eth0                     
> eth0           |
> > # -+---
> > 
> >      how to write the proper mplsd.conf on host
> 12-13
> > and host 13-14 ?
> > 
> >   any help is appreciated :)
> > 
> >
>
_________________________________________________________________
> > MSN Photos is the easiest way to share and print
> your photos: 
> > http://photos.msn.com/support/worldwide.aspx
> > 
> > 
> > 
> >
>
-------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> -- 
> James R. Leu
> 
> 
>
-------------------------------------------------------
> This sf.net email is sponsored by: DEDICATED SERVERS
> only $89!
> Linux or FreeBSD, FREE setup, FAST network. Get your
> own server 
> today at http://www.ServePath.com/indexfm.htm
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
>
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general


__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

Re: [mpls-linux-general] MPLS_Diffserv question ?

[Pim V. H. <pim...@in...>]

On Tue, 2002-10-01 at 16:26, Foroogh Noroozi wrote:
> Dear Madam/Sir,
> I am a beginner in MPLS,
> I want to know is there any source code on MPLS_Diffserv implementation on
> linux,
you might want to have a look at:

DiffServ/MPLS(RSVP-TE) for Linux:
http://dsmpls.atlantis.rug.ac.be

Pim.
> Regards,
> Noroozi
>           _\\|//_
>           ( O-O )
> ~~~~~~~o00~~(_)~~00o~~~~~
> 
> Email :no...@me...
> 
>        oooO
> ~~~~~~~(   )~~Oooo~~~~~~
>         \ (   (   )
>          \_)   ) /
>               (_/
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: DEDICATED SERVERS only $89!
> Linux or FreeBSD, FREE setup, FAST network. Get your own server 
> today at http://www.ServePath.com/indexfm.htm
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> 
-- 
Pim Van Heuven            Ghent University - IMEC
Department  of  Information  Technology   (INTEC)
Sint-Pietersnieuwstraat, 41 B-9000, Gent, Belgium
pim...@in...
        DiffServ/MPLS(RSVP-TE) for Linux:
        http://dsmpls.atlantis.rug.ac.be

Re: [mpls-linux-general] MPLS_Diffserv question ?

[James R. L. <jl...@mi...>]

mpls-linux-1.1 has Diffserv capbilities in the MPLS forwarding plane.

Take a look at:

http://dsmpls.atlantis.rug.ac.be/

Which uses mpls-linux-1.1

On Tue, Oct 01, 2002 at 05:56:11PM +0330, Foroogh Noroozi wrote:
> Dear Madam/Sir,
> I am a beginner in MPLS,
> I want to know is there any source code on MPLS_Diffserv implementation on
> linux,
> Regards,
> Noroozi
>           _\\|//_
>           ( O-O )
> ~~~~~~~o00~~(_)~~00o~~~~~
> 
> Email :no...@me...
> 
>        oooO
> ~~~~~~~(   )~~Oooo~~~~~~
>         \ (   (   )
>          \_)   ) /
>               (_/
> 
> 
> 
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: DEDICATED SERVERS only $89!
> Linux or FreeBSD, FREE setup, FAST network. Get your own server 
> today at http://www.ServePath.com/indexfm.htm
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

[mpls-linux-general] MPLS_Diffserv question ?

[Foroogh N. <no...@ce...>]

Dear Madam/Sir,
I am a beginner in MPLS,
I want to know is there any source code on MPLS_Diffserv implementation on
linux,
Regards,
Noroozi
          _\\|//_
          ( O-O )
~~~~~~~o00~~(_)~~00o~~~~~

Email :no...@me...

       oooO
~~~~~~~(   )~~Oooo~~~~~~
        \ (   (   )
         \_)   ) /
              (_/

Re: [mpls-linux-general] a question about the ldp-portable-0.2

[James R. L. <jl...@mi...>]

Currently ldp-portable has a bug which will not allow it to correctly read
a config file.  You will need to start mplsd then configure it by hand.

In you setup below, you would telnet to port 1025 then login and execute
the following commands:

enable
<password>
conf t
mpls ldp
exit
int eth1
mpls ldp
end

Then you can issue show commands: show ldp, show ldp neighbor,
show ldp database

Good luck.

On Thu, Sep 26, 2002 at 02:26:40PM +0800, Folke Aeon wrote:
> hi, all
> 
>   i am new commr of this community. :)
> 
>   i am trying to use ldp-portable packet to setup
> a lsp .
> 
>   i did all according to the README.zebra-ldp and
> all things happened seemed to be proper:
>   patched the zebra cleanly without error notice;
>   compiled all the components correctly;
>   i have a kernel-2.4.19 patched with mpls patch 1.160;
>   i can use mplsadm to setup a static lsp through
> my linux systems.
> 
>   but after i run:
>      zebra -f /etc/zebra.conf -P 1023 -d
>      ospdd -f /etc/ospfd.conf -P 1024 -d
>      mplsd -f /etc/mplsd.conf -P 1025
>   as directed in the README.zebra-ldp shipped with
> ldp-portable-0.200.tar.gz, nothing happened.i cannot
> see anything by 'cat /proc/net/mpls*', and there is
> no packets going through between my computers seems
> to be a hello message or label request message of
> the LDP defined in RFC3036
> 
>   i think ,maybe i did't write the *.conf file
> properly. will anyone here help me to write
> the correct config file for mplsd?
> 
>   my network topology is :
> 
> #
> #   11.0.0.0/24
> # -+--------------
> #  |             eth0
> #  |               +--------+
> #  +---------------+ host A +                         13.0.0.0/8 |
> #  |   11.0.0.18/24+--------+                     ---------------+
> #  |                                                             |
> #  |           eth0                        eth0                  |
> #  | 11.0.0.80/24+-------+        12.0.0.2/8+-------+            |
> #  +-------------+ 11-12 +------------------+ 12-13 +------------+
> #  |             +-------+12.0.0.1/8        +-------+13.0.0.1/8  |
> # -+---                 eth1                       eth1          |
> #                                                                |
> #   15.0.0.0/8                                                   |
> # -+---------------                                              |
> #  |           eth1                        eth1                  |
> #  |  15.0.0.1/8+--------+        14.0.0.1/8+-------+            |
> #  +------------+ host B +------------------+ 13-14 +------------+
> #  |            +--------+14.0.0.2/8        +-------+13.0.0.2/8  |
> #  |                    eth0                      eth0           |
> # -+---
> 
>      how to write the proper mplsd.conf on host 12-13
> and host 13-14 ?
> 
>   any help is appreciated :)
> 
> _________________________________________________________________
> MSN Photos is the easiest way to share and print your photos: 
> http://photos.msn.com/support/worldwide.aspx
> 
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] Example zebra + ospfd + mplsd configs

[James R. L. <jl...@mi...>]

On Mon, Sep 30, 2002 at 10:56:39PM -0700, Paresh Patil wrote:
> Hello James,
> 
> Thanks for your reply. I am quite new to this. I don't
> know what these conf t or mpls ldp means! Will you
> please explain it a bit? And main thing is how to log
> into mplsd daemon.
> What I normally do is-
> I cd to .../zebra-0.93a/mplsd 
> and then ./mplsd
> but that just says that MPLSd started. takes in
> nothing or nothing happens. No entries made anywhere!

I thing the first thing you should do is learn how to setup a basic OSPF
network using zebra.  Head over to zebra.org (http://zebra.org/) read up
on zebra and how to go about running zebra/ospfd to setup an OSPF network.
Once you have gotten that for you can apply what you've learned to mplsd (it
fits into the picture much like ospfd does, so you will end up running zebra
ospfd and mplsd on the same machine)

Have fun.

> --- "James R. Leu" <jl...@mi...> wrote:
> > You will have to log into the mplsd daemon and
> > configure it.  Here is a
> > sample of what you will have to configure after you
> > login.
> > 
> > enable
> > <password>
> > conf t
> > mpls ldp
> > exit
> > int eth1
> > mpls ldp
> > end
> > 
> > 
> > Unfortunately you cannot startup mplsd with a config
> > and expect it to work
> > (known bug that I'm working on).
> > 
> > Jim
> > 
> > On Mon, Sep 30, 2002 at 04:24:43AM -0700, Paresh
> > Patil wrote:
> > > After setting up ldp on zebra on Linux; how to
> > write
> > > mplsd.conf
> > > How to make this LDP working?
> > > 
> > > Paresh
> > > 
> > > __________________________________________________
> > > Do you Yahoo!?
> > > New DSL Internet Access from SBC & Yahoo!
> > > http://sbc.yahoo.com
> > > 
> > > 
> > >
> >
> -------------------------------------------------------
> > > This sf.net email is sponsored by:ThinkGeek
> > > Welcome to geek heaven.
> > > http://thinkgeek.com/sf
> > > _______________________________________________
> > > mpls-linux-general mailing list
> > > mpl...@li...
> > >
> >
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> > 
> > -- 
> > James R. Leu
> > 
> > 
> >
> -------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> >
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> 
> __________________________________________________
> Do you Yahoo!?
> New DSL Internet Access from SBC & Yahoo!
> http://sbc.yahoo.com
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by: DEDICATED SERVERS only $89!
> Linux or FreeBSD, FREE setup, FAST network. Get your own server 
> today at http://www.ServePath.com/indexfm.htm
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] Example zebra + ospfd + mplsd configs

[Paresh P. <par...@ya...>]

Hello James,

Thanks for your reply. I am quite new to this. I don't
know what these conf t or mpls ldp means! Will you
please explain it a bit? And main thing is how to log
into mplsd daemon.
What I normally do is-
I cd to .../zebra-0.93a/mplsd 
and then ./mplsd
but that just says that MPLSd started. takes in
nothing or nothing happens. No entries made anywhere!

Regards,
Paresh

--- "James R. Leu" <jl...@mi...> wrote:
> You will have to log into the mplsd daemon and
> configure it.  Here is a
> sample of what you will have to configure after you
> login.
> 
> enable
> <password>
> conf t
> mpls ldp
> exit
> int eth1
> mpls ldp
> end
> 
> 
> Unfortunately you cannot startup mplsd with a config
> and expect it to work
> (known bug that I'm working on).
> 
> Jim
> 
> On Mon, Sep 30, 2002 at 04:24:43AM -0700, Paresh
> Patil wrote:
> > After setting up ldp on zebra on Linux; how to
> write
> > mplsd.conf
> > How to make this LDP working?
> > 
> > Paresh
> > 
> > __________________________________________________
> > Do you Yahoo!?
> > New DSL Internet Access from SBC & Yahoo!
> > http://sbc.yahoo.com
> > 
> > 
> >
>
-------------------------------------------------------
> > This sf.net email is sponsored by:ThinkGeek
> > Welcome to geek heaven.
> > http://thinkgeek.com/sf
> > _______________________________________________
> > mpls-linux-general mailing list
> > mpl...@li...
> >
>
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> 
> -- 
> James R. Leu
> 
> 
>
-------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
>
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general


__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

Re: [mpls-linux-general] Example zebra + ospfd + mplsd configs

[James R. L. <jl...@mi...>]

You will have to log into the mplsd daemon and configure it.  Here is a
sample of what you will have to configure after you login.

enable
<password>
conf t
mpls ldp
exit
int eth1
mpls ldp
end


Unfortunately you cannot startup mplsd with a config and expect it to work
(known bug that I'm working on).

Jim

On Mon, Sep 30, 2002 at 04:24:43AM -0700, Paresh Patil wrote:
> After setting up ldp on zebra on Linux; how to write
> mplsd.conf
> How to make this LDP working?
> 
> Paresh
> 
> __________________________________________________
> Do you Yahoo!?
> New DSL Internet Access from SBC & Yahoo!
> http://sbc.yahoo.com
> 
> 
> -------------------------------------------------------
> This sf.net email is sponsored by:ThinkGeek
> Welcome to geek heaven.
> http://thinkgeek.com/sf
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu

Re: [mpls-linux-general] Example zebra + ospfd + mplsd configs

[Paresh P. <par...@ya...>]

After setting up ldp on zebra on Linux; how to write
mplsd.conf
How to make this LDP working?

Paresh

__________________________________________________
Do you Yahoo!?
New DSL Internet Access from SBC & Yahoo!
http://sbc.yahoo.com

[mpls-linux-general] Fw: Label

[Alexandre C. <ale...@re...>]

> > A have the following network:
> >
> > A----B---C
> >          |
> >          |
> >         D
> >
> > I already have as LSP from a to C. And i wnat do create another to D, I
> > tryied to use the same label from ABC, to ABD, but i think the packets
> that
> > r arriving on D dont belong to the original LSP... 

How can i do a biding with the same label to two diferente destination?

Alex

[mpls-linux-general] Fw: Label

[Alexandre C. <ale...@re...>]

----- Original Message -----
From: "Alexandre Carlos" <ale...@re...>
To: <jl...@mi...>
Sent: Friday, September 27, 2002 9:48 PM
Subject: Label


> A have the following network:
>
> A----B---C
>          |
>          |
>         D
>
> I already have as LSP from a to C. And i wnat do create another to D, I
> tryied to use the same label from ABC, to ABD, but i think the packets
that
> r arriving on D dont belong to the original LSP... I hope u can undesta=
nd.
>
> Alex
> ----- Original Message -----
> From: "James R. Leu" <jl...@mi...>
> To: "Alexandre Carlos" <ale...@re...>
> Sent: Tuesday, September 24, 2002 11:51 PM
> Subject: Re: MPLS label table
>
>
> > That shoul be fine as long as you only plan to use 'ip' while running=
 an
> > MPLS enabled kernel.
> >
> > Jim
> >
> > On Tue, Sep 24, 2002 at 10:46:09PM -0300, Alexandre Carlos wrote:
> > > Jim,
> > > I=B4ve done the following modification on
> > >
> > > /sbin/ mv ip ip.old
> > > and copyed /usr/src/iproute2/ip/ip to sbin.
> > >
> > > With this modification the ip route worked, can i do that?
> > >
> > > Alex
> > > ----- Original Message -----
> > > From: "James R. Leu" <jl...@mi...>
> > > To: "Alexandre Carlos" <ale...@re...>
> > > Sent: Tuesday, September 24, 2002 1:12 PM
> > > Subject: Re: MPLS label table
> > >
> > >
> > > > Nope.  That is why I sent my configs to the mailing list.  (are y=
ou
> > > > on the mailing list?)
> > > >
> > > > Jim
> > > >
> > > > On Tue, Sep 24, 2002 at 12:06:31PM -0300, Alexandre Carlos wrote:
> > > > > I=B4m planning to creat the LSPs using LDP, thats why i=B4m usi=
ng
> ospf...
> > > > >
> > > > > In your documentation is there a tutorial of using LDP to creat=
e
> LSP?
> > > > >
> > > > > Alex
> > > > > ----- Original Message -----
> > > > > From: "James R. Leu" <jl...@mi...>
> > > > > To: "Alexandre Carlos" <ale...@re...>
> > > > > Sent: Tuesday, September 24, 2002 1:04 PM
> > > > > Subject: Re: MPLS label table
> > > > >
> > > > >
> > > > > > If you are planning on creating LSP by hand, you will also wa=
nt
to
> > > create
> > > > > > your routing table by hand.
> > > > > >
> > > > > > If you plan to create LSPs dynamically (via LDP) then you wil=
l
> need a
> > > > > routing
> > > > > > protocol.
> > > > > >
> > > > > > Jim
> > > > > >
> > > > > > On Tue, Sep 24, 2002 at 11:56:10AM -0300, Alexandre Carlos
wrote:
> > > > > > > Jim,
> > > > > > >
> > > > > > > Don=B4t i have to start running any routing protocol? or th=
e
> routing
> > > table
> > > > > > > i=B4ll have to creat manualy?
> > > > > > >
> > > > > > > Alex
> > > > > > > ----- Original Message -----
> > > > > > > From: "James R. Leu" <jl...@mi...>
> > > > > > > To: "Alexandre Carlos" <ale...@re...>
> > > > > > > Sent: Tuesday, September 24, 2002 12:56 AM
> > > > > > > Subject: Re: MPLS label table
> > > > > > >
> > > > > > >
> > > > > > > > Correct.  You cannot add the same route as OSPF has added.
> > > > > > > >
> > > > > > > > On Mon, Sep 23, 2002 at 11:45:25PM -0300, Alexandre Carlo=
s
> wrote:
> > > > > > > > > Jim the ospfd is running, and i already have that route=
,
so
> i
> > > think
> > > > > > > thats
> > > > > > > > > why i=B4m not adding a new route.
> > > > > > > > >
> > > > > > > > > I=B4m i right?
> > > > > > > > >
> > > > > > > > > Alex
> > > > > > > > > ----- Original Message -----
> > > > > > > > > From: "James R. Leu" <jl...@mi...>
> > > > > > > > > To: "Alexandre Carlos" <ale...@re...>
> > > > > > > > > Sent: Tuesday, September 24, 2002 12:27 AM
> > > > > > > > > Subject: Re: MPLS label table
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > > Are you sure you are running an MPLS enabled kernel?
> > > > > > > > > >
> > > > > > > > > > Here is what I do (note I have installed my MPLS enab=
led
> > > binaries
> > > > > in
> > > > > > > the
> > > > > > > > > > directory /mpls)
> > > > > > > > > >
> > > > > > > > > > [root uml-1 8:27pm]~-> ifconfig eth1 11.0.1.1 netmask
> > > > > 255.255.255.0
> > > > > > > > > > [root uml-1 8:28pm]~-> /mpls/mplsadm2 -A -O 0
> > > > > > > > > > Key: 0x00000002
> > > > > > > > > > Out Segment add: Success
> > > > > > > > > > [root uml-1 8:29pm]~-> /mpls/mplsadm2 -O 0x2 -o
> > > > > > > > > push:gen:16:set:eth1:ipv4:11.0.1.2
> > > > > > > > > > Out Instr: Success
> > > > > > > > > > [root uml-1 8:30pm]~-> /mpls/ip route add 11.0.2.0/24
via
> > > 11.0.1.2
> > > > > lsp
> > > > > > > 0x2
> > > > > > > > > > [root uml-1 8:30pm]~-> more /proc/net/mpls_out
> > > > > > > > > > 0x00000002 0/0/0 1 PUSH(gen 16) SET(eth1,11.0.1.2)
> > > > > > > > > > [root uml-1 8:32pm]~-> /mpls/ip route show
> > > > > > > > > > 11.0.2.0/24 via 11.0.1.2 dev eth1 lsp 0x2
> > > > > > > > > > 192.168.2.0/24 dev eth0  proto kernel  scope link  sr=
c
> > > > > 192.168.2.101
> > > > > > > > > > 11.0.1.0/24 dev eth1  proto kernel  scope link  src
> 11.0.1.1
> > > > > > > > > > 127.0.0.0/8 dev lo  scope link
> > > > > > > > > >
> > > > > > > > > > On Mon, Sep 23, 2002 at 11:12:53PM -0300, Alexandre
Carlos
> > > wrote:
> > > > > > > > > > > Jim, I=B4m just start learning linux...
> > > > > > > > > > >
> > > > > > > > > > > I typed the following line ./ip/ip route add ...
> > > > > > > > > > >
> > > > > > > > > > > rtnetlink answer; invalid argument, what i did wron=
g?
> I=B4ve
> > > done
> > > > > > > > > everytinhg
> > > > > > > > > > > as u told to
> > > > > > > > > > >
> > > > > > > > > > > Alex
> > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > From: "James R. Leu" <jl...@mi...>
> > > > > > > > > > > To: "Alexandre Carlos" <ale...@re...>
> > > > > > > > > > > Sent: Tuesday, September 24, 2002 12:08 AM
> > > > > > > > > > > Subject: Re: MPLS label table
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > > If you are in the iproute2 directory, type ./ip/i=
p
> > > > > > > > > > > >
> > > > > > > > > > > > Are you familar with how a unix/linux shell searc=
hes
> for
> > > > > > > executable
> > > > > > > > > files?
> > > > > > > > > > > >
> > > > > > > > > > > > Jim
> > > > > > > > > > > >
> > > > > > > > > > > > On Mon, Sep 23, 2002 at 10:52:58PM -0300, Alexand=
re
> Carlos
> > > > > wrote:
> > > > > > > > > > > > > When i type ./ip route add ... on the iproute2
> directory
> > > i
> > > > > > > receive
> > > > > > > > > the
> > > > > > > > > > > > > message ./ip is a directory...
> > > > > > > > > > > > >
> > > > > > > > > > > > > Alex
> > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > From: "James R. Leu" <jl...@mi...>
> > > > > > > > > > > > > To: "Alexandre Carlos" <ale...@re...>
> > > > > > > > > > > > > Sent: Monday, September 23, 2002 11:49 PM
> > > > > > > > > > > > > Subject: Re: MPLS label table
> > > > > > > > > > > > >
> > > > > > > > > > > > >
> > > > > > > > > > > > > > Do you type just 'ip' or do you type './ip' o=
r
do
> you
> > > type
> > > > > > > > > something
> > > > > > > > > > > > > > like '/home/jleu/iproute2/ip/ip'?
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > Jim
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > On Mon, Sep 23, 2002 at 10:44:46PM -0300,
> Alexandre
> > > Carlos
> > > > > > > wrote:
> > > > > > > > > > > > > > > Jim i=B4ve just re-installed the iproute2  =
and
> patched
> > > > > > > iproute2,
> > > > > > > > > but
> > > > > > > > > > > still
> > > > > > > > > > > > > > > have the same error
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > Alex
> > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > From: "James R. Leu" <jl...@mi...>
> > > > > > > > > > > > > > > To: "Alexandre Carlos"
<ale...@re...>
> > > > > > > > > > > > > > > Sent: Monday, September 23, 2002 11:18 PM
> > > > > > > > > > > > > > > Subject: Re: MPLS label table
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Did you download the source to iproute2 a=
nd
> patch
> > > it
> > > > > with
> > > > > > > > > iproute2
> > > > > > > > > > > > > diff
> > > > > > > > > > > > > > > > from mpls-linux?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Are you specifing the path to 'ip'?
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > Jim
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > On Mon, Sep 23, 2002 at 10:09:27PM -0300,
> > > Alexandre
> > > > > Carlos
> > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > error: either "to" is duplicate, or "ls=
p"
is
> a
> > > > > garbage
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > Alex
> > > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > > From: "James R. Leu" <jleu@mindspring.c=
om>
> > > > > > > > > > > > > > > > > To: "Alexandre Carlos"
> <ale...@re...>
> > > > > > > > > > > > > > > > > Sent: Monday, September 23, 2002 11:04 =
PM
> > > > > > > > > > > > > > > > > Subject: Re: MPLS label table
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > What is the error mesg?
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > Jim
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > On Mon, Sep 23, 2002 at
10:00:37PM -0300,
> > > > > Alexandre
> > > > > > > Carlos
> > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > Jim,
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > When i type the following command i=
p
> route
> > > add
> > > > > > > > > > > 182.168.1.1/24
> > > > > > > > > > > > > lsp
> > > > > > > > > > > > > > > > > 0x00000008
> > > > > > > > > > > > > > > > > > > i receive an error message, do u kn=
ow
> why?
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > Alex
> > > > > > > > > > > > > > > > > > > ----- Original Message -----
> > > > > > > > > > > > > > > > > > > From: "James R. Leu"
> <jl...@mi...>
> > > > > > > > > > > > > > > > > > > To: "Alexandre Carlos"
> > > <ale...@re...>
> > > > > > > > > > > > > > > > > > > Sent: Monday, September 23, 2002 11=
:00
> PM
> > > > > > > > > > > > > > > > > > > Subject: Re: MPLS label table
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > /proc/net/mpls_*
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > On Mon, Sep 23, 2002 at
> 07:02:08PM -0300,
> > > > > > > Alexandre
> > > > > > > > > Carlos
> > > > > > > > > > > > > wrote:
> > > > > > > > > > > > > > > > > > > > > Jim,
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Where can i see my lable?
> > > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > > Alex
> > > > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > > > James R. Leu
> > > > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > > > James R. Leu
> > > > > > > > > > > > > > > >
> > > > > > > > > > > > > > > > --
> > > > > > > > > > > > > > > > James R. Leu
> > > > > > > > > > > > > >
> > > > > > > > > > > > > > --
> > > > > > > > > > > > > > James R. Leu
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > James R. Leu
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > James R. Leu
> > > > > > > >
> > > > > > > > --
> > > > > > > > James R. Leu
> > > > > >
> > > > > > --
> > > > > > James R. Leu
> > > >
> > > > --
> > > > James R. Leu
> >
> > --
> > James R. Leu
>

[mpls-linux-general] a question about the ldp-portable-0.2

[Folke A. <aeo...@ho...>]

hi, all

  i am new commr of this community. :)

  i am trying to use ldp-portable packet to setup
a lsp .

  i did all according to the README.zebra-ldp and
all things happened seemed to be proper:
  patched the zebra cleanly without error notice;
  compiled all the components correctly;
  i have a kernel-2.4.19 patched with mpls patch 1.160;
  i can use mplsadm to setup a static lsp through
my linux systems.

  but after i run:
     zebra -f /etc/zebra.conf -P 1023 -d
     ospdd -f /etc/ospfd.conf -P 1024 -d
     mplsd -f /etc/mplsd.conf -P 1025
  as directed in the README.zebra-ldp shipped with
ldp-portable-0.200.tar.gz, nothing happened.i cannot
see anything by 'cat /proc/net/mpls*', and there is
no packets going through between my computers seems
to be a hello message or label request message of
the LDP defined in RFC3036

  i think ,maybe i did't write the *.conf file
properly. will anyone here help me to write
the correct config file for mplsd?

  my network topology is :

#
#   11.0.0.0/24
# -+--------------
#  |             eth0
#  |               +--------+
#  +---------------+ host A +                         13.0.0.0/8 |
#  |   11.0.0.18/24+--------+                     ---------------+
#  |                                                             |
#  |           eth0                        eth0                  |
#  | 11.0.0.80/24+-------+        12.0.0.2/8+-------+            |
#  +-------------+ 11-12 +------------------+ 12-13 +------------+
#  |             +-------+12.0.0.1/8        +-------+13.0.0.1/8  |
# -+---                 eth1                       eth1          |
#                                                                |
#   15.0.0.0/8                                                   |
# -+---------------                                              |
#  |           eth1                        eth1                  |
#  |  15.0.0.1/8+--------+        14.0.0.1/8+-------+            |
#  +------------+ host B +------------------+ 13-14 +------------+
#  |            +--------+14.0.0.2/8        +-------+13.0.0.2/8  |
#  |                    eth0                      eth0           |
# -+---

     how to write the proper mplsd.conf on host 12-13
and host 13-14 ?

  any help is appreciated :)

_________________________________________________________________
MSN Photos is the easiest way to share and print your photos: 
http://photos.msn.com/support/worldwide.aspx

Re: [mpls-linux-general] Routing table

[Miguel G. <mg...@fi...>]

If you're asking how to delete an output or input you've created with
mplsadm, you have to use mplsadm -D <whatever> to delete it.
To remove a route read the man pages from iproute2 if that is what you're
using.
Miguel.

On Tue, 24 Sep 2002, Alexandre Carlos wrote:

> What is the command to delete all the routing table?
>
> Alex
>

[mpls-linux-general] Routing table

[Alexandre C. <ale...@re...>]

What is the command to delete all the routing table?

Alex

RE: [mpls-linux-general] MPLS over synchronous serial interfaces

[David.Nisbet <Dav...@uk...>]

Hi,

I posed this same question a month back. The Farsite cards currently use the kernel supplied 'syncppp' driver which supports a limited ppp capability and cisco hdlc. In the more recent driver release they have a patch which allows the generic hdlc driver to be used when frame relay is required. Neither (as far as I know) is natively able to handle MPLS.
I have tried hacking an MPLSCP into the sync ppp driver based on the pppd code and this is looking promising. I'm afraid I haven't tried to change the hdlc code.

David

-----Original Message-----
From: Leigh Porter [mailto:le...@bl...]
Sent: 24 September 2002 09:53
To: jl...@mi...
Cc: mpl...@li...
Subject: Re: [mpls-linux-general] MPLS over synchronous serial
interfaces


Hiya,


Thanks, but no PPP as the link is unidirectional so it'll have to be 
HDLC. I'll take a look
at the code they supply with the cards (if they let me have it) and see 
what their HDLC
drivers look like.

--
Leigh Porter


James R. Leu wrote:

>I have not used it over a sync interface yet.  If you can run PPP over the
>interface, and you can use pppd to negotiate PPP capabilities.  If so,
>then all you should need to do is use a MPLS enabled kernel and a 
>patched version of pppd.
>
>Jim
>
>On Tue, Sep 24, 2002 at 02:45:10AM +0100, Leigh Porter wrote:
>  
>
>>Hiya,
>>
>>Does anybody know if the MPLS code will forward MPLS over some of the
>>readily available (Linux supported) synch serial interfaces around such 
>>as the
>>interfaces available from:
>>
>>http://www.farsite.co.uk/tcp_ip_ppp_x.21_v.35_pci_cards/farsync_x21_v35_card_Linux.htm
>>
>>?
>>
>>Thanks,
>>Leigh Porter
>>
>>
>>
>>
>>-------------------------------------------------------
>>This sf.net email is sponsored by:ThinkGeek
>>Welcome to geek heaven.
>>http://thinkgeek.com/sf
>>_______________________________________________
>>mpls-linux-general mailing list
>>mpl...@li...
>>https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>>    
>>
>
>  
>



-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
_______________________________________________
mpls-linux-general mailing list
mpl...@li...
https://lists.sourceforge.net/lists/listinfo/mpls-linux-general


*******************************************************************************
This email and any files transmitted with it are intended solely for the use of
the individual or entity to whom they are addressed and may not be divulged to
any third party without the express permission of the originator.  Any views
expressed in this message are those of the individual sender, except where the
sender specifically states them to be the views of Thales Research Ltd.
*******************************************************************************

Re: [mpls-linux-general] MPLS over synchronous serial interfaces

[James R. L. <jl...@mi...>]

In the case of HDLC, it just might work.  The protocol encoding on HDLC
is the same as on ethernet.

Jim

On Tue, Sep 24, 2002 at 09:53:06AM +0100, Leigh Porter wrote:
> Hiya,
> 
> 
> Thanks, but no PPP as the link is unidirectional so it'll have to be 
> HDLC. I'll take a look
> at the code they supply with the cards (if they let me have it) and see 
> what their HDLC
> drivers look like.
> 
> --
> Leigh Porter
> 
> 
> James R. Leu wrote:
> 
> >I have not used it over a sync interface yet.  If you can run PPP over the
> >interface, and you can use pppd to negotiate PPP capabilities.  If so,
> >then all you should need to do is use a MPLS enabled kernel and a 
> >patched version of pppd.
> >
> >Jim
> >
> >On Tue, Sep 24, 2002 at 02:45:10AM +0100, Leigh Porter wrote:
> >  
> >
> >>Hiya,
> >>
> >>Does anybody know if the MPLS code will forward MPLS over some of the
> >>readily available (Linux supported) synch serial interfaces around such 
> >>as the
> >>interfaces available from:
> >>
> >>http://www.farsite.co.uk/tcp_ip_ppp_x.21_v.35_pci_cards/farsync_x21_v35_card_Linux.htm
> >>
> >>?
> >>
> >>Thanks,
> >>Leigh Porter
> >>
> >>
> >>
> >>
> >>-------------------------------------------------------
> >>This sf.net email is sponsored by:ThinkGeek
> >>Welcome to geek heaven.
> >>http://thinkgeek.com/sf
> >>_______________________________________________
> >>mpls-linux-general mailing list
> >>mpl...@li...
> >>https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
> >>    
> >>
> >
> >  
> >

-- 
James R. Leu

Re: [mpls-linux-general] MPLS over synchronous serial interfaces

[Leigh P. <le...@bl...>]

Hiya,


Thanks, but no PPP as the link is unidirectional so it'll have to be 
HDLC. I'll take a look
at the code they supply with the cards (if they let me have it) and see 
what their HDLC
drivers look like.

--
Leigh Porter


James R. Leu wrote:

>I have not used it over a sync interface yet.  If you can run PPP over the
>interface, and you can use pppd to negotiate PPP capabilities.  If so,
>then all you should need to do is use a MPLS enabled kernel and a 
>patched version of pppd.
>
>Jim
>
>On Tue, Sep 24, 2002 at 02:45:10AM +0100, Leigh Porter wrote:
>  
>
>>Hiya,
>>
>>Does anybody know if the MPLS code will forward MPLS over some of the
>>readily available (Linux supported) synch serial interfaces around such 
>>as the
>>interfaces available from:
>>
>>http://www.farsite.co.uk/tcp_ip_ppp_x.21_v.35_pci_cards/farsync_x21_v35_card_Linux.htm
>>
>>?
>>
>>Thanks,
>>Leigh Porter
>>
>>
>>
>>
>>-------------------------------------------------------
>>This sf.net email is sponsored by:ThinkGeek
>>Welcome to geek heaven.
>>http://thinkgeek.com/sf
>>_______________________________________________
>>mpls-linux-general mailing list
>>mpl...@li...
>>https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>>    
>>
>
>  
>