Re: [mpls-linux-general] MPLS for Linux: IPv4 over MPLS: two LER example for mpls-linux-1.95x

[Giuseppe B. <giu...@gm...>]

hi, please forget previus message, i understand the example and now it
work great, i simply use my only eth0 in client A with the command :

ip route add 192.168.1.4 via 192.168.0.2 src 192.168.0.1

or it's the same with

ip route add 192.168.1.0/24 via 192.168.0.2 dev eth0

sorry for mail, now i'm working with adriana popa example for diffserv
over MPLS by L-LSP, hope it's works great like EoMPLS,
best regards


2009/6/14 Giuseppe Boncompagni <giu...@gm...>:
> Hello,
>
> I'm new to linux and new to mpls and I'm my final college project is
> based on mpls.
>
> I've install all Mpls repo for fedora core 8, and everything sound
> good, i'de like to realize Eth over mpls and my configuration is like
> MPLS for Linux: IPv4 over MPLS: two LER example for mpls-linux-1.95x
> but in the host A when i do the command :
>
> ip route add 10.0.0.2/32 via 192.168.0.2 src 10.0.0.1
>
> the responce is
>
> RTNETLINK answers: Invalid argument
>
> i've tried to load mpls4 module but it's the same, probabily i don't
> undestard the meaning of dummy0 10.0.0.1/32 for the host A and similar
> to host B:
> my hostA have only one eth with 192.168.0.1 ip..
> thx a lot !
> Giuseppe
>
>
>                           172.16.0.0/24
> 10.0.0.1/32                            |                             10.0.0.2/32
>  dummy0                             |                               dummy0
>    |                                       |
>           |
>  --------eth1   eth1------eth2   v   eth2------eth3   eth3--------
> | HOST A |---------| LER1 |-------------| LER2 |---------| HOST B |
>  --------.1   ^          2------.2                3------.3   ^    4--------
>                    |                                                  |
>                    |                                                  |
>        192.168.0.0/24                             192.168.1.0/24
>
> Traffic from HOST A to HOST B
> =============================
>
> HOST A
> ------
> ip route add 10.0.0.2/32 via 192.168.0.2 src 10.0.0.1
>
> LER1
> -----
> mpls nhlfe add key 0 instructions push gen 1000 nexthop eth2 ipv4 172.16.0.3
> (returns key 0x2)
> ip route add 10.0.0.2/32 via 172.16.0.3 mpls 0x2
> echo 1 > /proc/sys/net/ipv4/ip_forward
>
> LER2
> -----
> mpls labelspace set dev eth2 labelspace 0
> mpls ilm add label gen 1000 labelspace 0
> mpls nhlfe add key 0 instructions nexthop eth3 ipv4 192.168.1.4
> (returns key 0x2)
> mpls xc add ilm_label gen 1000 ilm_labelspace 0 nhlfe_key 0x2
>
> Traffic from HOST B to HOST A
> =============================
>
> HOST B
> ------
> ip route add 10.0.0.1/32 via 192.168.1.3 src 10.0.0.2
>
> LER2
> -----
> mpls nhlfe add key 0 instructions push gen 2000 nexthop eth2 ipv4 172.16.0.2
> (returns key 0x3)
> ip route add 10.0.0.1/32 via 172.16.0.2 mpls 0x3
> echo 1 > /proc/sys/net/ipv4/ip_forward
>
> LER1
> -----
> mpls labelspace set dev eth2 labelspace 0
> mpls ilm add label gen 2000 labelspace 0
> mpls nhlfe add key 0 instructions nexthop eth1 ipv4 192.168.0.1
> (returns key 0x3)
> mpls xc add ilm_label gen 2000 ilm_labelspace 0 nhlfe_key 0x3
>
> NOTES
> -----
> Make sure the MTU of the link between LER1 and LER2 is 4 bytes greater then
> the MTU of the links between HOST A/LER1 and HOST B/LER2.
>
> Think about it, here is what a IPv4 packet going from HOST A to HOST B
> looks like on the link from LER1 to LER2:
>
> {ler2 mac|ler1 mac|0x8847|1000,0,1,255|IP payload}
>