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

Re: [mpls-linux-general] mpls-quagga RPMs?

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

That is the last of the RPMs I need to build for F10.  I'm getting
some errors in my netlink code.  Once I have that finished up
and I've completed my testing, I will send an announcement.

On Mon, Jun 08, 2009 at 02:25:43PM -0700, Scott Whyte wrote:
> mpls-linux-general,
> 
> I've managed to build everything in the git repo except mpls-quagga.  I 
> thought I'd just try the RPMs, but I don't see quagga-mpls anywhere in 
> http://mpls-linux.sourceforge.net/fedora/8/i386/
> 
> Can someone point me to a Fedora 8 or (preferably) Fedora 10 RPM for 
> quagga-mpls?
> 
> TIA,
> Scott
> 
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables unlimited
> royalty-free distribution of the report engine for externally facing 
> server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu
jl...@mi...

[mpls-linux-general] mpls-quagga RPMs?

[Scott W. <sw...@go...>]

mpls-linux-general,

I've managed to build everything in the git repo except mpls-quagga.  I 
thought I'd just try the RPMs, but I don't see quagga-mpls anywhere in 
http://mpls-linux.sourceforge.net/fedora/8/i386/

Can someone point me to a Fedora 8 or (preferably) Fedora 10 RPM for 
quagga-mpls?

TIA,
Scott

Re: [mpls-linux-general] Problems running EoMPLS example

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

No, you're not missing anything.  It has been a while since I've
touched the EoMPLS code so I'm thinking there was some bit rot on the
ebtables side of things.  I'm going to start testing my Fedora 10 RPMs
in the coming week, as part of that testing I will validate that EoMPLS
is working (or fix it :-)

On Fri, Jun 05, 2009 at 01:26:37PM -0300, Ismael Grehs wrote:
> Hi,
> 
> I'm trying to run the Ethernet over MPLS example
> (http://apps.sourceforge.net/mediawiki/mpls-linux/index.php?title=Examples),
> however LER1 is freezing after about 10 seconds the ebtables
> configuration is set. Some packets arrived succesfully at LER2 before
> the crash.
> 
> Am I missing something here?
> 
> Thanks,
> Ismael
> 
> ------------------------------------------------------------------------------
> OpenSolaris 2009.06 is a cutting edge operating system for enterprises 
> looking to deploy the next generation of Solaris that includes the latest 
> innovations from Sun and the OpenSource community. Download a copy and 
> enjoy capabilities such as Networking, Storage and Virtualization. 
> Go to: http://p.sf.net/sfu/opensolaris-get
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu
jl...@mi...

[mpls-linux-general] Problems running EoMPLS example

[Ismael G. <ism...@gm...>]

Hi,

I'm trying to run the Ethernet over MPLS example
(http://apps.sourceforge.net/mediawiki/mpls-linux/index.php?title=Examples),
however LER1 is freezing after about 10 seconds the ebtables
configuration is set. Some packets arrived succesfully at LER2 before
the crash.

Am I missing something here?

Thanks,
Ismael

Re: [mpls-linux-general] mpls in layer 2 equipment (pc working as switch)

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

The nexthop logic that is associated with a NHLFE is designed to
figure out how to deliver the MPLS packet to the next device.
In the linux kernel this is done via the 'neighbour' sub system which
handles all of the possible link types and there associated addressing
models.

It would be easy to modify the 'mpls' command to accept a MAC address
'nexthop eth1 MAC 00:0a:0a:0a:0a:0a', but I'm not quite sure how
easy it is to by-pass the neighbour subsystem.

If we get that far, then you could create MPLS tunnel interfaces
on your ingress LERs and point IP routes down the tunnels or use
ebtables to map ingress ethernet frames to an LSP.

I'm trying to finish up converting my development environment
and build scripts to GIT.  Once that is done I could start to look
into the feasability of use MACs as nexthops.

On Thu, May 28, 2009 at 11:52:28AM +0100, Ricardo Faria wrote:
> Hello.
> 
> It is possible to use MPLS in a layer 2 (data link) equipment? 
> 
> I want to connect several pcs, with IPs, with layer 2 equipments (pc working
> as switch) running MPLS. This means that this switch-pcs don't have IPs.
> Therefore, the mpls nhlfe command cannot be performed between 2 switch-pcs,
> (again, no IP exists, only MAC). 
> 
> Also, I cannot make ip route add. 
> 
> Any suggestion?
> 
>  
> 
> Thanks, 
> 
> Ricardo
> 
>  
> 

> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT 
> is a gathering of tech-side developers & brand creativity professionals. Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, & 
> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian 
> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general


-- 
James R. Leu
jl...@mi...

Re: [mpls-linux-general] mpls in layer 2 equipment (pc working as switch)

[Adrian P. <adr...@gm...>]

Hello Ricardo,

By design, MPLS was not intended to run on switches. It was intended to
replace IP lookup in core routers - so it expects it connects routers. You
don't need MPLS for layer 2 because switches don't do "best match" table
lookup (like IP routers)- so the operation is not so costly.

You can connect 2 PCs in a simulated LAN environment over MPLS by creating a
layer 2 MPLS tunnel that will transport your Layer 2 traffic between the
PCs. Look at the Layer 2 VPN examples in the documentation if this is what
you are looking for. However, your PC Switches will need IPs on some
interfaces to communicate.

Regards,
Adrian

On Thu, May 28, 2009 at 1:52 PM, Ricardo Faria <ric...@fe...>wrote:

>   Hello.
>
> It is possible to use MPLS in a layer 2 (data link) equipment?
>
> I want to connect several pcs, with IPs, with layer 2 equipments (pc
> working as switch) running MPLS. This means that this switch-pcs don’t have
> IPs. Therefore, the mpls nhlfe command cannot be performed between 2
> switch-pcs, (again, no IP exists, only MAC).
>
> Also, I cannot make ip route add.
>
> Any suggestion?
>
>
>
> Thanks,
>
> Ricardo
>
>
>
>
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals.
> Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, &
> iPhoneDevCamp as they present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://p.sf.net/sfu/creativitycat-com
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
>

[mpls-linux-general] mpls in layer 2 equipment (pc working as switch)

[Ricardo F. <ric...@fe...>]

Hello.

It is possible to use MPLS in a layer 2 (data link) equipment? 

I want to connect several pcs, with IPs, with layer 2 equipments (pc working
as switch) running MPLS. This means that this switch-pcs don't have IPs.
Therefore, the mpls nhlfe command cannot be performed between 2 switch-pcs,
(again, no IP exists, only MAC). 

Also, I cannot make ip route add. 

Any suggestion?

 

Thanks, 

Ricardo

 

Re: [mpls-linux-general] LDP-Portable download

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

Felipe,

I was able to clone it using:

    git clone git://repo.or.cz/mpls-ldp-portable.git

maybe my instructions at mpls-linux.fs.net are not accurate?

On Mon, May 25, 2009 at 10:34:53AM -0300, fsm...@in... wrote:
> Hello,
> 
> I've been trying to download the ldp-portable from  
> repo.or.cz/mpls-ldp-portable.git but i did not succeed. It seems that  
> the repository isn't online. How do i download ldp-portable?
> 
> Thanks for your help,
> 
> Felipe
> 
> ----------------------------------------------------------------
> This message was sent using IMP, the Internet Messaging Program.
> 
> 
> 
> ------------------------------------------------------------------------------
> Register Now for Creativity and Technology (CaT), June 3rd, NYC. CaT
> is a gathering of tech-side developers & brand creativity professionals. Meet
> the minds behind Google Creative Lab, Visual Complexity, Processing, & 
> iPhoneDevCamp asthey present alongside digital heavyweights like Barbarian
> Group, R/GA, & Big Spaceship. http://www.creativitycat.com 
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general

-- 
James R. Leu
jl...@mi...

[mpls-linux-general] LDP-Portable download

[<fsm...@in...>]

Hello,

I've been trying to download the ldp-portable from  
repo.or.cz/mpls-ldp-portable.git but i did not succeed. It seems that  
the repository isn't online. How do i download ldp-portable?

Thanks for your help,

Felipe

----------------------------------------------------------------
This message was sent using IMP, the Internet Messaging Program.

[mpls-linux-general] Use an ID instead of IP

[Ricardo F. <ric...@fe...>]

Hello,

i want to use MPLS in a ethernet network, layer 2, but to add the mpls
routes i have to use the IP destination.
I was wondering if i use an id, any kind of id, (f.e., mpls nhlfe add
key 0 instructions push gen 1000 nexthop eth5 ipv4 1234), instead of
ip,  and i associate that id with the MAC address off the next
hop/destination, in the arp table, the packets would reach the destination?

Best regards,
Ricardo

Re: [mpls-linux-general] ebtables info

[Adrian P. <adr...@gm...>]

Hello,
You can try by manually setting MAC-IP mappings and bypass the ARP mechanism
(this way you can test your mpls testbed). You can try with something like:
 arp [-v]   [<HW>] [-i <if>] -s  <host> <hwaddr> [temp]            <-Add
entry
 arp -s 1.2.3.4 00:11:22:33:44:55

You can view your mappings with arp -n.

Good luck!


On Tue, May 19, 2009 at 3:29 AM, Ricardo Faria <ric...@fe...>wrote:

> Hello,
> I am doing a network to use MPLS with several terminal machines ( this
> have IPs) and to connect all i have a layer 2 network made by computers
> that are going to route the traffic using MPLS. I need to know, in this
> middle computers, the neightbours MAC to build the path between the
> terminal machines ( that have IPS). My problem is that ARP need to
> associate a MAC to a IP, which i do not have in this middle  computers.
> So i was wondering if ebtables could help me build a "arp" table, i.e.,
> the computer PC2 that is connected to one final terminal PC1 ( that has
> an IP) sends back to the network, in broadcast, a specific frame with is
> own  PC2-MAC, and the terminal PC1 MAC-IP pair. The PC3 listen to this
> frame and stores that the route to the IP of PC1 is using PC2. PC3 does
> exactly the same and so on. PC4 does the as PC2 when PC5 connects to it.
> I want to know if ebtables could help me build specific frames and how
> to send them to the network and how to catch them.
>
>
> EX.:
>
>   PC1----------PC2--------PC3------PC4--------PC5
> (MAC/IP)   (MAC)    (MAC)  (MAC)   (MAC/IP)
>
>
>
>
> If someone could help me i would appreciated.
> Thank you and sorry for the bad spelling english.
>
>
>
> ------------------------------------------------------------------------------
> Crystal Reports - New Free Runtime and 30 Day Trial
> Check out the new simplified licensing option that enables
> unlimited royalty-free distribution of the report engine
> for externally facing server and web deployment.
> http://p.sf.net/sfu/businessobjects
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>

[mpls-linux-general] ebtables info

[Ricardo F. <ric...@fe...>]

Hello,
I am doing a network to use MPLS with several terminal machines ( this
have IPs) and to connect all i have a layer 2 network made by computers
that are going to route the traffic using MPLS. I need to know, in this
middle computers, the neightbours MAC to build the path between the
terminal machines ( that have IPS). My problem is that ARP need to
associate a MAC to a IP, which i do not have in this middle  computers.
So i was wondering if ebtables could help me build a "arp" table, i.e.,
the computer PC2 that is connected to one final terminal PC1 ( that has
an IP) sends back to the network, in broadcast, a specific frame with is
own  PC2-MAC, and the terminal PC1 MAC-IP pair. The PC3 listen to this
frame and stores that the route to the IP of PC1 is using PC2. PC3 does
exactly the same and so on. PC4 does the as PC2 when PC5 connects to it.
I want to know if ebtables could help me build specific frames and how
to send them to the network and how to catch them.


EX.:

   PC1----------PC2--------PC3------PC4--------PC5
(MAC/IP)   (MAC)    (MAC)  (MAC)   (MAC/IP)




If someone could help me i would appreciated.
Thank you and sorry for the bad spelling english.

Re: [mpls-linux-general] MPLS on Virtual machines - no connectivity

[Bowden R. E <REB...@qi...>]

Ricardo,

 

I'm happy to hear that helped.  It took me a while to find the problem
only recently.

 

I tend to look at the packets passing through each router using tcpdump,
very similar to Wireshark but on the command line so it is quicker and
easier to set up but less information.  It will show you the MPLS labels
though, just enter: # tcpdump -i eth5   to display the packets on eth5.
There may be a simpler way.

 

As for your other questions, I will have to leave them to the
development team, I'm a simple user.

 

By the way, if you have any success with iptables or quagga then please
let me know because I am struggling.

 

Thanks,

Richard

 

________________________________

From: Ricardo Faria [mailto:ric...@fe...] 
Sent: 14 May 2009 01:51
To: Bowden Richard E
Cc: mpl...@li...
Subject: RE: [mpls-linux-general] MPLS on Virtual machines - no
connectivity

 

Hello Richard.

Thank you, your  idea worked. I already have response from host B.

By the way, how can I see if the packets sent have the mpls labels? With
Wireshark in each machine? Or is there a simple way?

 

I need to make the mpls paths automatically, (i.e., add a new machine
and create the mpls routes along the way) and also change the mpls
existing module to work in a layer 2  network, instead using IPs in the
command, use MAC addr. Any ideas for where to start?

I appreciate every help.

Thanks.

 

 

From: Bowden Richard 

 

Fedora 8 seems to, by default, have a rule which rejects forwarding ping
requests.  

Look at the contents of all the tables using # iptables -L

Try running # iptables -F FORWARD on LER1 and LER2 to flush the FORWARD
tables.

 

________________________________

From: Ricardo Faria 

 

Hello,

I'm new to mpls and I'm my final college project is based on mpls.

 I was trying to put it to work in fedora 8 virtual machine (VMware). I
installed all the rpms from the rep, getting the mpls 1.962 version on a

i386 kernel, and made 4 copies of that VM. Then follow the "MPLS for
Linux: IPv4 over MPLS: two LER one LSR example for mpls-linux-1.95x", (i
know is not the same version, but i suspect that the commands are the
same).

 

This is my exact configuration:

 

                                                     172.16.0.0/24


10.0.0.2/32                                          |
10.0.0.3/32

  eth4                                                     |
eth7

    |                                                         |

 --------eth3       eth6------eth5    v  eth3------eth5
eth6--------

| HOST A |---------| LER1 |-------------| LER2 |---------| HOST B |

     ---------2    ^        3-------2                      3-------3
^      4--------

                          |
|

                          |
|

            192.168.0.0/24
192.168.1.0/24

 

Host A

ifconfig eth4 10.0.0.2/32

ifconfig eth3 192.168.0.2/24

 

LER1

ifconfig eth6 192.168.0.3/24

ifconfig eth5 172.16.0.2/24

 

LER2

ifconfig eth3 172.16.0.3/24

ifconfig eth5 192.168.1.3/24

 

Host B

ifconfig eth7 10.0.0.3/32

ifconfig eth6 192.168.1.4/24

 

 

Traffic from HOST A to HOST B

=============================

HOST A

------

modprobe mpls4

ip route add 10.0.0.3/32 via 192.168.0.3 src 10.0.0.2

 

LER1

-----

modprobe mpls4

mpls nhlfe add key 0 instructions push gen 1000 nexthop eth5 ipv4
172.16.0.3   (returns key 0x2)

ip route add 10.0.0.3/32 via 172.16.0.3 mpls 0x2

echo 1 > /proc/sys/net/ipv4/ip_forward

 

LER2

-----

modprobe mpls4

mpls labelspace set dev eth3 labelspace 0

mpls ilm add label gen 1000 labelspace 0

mpls nhlfe add key 0 instructions nexthop eth5 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

------

modprobe mpls4

ip route add 10.0.0.2/32 via 192.168.1.3 src 10.0.0.3

 

LER2

-----

modprobe mpls4

mpls nhlfe add key 0 instructions push gen 2000 nexthop eth3 ipv4
172.16.0.2   (returns key 0x3)

ip route add 10.0.0.2/32 via 172.16.0.2 mpls 0x3

echo 1 > /proc/sys/net/ipv4/ip_forward

 

LER1

-----

modprobe mpls4

mpls labelspace set dev eth5 labelspace 0

mpls ilm add label gen 2000 labelspace 0

mpls nhlfe add key 0 instructions nexthop eth6 ipv4 192.168.0.2
(returns key 0x3) 

mpls xc add ilm_label gen 2000 ilm_labelspace 0 nhlfe_key 0x3

 

 

I execute all, but in the end i don't have any connectivity. I would
like to know if a simple ping from host A to Host B should have a
response (witch i already tried without success) , or i have to execute
some special command to test the mpls. Also, for this example, do i have
to add something to iptables or route add something else? Should this
few commands in the example work without nothing else?

In attachment I put the output of the commands: "ip link show", "ip
route show", "mpls nhlfe show", "mpls ilm show", "mpls labelspace show"
and "lsmod" for each computer.

 

Thanks for the help you could give me, but I'm starting with this and
I'm getting a lot of difficulties just to start.

Also if you have other tutorial, i would appreciate that.

 

 


The information contained in this E-Mail and any subsequent 
correspondence is private and is intended solely for the intended 
recipient(s).  The information in this communication may be 
confidential and/or legally privileged.  Nothing in this e-mail is 
intended to conclude a contract on behalf of QinetiQ or make QinetiQ 
subject to any other legally binding commitments, unless the e-mail 
contains an express statement to the contrary or incorporates a formal Purchase Order.

For those other than the recipient any disclosure, copying, 
distribution, or any action taken or omitted to be taken in reliance 
on such information is prohibited and may be unlawful.

Emails and other electronic communication with QinetiQ may be 
monitored and recorded for business purposes including security, audit 
and archival purposes.  Any response to this email indicates consent 
to this.

Telephone calls to QinetiQ may be monitored or recorded for quality 
control, security and other business purposes.

QinetiQ Limited
Registered in England & Wales: Company Number:3796233
Registered office: 85 Buckingham Gate, London SW1E 6PD, United Kingdom
Trading address: Cody Technology Park, Cody Building, Ively Road, Farnborough, Hampshire, GU14 0LX, United Kingdom 
http://www.qinetiq.com/home/notices/legal.html

Re: [mpls-linux-general] MPLS on Virtual machines - no connectivity

[Ricardo F. <ric...@fe...>]

Hello Richard.

Thank you, your  idea worked. I already have response from host B.

By the way, how can I see if the packets sent have the mpls labels? With
Wireshark in each machine? Or is there a simple way?

 

I need to make the mpls paths automatically, (i.e., add a new machine and
create the mpls routes along the way) and also change the mpls existing
module to work in a layer 2  network, instead using IPs in the command, use
MAC addr. Any ideas for where to start?

I appreciate every help.

Thanks.

 

 

From: Bowden Richard 

 

Fedora 8 seems to, by default, have a rule which rejects forwarding ping
requests.  

Look at the contents of all the tables using # iptables -L

Try running # iptables -F FORWARD on LER1 and LER2 to flush the FORWARD
tables.

 

  _____  

From: Ricardo Faria 

 

Hello,

I'm new to mpls and I'm my final college project is based on mpls.

 I was trying to put it to work in fedora 8 virtual machine (VMware). I
installed all the rpms from the rep, getting the mpls 1.962 version on a

i386 kernel, and made 4 copies of that VM. Then follow the "MPLS for Linux:
IPv4 over MPLS: two LER one LSR example for mpls-linux-1.95x", (i know is
not the same version, but i suspect that the commands are the same).

 

This is my exact configuration:

 

                                                     172.16.0.0/24


10.0.0.2/32                                          |
10.0.0.3/32

  eth4                                                     |
eth7

    |                                                         |

 --------eth3       eth6------eth5    v  eth3------eth5       eth6--------

| HOST A |---------| LER1 |-------------| LER2 |---------| HOST B |

     ---------2    ^        3-------2                      3-------3      ^
4--------

                          |
|

                          |
|

            192.168.0.0/24
192.168.1.0/24

 

Host A

ifconfig eth4 10.0.0.2/32

ifconfig eth3 192.168.0.2/24

 

LER1

ifconfig eth6 192.168.0.3/24

ifconfig eth5 172.16.0.2/24

 

LER2

ifconfig eth3 172.16.0.3/24

ifconfig eth5 192.168.1.3/24

 

Host B

ifconfig eth7 10.0.0.3/32

ifconfig eth6 192.168.1.4/24

 

 

Traffic from HOST A to HOST B

=============================

HOST A

------

modprobe mpls4

ip route add 10.0.0.3/32 via 192.168.0.3 src 10.0.0.2

 

LER1

-----

modprobe mpls4

mpls nhlfe add key 0 instructions push gen 1000 nexthop eth5 ipv4 172.16.0.3
(returns key 0x2)

ip route add 10.0.0.3/32 via 172.16.0.3 mpls 0x2

echo 1 > /proc/sys/net/ipv4/ip_forward

 

LER2

-----

modprobe mpls4

mpls labelspace set dev eth3 labelspace 0

mpls ilm add label gen 1000 labelspace 0

mpls nhlfe add key 0 instructions nexthop eth5 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

------

modprobe mpls4

ip route add 10.0.0.2/32 via 192.168.1.3 src 10.0.0.3

 

LER2

-----

modprobe mpls4

mpls nhlfe add key 0 instructions push gen 2000 nexthop eth3 ipv4 172.16.0.2
(returns key 0x3)

ip route add 10.0.0.2/32 via 172.16.0.2 mpls 0x3

echo 1 > /proc/sys/net/ipv4/ip_forward

 

LER1

-----

modprobe mpls4

mpls labelspace set dev eth5 labelspace 0

mpls ilm add label gen 2000 labelspace 0

mpls nhlfe add key 0 instructions nexthop eth6 ipv4 192.168.0.2
(returns key 0x3) 

mpls xc add ilm_label gen 2000 ilm_labelspace 0 nhlfe_key 0x3

 

 

I execute all, but in the end i don't have any connectivity. I would like to
know if a simple ping from host A to Host B should have a response (witch i
already tried without success) , or i have to execute some special command
to test the mpls. Also, for this example, do i have to add something to
iptables or route add something else? Should this few commands in the
example work without nothing else?

In attachment I put the output of the commands: "ip link show", "ip route
show", "mpls nhlfe show", "mpls ilm show", "mpls labelspace show" and
"lsmod" for each computer.

 

Thanks for the help you could give me, but I'm starting with this and I'm
getting a lot of difficulties just to start.

Also if you have other tutorial, i would appreciate that.

 

 

Re: [mpls-linux-general] MPLS on Virtual machines - no connectivity

[Bowden R. E <REB...@qi...>]

Fedora 8 seems to, by default, have a rule which rejects forwarding ping
requests.  

Look at the contents of all the tables using # iptables -L

Try running # iptables -F FORWARD on LER1 and LER2 to flush the FORWARD
tables.

 

________________________________

From: Ricardo Faria [mailto:ric...@fe...] 
Sent: 13 May 2009 01:40
To: mpl...@li...
Subject: [mpls-linux-general] MPLS on Virtual machines - no connectivity

 

Hello,

I'm new to mpls and I'm my final college project is based on mpls.

 I was trying to put it to work in fedora 8 virtual machine (VMware). I
installed all the rpms from the rep, getting the mpls 1.962 version on a

i386 kernel, and made 4 copies of that VM. Then follow the "MPLS for
Linux: IPv4 over MPLS: two LER one LSR example for mpls-linux-1.95x", (i
know is not the same version, but i suspect that the commands are the
same).

 

This is my exact configuration:

 

                                                     172.16.0.0/24


10.0.0.2/32                                          |
10.0.0.3/32

  eth4                                                     |
eth7

    |                                                         |

 --------eth3       eth6------eth5    v  eth3------eth5
eth6--------

| HOST A |---------| LER1 |-------------| LER2 |---------| HOST B |

     ---------2    ^        3-------2                      3-------3
^      4--------

                          |
|

                          |
|

            192.168.0.0/24
192.168.1.0/24

 

Host A

ifconfig eth4 10.0.0.2/32

ifconfig eth3 192.168.0.2/24

 

LER1

ifconfig eth6 192.168.0.3/24

ifconfig eth5 172.16.0.2/24

 

LER2

ifconfig eth3 172.16.0.3/24

ifconfig eth5 192.168.1.3/24

 

Host B

ifconfig eth7 10.0.0.3/32

ifconfig eth6 192.168.1.4/24

 

 

Traffic from HOST A to HOST B

=============================

HOST A

------

modprobe mpls4

ip route add 10.0.0.3/32 via 192.168.0.3 src 10.0.0.2

 

LER1

-----

modprobe mpls4

mpls nhlfe add key 0 instructions push gen 1000 nexthop eth5 ipv4
172.16.0.3   (returns key 0x2)

ip route add 10.0.0.3/32 via 172.16.0.3 mpls 0x2

echo 1 > /proc/sys/net/ipv4/ip_forward

 

LER2

-----

modprobe mpls4

mpls labelspace set dev eth3 labelspace 0

mpls ilm add label gen 1000 labelspace 0

mpls nhlfe add key 0 instructions nexthop eth5 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

------

modprobe mpls4

ip route add 10.0.0.2/32 via 192.168.1.3 src 10.0.0.3

 

LER2

-----

modprobe mpls4

mpls nhlfe add key 0 instructions push gen 2000 nexthop eth3 ipv4
172.16.0.2   (returns key 0x3)

ip route add 10.0.0.2/32 via 172.16.0.2 mpls 0x3

echo 1 > /proc/sys/net/ipv4/ip_forward

 

LER1

-----

modprobe mpls4

mpls labelspace set dev eth5 labelspace 0

mpls ilm add label gen 2000 labelspace 0

mpls nhlfe add key 0 instructions nexthop eth6 ipv4 192.168.0.2
(returns key 0x3) 

mpls xc add ilm_label gen 2000 ilm_labelspace 0 nhlfe_key 0x3

 

 

I execute all, but in the end i don't have any connectivity. I would
like to know if a simple ping from host A to Host B should have a
response (witch i already tried without success) , or i have to execute
some special command to test the mpls. Also, for this example, do i have
to add something to iptables or route add something else? Should this
few commands in the example work without nothing else?

In attachment I put the output of the commands: "ip link show", "ip
route show", "mpls nhlfe show", "mpls ilm show", "mpls labelspace show"
and "lsmod" for each computer.

 

Thanks for the help you could give me, but I'm starting with this and
I'm getting a lot of difficulties just to start.

Also if you have other tutorial, i would appreciate that.

 


The information contained in this E-Mail and any subsequent 
correspondence is private and is intended solely for the intended 
recipient(s).  The information in this communication may be 
confidential and/or legally privileged.  Nothing in this e-mail is 
intended to conclude a contract on behalf of QinetiQ or make QinetiQ 
subject to any other legally binding commitments, unless the e-mail 
contains an express statement to the contrary or incorporates a formal Purchase Order.

For those other than the recipient any disclosure, copying, 
distribution, or any action taken or omitted to be taken in reliance 
on such information is prohibited and may be unlawful.

Emails and other electronic communication with QinetiQ may be 
monitored and recorded for business purposes including security, audit 
and archival purposes.  Any response to this email indicates consent 
to this.

Telephone calls to QinetiQ may be monitored or recorded for quality 
control, security and other business purposes.

QinetiQ Limited
Registered in England & Wales: Company Number:3796233
Registered office: 85 Buckingham Gate, London SW1E 6PD, United Kingdom
Trading address: Cody Technology Park, Cody Building, Ively Road, Farnborough, Hampshire, GU14 0LX, United Kingdom 
http://www.qinetiq.com/home/notices/legal.html

[mpls-linux-general] MPLS on Virtual machines - no connectivity

[Ricardo F. <ric...@fe...>]

Host A

[root@localhost ~]# ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 16436 qdisc noqueue state UNKNOWN
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:0c:29:29:8a:d1 brd ff:ff:ff:ff:ff:ff
3: eth3: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:0c:29:29:8a:db brd ff:ff:ff:ff:ff:ff
4: eth4: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UNKNOWN qlen 1000
    link/ether 00:0c:29:29:8a:e5 brd ff:ff:ff:ff:ff:ff
[root@localhost ~]# ip route show
10.0.0.3 via 192.168.0.3 dev eth3  src 10.0.0.2
192.168.0.0/24 dev eth3  proto kernel  scope link  src 192.168.0.2
192.168.207.0/24 dev eth0  proto kernel  scope link  src 192.168.207.133
[root@localhost ~]# mpls nhlfe show
[root@localhost ~]# mpls ilm show
[root@localhost ~]# mpls labelspace show
LABELSPACE entry dev lo labelspace -1
LABELSPACE entry dev eth0 labelspace -1
LABELSPACE entry dev eth3 labelspace -1
LABELSPACE entry dev eth4 labelspace -1
[root@localhost ~]# lsmod
Module                  Size  Used by
mpls4                   8001  0
autofs4                20933  2
sunrpc                154785  3
nf_conntrack_ipv4      11849  2
ipt_REJECT              6977  2
iptable_filter          6849  1
ip_tables              14033  1 iptable_filter
nf_conntrack_ipv6      16469  2
xt_state                6209  4
nf_conntrack           51221  3 nf_conntrack_ipv4,nf_conntrack_ipv6,xt_state
xt_tcpudp               6977  8
ip6t_ipv6header         6209  2
ip6t_REJECT             7617  2
ip6table_filter         6593  1
ip6_tables             15057  2 ip6t_ipv6header,ip6table_filter
x_tables               15557  7 ipt_REJECT,ip_tables,xt_state,xt_tcpudp,ip6t_ipv6header,ip6t_REJECT,ip6_tables
ipv6                  238789  16 nf_conntrack_ipv6,ip6t_REJECT
loop                   16973  0
dm_multipath           18633  0
snd_ens1371            24161  0
gameport               14029  1 snd_ens1371
snd_rawmidi            21441  1 snd_ens1371
snd_ac97_codec         92517  1 snd_ens1371
ac97_bus                5825  1 snd_ac97_codec
snd_seq_dummy           6853  0
snd_seq_oss            29633  0
snd_seq_midi_event      9921  1 snd_seq_oss
snd_seq                45041  5 snd_seq_dummy,snd_seq_oss,snd_seq_midi_event
snd_seq_device          9933  4 snd_rawmidi,snd_seq_dummy,snd_seq_oss,snd_seq
snd_pcm_oss            37441  0
snd_mixer_oss          16705  1 snd_pcm_oss
snd_pcm                61509  3 snd_ens1371,snd_ac97_codec,snd_pcm_oss
snd_timer              21065  2 snd_seq,snd_pcm
snd                    46437  10 snd_ens1371,snd_rawmidi,snd_ac97_codec,snd_seq_oss,snd_seq,snd_seq_device,snd_pcm_oss,snd_mixer_oss,snd_pcm,snd_timer
ac                      8005  0
i2c_piix4              11473  0
parport_pc             26725  0
pcnet32                31941  0
sg                     31605  0
sr_mod                 17541  0
soundcore               9633  1 snd
pcspkr                  6593  0
i2c_core               20949  1 i2c_piix4
mii                     8385  1 pcnet32
cdrom                  33377  1 sr_mod
parport                32173  1 parport_pc
floppy                 52229  0
snd_page_alloc         11337  1 snd_pcm
ata_piix               19525  0
libata                132065  1 ata_piix
dm_snapshot            18661  0
dm_zero                 5825  0
dm_mirror              19521  0
dm_log                 12229  1 dm_mirror
dm_mod                 48265  10 dm_multipath,dm_snapshot,dm_zero,dm_mirror,dm_log
BusLogic               65973  2
sd_mod                 26329  3
scsi_mod              123917  5 sg,sr_mod,libata,BusLogic,sd_mod
ext3                  110281  2
jbd                    41173  1 ext3
mbcache                10309  1 ext3
uhci_hcd               22993  0
ohci_hcd               22853  0
ehci_hcd               32845  0

Re: [mpls-linux-general] iptables: Invalid argument

[Bowden R. E <REB...@qi...>]

Hi James,

Thanks for your response.

Yes, the mpls4 module seems to load fine and I have been able to work
through several of the examples created by Irina and Adrian.  However, I
am still having this problem with iptables.  I did eventually twig that
the iptables code had moved to xt_mpls and that that module is
auto-loading itself.  However, I am still getting the same error message
' Iptables: Invalid Argument' when I try to run an iptable mpls command.
The command works without the mpls arguments so it is something in the
mpls part.  Has the argument structure changed at all between the
version Irina and Adrian intended (1.950) and the Fedora 8 binaries
(1.962).

Cheers,

Richard

-----Original Message-----
From: James R. Leu [mailto:jl...@mi...] 
Sent: 11 May 2009 05:31
To: Bowden Richard E
Cc: mpl...@li...
Subject: Re: [mpls-linux-general] iptables: Invalid argument

Hello Richard,

Do you have the mpls4 module loaded?

BTW the iptables code is now in xt_mpls and is build as a
module of teh same name.

On Thu, May 07, 2009 at 05:17:29PM +0100, Bowden Richard E wrote:
> Hi,
> 
>  
> 
> I'm trying to work through some of Irina Dumitrascu and Adrian Popa's
> mpls examples but I am struggling to get the examples which use
iptables
> to work.  
> 
>  
> 
> When I run the command:
> 
> # iptables -A FORWARD -m dscp --dscp 0x1a -j mpls --nhlfe 0x2
> 
> The message returned is:
> 
> Iptables: Invalid Argument
> 
>  
> 
> Check it's running the correct version of iptables:
> 
> #yum info iptables
> 
> .....
> 
> Version             1.4.1.1
> 
> Release            2.fc8.mpls.1.962
> 
> Repo                 Installed
> 
> .....
> 
> So we are running the correct iptables.
> 
>  
> 
> So I tried:
> 
> # iptables -A FORWARD -m dscp --dscp 0x1a
> 
> which worked fine and then deleted the entry again.
> 
>  
> 
> Added -j mpls
> 
> # iptables -A FORWARD -m dscp --dscp 0x1a -j mpls
> 
> Get the error message:
> 
> mpls target: parameter --nhlfe is required
> 
>  
> 
> That seems like good news, it understands the mpls bit and is
expecting
> --nhlfe
> 
> # iptables -A FORWARD -m dscp --dscp 0x1a -j mpls -nhlfe
> 
> Unknown arg '--nhlde'
> 
>  
> 
> That seems weird, I was expecting an error because there is no key but
> that error suggests it's not expecting the '--nhlde' argument.
> 
>  
> 
> Just to check that the nhlfe table entry has gone in properly:
> 
> # mpls nhlfe show
> 
> NHLFE entry key 0x00000002 mtu 1492 propogate_ttl
> 
>             Blah blah blah a lot of numbers blah blah blah
> 
>  
> 
> I have installed the kernel, iptables, iproute and ebtables packages
> from the mpls 8 repo (v1.962) to a vanilla Fedora 8 installation in
the
> hopes of keeping everything simple and not have to recompile things.
I
> have also installed the iptables from source.  Can anyone tell me what
> is going wrong?
> 
>  
> 
> One other thing that strikes me as odd: I have seen reference on the
> internet a few times to the ipt_mpls module which it makes sense
should
> be loaded.  Checked lsmod and it's not there.  '# Modprobe ipt_mpls'
> does not return an error but the module still does not show up in
lsmod
> and I can't find an ipt_mpls.ko file anywhere on the computer,
> especially under ..../kernel/net/ipv4/netfilter/ipt_mpls.ko where I'd
> expect to find it.
> 
>  
> 
> I have 
> 
>  
> 
> Richard
> 
>  
> 
> 
> The information contained in this E-Mail and any subsequent 
> correspondence is private and is intended solely for the intended 
> recipient(s).  The information in this communication may be 
> confidential and/or legally privileged.  Nothing in this e-mail is 
> intended to conclude a contract on behalf of QinetiQ or make QinetiQ 
> subject to any other legally binding commitments, unless the e-mail 
> contains an express statement to the contrary or incorporates a formal
Purchase Order.
> 
> For those other than the recipient any disclosure, copying, 
> distribution, or any action taken or omitted to be taken in reliance 
> on such information is prohibited and may be unlawful.
> 
> Emails and other electronic communication with QinetiQ may be 
> monitored and recorded for business purposes including security, audit

> and archival purposes.  Any response to this email indicates consent 
> to this.
> 
> Telephone calls to QinetiQ may be monitored or recorded for quality 
> control, security and other business purposes.
> 
> QinetiQ Limited
> Registered in England & Wales: Company Number:3796233
> Registered office: 85 Buckingham Gate, London SW1E 6PD, United Kingdom
> Trading address: Cody Technology Park, Cody Building, Ively Road,
Farnborough, Hampshire, GU14 0LX, United Kingdom 
> http://www.qinetiq.com/home/notices/legal.html

>
------------------------------------------------------------------------
------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances!
Your
> production scanning environment may not be a perfect world - but
thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW
KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image 
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general


-- 
James R. Leu
jl...@mi...
The QinetiQ e-mail privacy policy and company information is detailed elsewhere in the body of this email.

Re: [mpls-linux-general] iptables: Invalid argument

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

Hello Richard,

Do you have the mpls4 module loaded?

BTW the iptables code is now in xt_mpls and is build as a
module of teh same name.

On Thu, May 07, 2009 at 05:17:29PM +0100, Bowden Richard E wrote:
> Hi,
> 
>  
> 
> I'm trying to work through some of Irina Dumitrascu and Adrian Popa's
> mpls examples but I am struggling to get the examples which use iptables
> to work.  
> 
>  
> 
> When I run the command:
> 
> # iptables -A FORWARD -m dscp --dscp 0x1a -j mpls --nhlfe 0x2
> 
> The message returned is:
> 
> Iptables: Invalid Argument
> 
>  
> 
> Check it's running the correct version of iptables:
> 
> #yum info iptables
> 
> .....
> 
> Version             1.4.1.1
> 
> Release            2.fc8.mpls.1.962
> 
> Repo                 Installed
> 
> .....
> 
> So we are running the correct iptables.
> 
>  
> 
> So I tried:
> 
> # iptables -A FORWARD -m dscp --dscp 0x1a
> 
> which worked fine and then deleted the entry again.
> 
>  
> 
> Added -j mpls
> 
> # iptables -A FORWARD -m dscp --dscp 0x1a -j mpls
> 
> Get the error message:
> 
> mpls target: parameter --nhlfe is required
> 
>  
> 
> That seems like good news, it understands the mpls bit and is expecting
> --nhlfe
> 
> # iptables -A FORWARD -m dscp --dscp 0x1a -j mpls -nhlfe
> 
> Unknown arg '--nhlde'
> 
>  
> 
> That seems weird, I was expecting an error because there is no key but
> that error suggests it's not expecting the '--nhlde' argument.
> 
>  
> 
> Just to check that the nhlfe table entry has gone in properly:
> 
> # mpls nhlfe show
> 
> NHLFE entry key 0x00000002 mtu 1492 propogate_ttl
> 
>             Blah blah blah a lot of numbers blah blah blah
> 
>  
> 
> I have installed the kernel, iptables, iproute and ebtables packages
> from the mpls 8 repo (v1.962) to a vanilla Fedora 8 installation in the
> hopes of keeping everything simple and not have to recompile things.  I
> have also installed the iptables from source.  Can anyone tell me what
> is going wrong?
> 
>  
> 
> One other thing that strikes me as odd: I have seen reference on the
> internet a few times to the ipt_mpls module which it makes sense should
> be loaded.  Checked lsmod and it's not there.  '# Modprobe ipt_mpls'
> does not return an error but the module still does not show up in lsmod
> and I can't find an ipt_mpls.ko file anywhere on the computer,
> especially under ..../kernel/net/ipv4/netfilter/ipt_mpls.ko where I'd
> expect to find it.
> 
>  
> 
> I have 
> 
>  
> 
> Richard
> 
>  
> 
> 
> The information contained in this E-Mail and any subsequent 
> correspondence is private and is intended solely for the intended 
> recipient(s).  The information in this communication may be 
> confidential and/or legally privileged.  Nothing in this e-mail is 
> intended to conclude a contract on behalf of QinetiQ or make QinetiQ 
> subject to any other legally binding commitments, unless the e-mail 
> contains an express statement to the contrary or incorporates a formal Purchase Order.
> 
> For those other than the recipient any disclosure, copying, 
> distribution, or any action taken or omitted to be taken in reliance 
> on such information is prohibited and may be unlawful.
> 
> Emails and other electronic communication with QinetiQ may be 
> monitored and recorded for business purposes including security, audit 
> and archival purposes.  Any response to this email indicates consent 
> to this.
> 
> Telephone calls to QinetiQ may be monitored or recorded for quality 
> control, security and other business purposes.
> 
> QinetiQ Limited
> Registered in England & Wales: Company Number:3796233
> Registered office: 85 Buckingham Gate, London SW1E 6PD, United Kingdom
> Trading address: Cody Technology Park, Cody Building, Ively Road, Farnborough, Hampshire, GU14 0LX, United Kingdom 
> http://www.qinetiq.com/home/notices/legal.html

> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK i700
> Series Scanner you'll get full speed at 300 dpi even with all image 
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general


-- 
James R. Leu
jl...@mi...

Re: [mpls-linux-general] iptables: Invalid argument

[Adrian P. <adr...@gm...>]

Hello Richard,

First of all I'd like to say that the tests done by Irina and me used mpls
version 1.950 and there might be significant differences between this
version and the one you are using in terms of syntax for example.

Secondly - you are right - iptables should be using an ipt_mpls.ko either as
a module (in which case you should find a *mpls* file under
/lib/modules/`uname -r`/*/netfiler/), or it could be compiled into the
kernel (in which case you shouldn't have a file). There's no easy way to
find out, but you could browse your /boot/config-* file for your kernel and
look at the iptables/netfilter configuration. Or you could use that file
(copied to /usr/src/*mykernel*/.config) with make menuconfig and browse to
see the iptables/netfilter configuration.

If it should be a module - you need to load it (modprobe ipt_mpls) before
using it with iptables (although iptables should be able to autoload it on
request AFAIK). If it's built-in, then probably there's a different problem
- maybe James can help.

Good luck,
Adrian

On Thu, May 7, 2009 at 7:17 PM, Bowden Richard E <REB...@qi...>wrote:

>  Hi,
>
>
>
> I’m trying to work through some of Irina Dumitrascu and Adrian Popa’s mpls
> examples but I am struggling to get the examples which use iptables to work.
>
>
>
>
> When I run the command:
>
> # iptables -A FORWARD -m dscp --dscp 0x1a -j mpls --nhlfe 0x2
>
> The message returned is:
>
> Iptables: Invalid Argument
>
>
>
> Check it’s running the correct version of iptables:
>
> #yum info iptables
>
> …..
>
> Version             1.4.1.1
>
> Release            2.fc8.mpls.1.962
>
> Repo                 Installed
>
> …..
>
> So we are running the correct iptables.
>
>
>
> So I tried:
>
> # iptables -A FORWARD -m dscp --dscp 0x1a
>
> which worked fine and then deleted the entry again.
>
>
>
> Added -j mpls
>
> # iptables -A FORWARD -m dscp --dscp 0x1a -j mpls
>
> Get the error message:
>
> mpls target: parameter --nhlfe is required
>
>
>
> That seems like good news, it understands the mpls bit and is expecting
> --nhlfe
>
> # iptables -A FORWARD -m dscp --dscp 0x1a -j mpls –nhlfe
>
> Unknown arg ‘--nhlde’
>
>
>
> That seems weird, I was expecting an error because there is no key but that
> error suggests it’s not expecting the ‘--nhlde’ argument.
>
>
>
> Just to check that the nhlfe table entry has gone in properly:
>
> # mpls nhlfe show
>
> NHLFE entry key 0x00000002 mtu 1492 propogate_ttl
>
>             Blah blah blah a lot of numbers blah blah blah
>
>
>
> I have installed the kernel, iptables, iproute and ebtables packages from
> the mpls 8 repo (v1.962) to a vanilla Fedora 8 installation in the hopes of
> keeping everything simple and not have to recompile things.  I have also
> installed the iptables from source.  Can anyone tell me what is going wrong?
>
>
>
> One other thing that strikes me as odd: I have seen reference on the
> internet a few times to the ipt_mpls module which it makes sense should be
> loaded.  Checked lsmod and it’s not there.  ‘# Modprobe ipt_mpls’ does not
> return an error but the module still does not show up in lsmod and I can’t
> find an ipt_mpls.ko file anywhere on the computer, especially under
> …./kernel/net/ipv4/netfilter/ipt_mpls.ko where I’d expect to find it.
>
>
>
> I have
>
>
>
> Richard
>
>
>
> The information contained in this E-Mail and any subsequent
> correspondence is private and is intended solely for the intended
> recipient(s).  The information in this communication may be
> confidential and/or legally privileged.  Nothing in this e-mail is
> intended to conclude a contract on behalf of QinetiQ or make QinetiQ
> subject to any other legally binding commitments, unless the e-mail
> contains an express statement to the contrary or incorporates a formal
> Purchase Order.
>
> For those other than the recipient any disclosure, copying,
> distribution, or any action taken or omitted to be taken in reliance
> on such information is prohibited and may be unlawful.
>
> Emails and other electronic communication with QinetiQ may be
> monitored and recorded for business purposes including security, audit
> and archival purposes.  Any response to this email indicates consent
> to this.
>
> Telephone calls to QinetiQ may be monitored or recorded for quality
> control, security and other business purposes.
>
> QinetiQ Limited
> Registered in England & Wales: Company Number:3796233
> Registered office: 85 Buckingham Gate, London SW1E 6PD, United Kingdom
> Trading address: Cody Technology Park, Cody Building, Ively Road,
> Farnborough, Hampshire, GU14 0LX, United Kingdom
> http://www.qinetiq.com/home/notices/legal.html<http://www.QinetiQ.com/home/legal.html>
>
>
> ------------------------------------------------------------------------------
> The NEW KODAK i700 Series Scanners deliver under ANY circumstances! Your
> production scanning environment may not be a perfect world - but thanks to
> Kodak, there's a perfect scanner to get the job done! With the NEW KODAK
> i700
> Series Scanner you'll get full speed at 300 dpi even with all image
> processing features enabled. http://p.sf.net/sfu/kodak-com
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>
>

[mpls-linux-general] iptables: Invalid argument

[Bowden R. E <REB...@qi...>]

Hi,

 

I'm trying to work through some of Irina Dumitrascu and Adrian Popa's
mpls examples but I am struggling to get the examples which use iptables
to work.  

 

When I run the command:

# iptables -A FORWARD -m dscp --dscp 0x1a -j mpls --nhlfe 0x2

The message returned is:

Iptables: Invalid Argument

 

Check it's running the correct version of iptables:

#yum info iptables

.....

Version             1.4.1.1

Release            2.fc8.mpls.1.962

Repo                 Installed

.....

So we are running the correct iptables.

 

So I tried:

# iptables -A FORWARD -m dscp --dscp 0x1a

which worked fine and then deleted the entry again.

 

Added -j mpls

# iptables -A FORWARD -m dscp --dscp 0x1a -j mpls

Get the error message:

mpls target: parameter --nhlfe is required

 

That seems like good news, it understands the mpls bit and is expecting
--nhlfe

# iptables -A FORWARD -m dscp --dscp 0x1a -j mpls -nhlfe

Unknown arg '--nhlde'

 

That seems weird, I was expecting an error because there is no key but
that error suggests it's not expecting the '--nhlde' argument.

 

Just to check that the nhlfe table entry has gone in properly:

# mpls nhlfe show

NHLFE entry key 0x00000002 mtu 1492 propogate_ttl

            Blah blah blah a lot of numbers blah blah blah

 

I have installed the kernel, iptables, iproute and ebtables packages
from the mpls 8 repo (v1.962) to a vanilla Fedora 8 installation in the
hopes of keeping everything simple and not have to recompile things.  I
have also installed the iptables from source.  Can anyone tell me what
is going wrong?

 

One other thing that strikes me as odd: I have seen reference on the
internet a few times to the ipt_mpls module which it makes sense should
be loaded.  Checked lsmod and it's not there.  '# Modprobe ipt_mpls'
does not return an error but the module still does not show up in lsmod
and I can't find an ipt_mpls.ko file anywhere on the computer,
especially under ..../kernel/net/ipv4/netfilter/ipt_mpls.ko where I'd
expect to find it.

 

I have 

 

Richard

 


The information contained in this E-Mail and any subsequent 
correspondence is private and is intended solely for the intended 
recipient(s).  The information in this communication may be 
confidential and/or legally privileged.  Nothing in this e-mail is 
intended to conclude a contract on behalf of QinetiQ or make QinetiQ 
subject to any other legally binding commitments, unless the e-mail 
contains an express statement to the contrary or incorporates a formal Purchase Order.

For those other than the recipient any disclosure, copying, 
distribution, or any action taken or omitted to be taken in reliance 
on such information is prohibited and may be unlawful.

Emails and other electronic communication with QinetiQ may be 
monitored and recorded for business purposes including security, audit 
and archival purposes.  Any response to this email indicates consent 
to this.

Telephone calls to QinetiQ may be monitored or recorded for quality 
control, security and other business purposes.

QinetiQ Limited
Registered in England & Wales: Company Number:3796233
Registered office: 85 Buckingham Gate, London SW1E 6PD, United Kingdom
Trading address: Cody Technology Park, Cody Building, Ively Road, Farnborough, Hampshire, GU14 0LX, United Kingdom 
http://www.qinetiq.com/home/notices/legal.html

Re: [mpls-linux-general] mpls on debian

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

If someone can point me to a good howto for building deb's from
source, I would entertain creating a debian build enviroment.

On Tue, Apr 21, 2009 at 12:14:30PM +0200, Giuseppe Boncompagni wrote:
> Hi all,
> could you tell me how is the procedure to use mpls on debian ?
> i've look http://hasso.linux.ee/doku.php/english:network:mpls-linux but whic
> kind of kernel i have to use? 2.4.x ? because i can't install
> linux-kernel-headers_2.5.999-test7-bk-17.mpls.946a_i386.deb<http://hasso.linux.ee/stuff/mpls-linux/linux-kernel-headers_2.5.999-test7-bk-17.mpls.946a_i386.deb>with
> my 2.6.26
> exist a repo or CVS to install all ?or a source code to patch the kernel ?
> Thx a lot
> Giuseppe

> ------------------------------------------------------------------------------
> Stay on top of everything new and different, both inside and 
> around Java (TM) technology - register by April 22, and save
> $200 on the JavaOne (SM) conference, June 2-5, 2009, San Francisco.
> 300 plus technical and hands-on sessions. Register today. 
> Use priority code J9JMT32. http://p.sf.net/sfu/p
> _______________________________________________
> mpls-linux-general mailing list
> mpl...@li...
> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general


-- 
James R. Leu
jl...@mi...

Re: [mpls-linux-general] iptables problem?

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

Tom,

I think I understand the issue you're seeing.  I'm going to try 
to duplicate your setup and see if I can figure out a work around.

On Wed, Apr 22, 2009 at 02:08:48PM +0200, Tom Kleiberg wrote:
> Hello James,
>
> Thanks for your reply. Flushing the cache indeed "solves" the problem.  
> It may be my perception, but I find this behavior somewhat erratic. It  
> basically means that once there are several streams of packets towards a 
> specific destination, albeit with different portnumbers and/or protocol, 
> and there are one or more rules in the mangle table, all the packets to 
> the destination are mangled and mapped onto the LSP. Different streams 
> that match with different rules, are indeed treated differently, which is 
> correct. But packets that do not match any of the rules are also mangled, 
> this I find awkward...or am I mistaken? Is there a way to circumvent this 
> problem?
>
> Thanks for your efforts!!
>
> Tom
>
> Btw, I recently find that the mailinglists are no longer searchable/ 
> browsable on the web.
>
>
>
>
> On Apr 21, 2009, at 6:09 PM, James R. Leu wrote:
>
>> Hello Tom,
>>
>> I'm going to top-post since my response is more generalized:
>>
>> I think you are observing the effects of the Linux route cache.
>> All traffic that goes through the IPv4 stack has two 'stages' to
>> its forwarding.  The first couple of packets go through the 'slow'
>> path in which a full iptables/route lookup is done.  The results
>> of that may be summarized into a route cache entry.  From that point
>> on all traffic that matches the src and dst of the route cache use
>> the 'fast' path and are forwarded according to the contents of the
>> route cache.
>>
>> I believe the route cache entries timeout after ~300 seconds.
>> You can look at the contents of the route cache by doing:
>>
>>    ip route show cache
>>
>> And you can flush it via:
>>
>>    ip route flush cache
>>
>> Does this explain what you are seeing?
>>
>> On Tue, Apr 21, 2009 at 04:21:24PM +0200, Tom Kleiberg wrote:
>>> Hello all,
>>>
>>> I have a question regarding iptables and mpls. I use four nodes (as  
>>> in
>>> the MPLS for Linux example on the SF.net website), mpls version  
>>> 1.962,
>>> FC8. The mpls packages are installed from the repository (so no  
>>> custom
>>> patching etc). I try to filter the packets using iptables and mangle
>>> them so that they are directed onto an LSP, e.g.
>>>
>>> sudo /sbin/mpls nhlfe add key 0 instructions push gen 1001 nexthop  
>>> eth1
>>> ipv4 10.0.0.2
>>> (returns 0x2)
>>> sudo /sbin/iptables -t mangle -A POSTROUTING -s 10.0.0.1 -d  
>>> 10.0.0.10 -p
>>> tcp --source-port 4000 --destination-port 4001 -j mpls --nhlfe 0x2
>>>
>>>
>>> At the downstream nodes, the label is swapped and finally removed at 
>>> the
>>> last hop before the destination.
>>> Now when I generate traffic (using d-itg), I see the following  
>>> tcpdump
>>> at the first downstream node (10.0.0.2):
>>>
>>> 16:01:25.713116 MPLS (label 1001, exp 0, [S], ttl 64)
>>> 	IP (tos 0x0, ttl 64, id 22294, offset 0, flags [DF], proto TCP (6),
>>> length 564) 10.0.0.1.4000 > 10.0.0.10.4001: P 958977:959489(512) ack 
>>> 1
>>> win 46 <nop,nop,timestamp 3001565 3070458>
>>> 16:01:25.713342 IP (tos 0x0, ttl 62, id 4498, offset 0, flags [DF],
>>> proto TCP (6), length 52) 10.0.0.10.4001 > 10.0.0.1.4000: ., cksum
>>> 0xa1e4 (correct), ack 959489 win 5024 <nop,nop,timestamp 3070459
>>> 3001565>
>>> 16:01:25.714115 MPLS (label 1001, exp 0, [S], ttl 64)
>>> 	IP (tos 0x0, ttl 64, id 22295, offset 0, flags [DF], proto TCP (6),
>>> length 564) 10.0.0.1.4000 > 10.0.0.10.4001: P 959489:960001(512) ack 
>>> 1
>>> win 46 <nop,nop,timestamp 3001566 3070459>
>>> 16:01:25.714337 IP (tos 0x0, ttl 62, id 4499, offset 0, flags [DF],
>>> proto TCP (6), length 52) 10.0.0.10.4001 > 10.0.0.1.4000: ., cksum
>>> 0x9fe2 (correct), ack 960001 win 5024 <nop,nop,timestamp 3070460
>>> 3001566>
>>> 16:01:25.715116 MPLS (label 1001, exp 0, [S], ttl 64)
>>> 	IP (tos 0x0, ttl 64, id 22296, offset 0, flags [DF], proto TCP (6),
>>> length 564) 10.0.0.1.4000 > 10.0.0.10.4001: P 960001:960513(512) ack 
>>> 1
>>> win 46 <nop,nop,timestamp 3001567 3070460>
>>> 16:01:25.715339 IP (tos 0x0, ttl 62, id 4500, offset 0, flags [DF],
>>> proto TCP (6), length 52) 10.0.0.10.4001 > 10.0.0.1.4000: ., cksum
>>> 0x9de0 (correct), ack 960513 win 5024 <nop,nop,timestamp 3070461
>>> 3001567>
>>>
>>> However, when I change the source or destination port used by the
>>> traffic generator (or the protocol), then that traffic (which does  
>>> not
>>> match the iptables rule), is still mapped onto the LSP (in this case 
>>> the
>>> destination port is changed to 4002, but any other traffic to  
>>> 10.0.0.10
>>> is in fact mapped onto the LSP).
>>>
>>> 16:11:31.590680 MPLS (label 1001, exp 0, [S], ttl 64)
>>> 	IP (tos 0x0, ttl 64, id 30521, offset 0, flags [DF], proto TCP (6),
>>> length 564) 10.0.0.1.4000 > 10.0.0.10.4002: P 1021953:1022465(512)  
>>> ack 1
>>> win 46 <nop,nop,timestamp 3607443 3676339>
>>> 16:11:31.591011 IP (tos 0x0, ttl 62, id 46089, offset 0, flags [DF],
>>> proto TCP (6), length 52) 10.0.0.10.4002 > 10.0.0.1.4000: ., cksum
>>> 0xeeb5 (correct), ack 1022465 win 5876 <nop,nop,timestamp 3676340
>>> 3607443>
>>> 16:11:31.591681 MPLS (label 1001, exp 0, [S], ttl 64)
>>> 	IP (tos 0x0, ttl 64, id 30522, offset 0, flags [DF], proto TCP (6),
>>> length 564) 10.0.0.1.4000 > 10.0.0.10.4002: P 1022465:1022977(512)  
>>> ack 1
>>> win 46 <nop,nop,timestamp 3607444 3676340>
>>> 16:11:31.592009 IP (tos 0x0, ttl 62, id 46090, offset 0, flags [DF],
>>> proto TCP (6), length 52) 10.0.0.10.4002 > 10.0.0.1.4000: ., cksum
>>> 0xeca3 (correct), ack 1022977 win 5892 <nop,nop,timestamp 3676341
>>> 3607444>
>>> 16:11:31.592681 MPLS (label 1001, exp 0, [S], ttl 64)
>>> 	IP (tos 0x0, ttl 64, id 30523, offset 0, flags [DF], proto TCP (6),
>>> length 564) 10.0.0.1.4000 > 10.0.0.10.4002: P 1022977:1023489(512)  
>>> ack 1
>>> win 46 <nop,nop,timestamp 3607445 3676341>
>>> 16:11:31.593007 IP (tos 0x0, ttl 62, id 46091, offset 0, flags [DF],
>>> proto TCP (6), length 52) 10.0.0.10.4002 > 10.0.0.1.4000: ., cksum
>>> 0xea90 (correct), ack 1023489 win 5909 <nop,nop,timestamp 3676342
>>> 3607445>
>>> 16:11:31.593681 MPLS (label 1001, exp 0, [S], ttl 64)
>>> 	IP (tos 0x0, ttl 64, id 30524, offset 0, flags [DF], proto TCP (6),
>>> length 564) 10.0.0.1.4000 > 10.0.0.10.4002: P 1023489:1024001(512)  
>>> ack 1
>>> win 46 <nop,nop,timestamp 3607446 3676342>
>>> 16:11:31.594005 IP (tos 0x0, ttl 62, id 46092, offset 0, flags [DF],
>>> proto TCP (6), length 52) 10.0.0.10.4002 > 10.0.0.1.4000: ., cksum
>>> 0xe87e (correct), ack 1024001 win 5926 <nop,nop,timestamp 3676342
>>> 3607446>
>>>
>>> When I query the number of packets that match an iptables rule  
>>> (iptables
>>> -t mangle -vnL), the query does not show any increment between after 
>>> the
>>> second batch of traffic is generated (so according to the iptables  
>>> output
>>> the packets that do not match the filter are not mapped onto the LSP,
>>> although in fact it DOES happen).
>>>
>>> More interestingly, the incorrect behavior disappears after some
>>> time...so when I do not send packets from the source to the  
>>> destination,
>>> the filtering recovers itself (until the packets are being send that 
>>> do
>>> match the filter)...
>>>
>>> I hope my question makes sense and someone can help me figure out the
>>> problem.
>>>
>>> thanks
>>> tom
>>>
>>>
>>>
>>
>> -- 
>> James R. Leu
>> jl...@mi...
>

-- 
James R. Leu
jl...@mi...

Re: [mpls-linux-general] configuration problem?

[Ismael G. <ism...@gm...>]

Thank you Tom, I thought there were no modules to load...It's working fine
now :-)
On Fri, Apr 24, 2009 at 4:43 AM, Tom Kleiberg <t.k...@gm...> wrote:

> Hi Ismael,
>
> did you load the mpls module into memory?
>
> % modprobe mpls4
>
> br,
>
> tom
>
>
> On Apr 24, 2009, at 6:27 AM,
> mpl...@li... wrote:
>
>  Send mpls-linux-general mailing list submissions to
>>        mpl...@li...
>>
>> To subscribe or unsubscribe via the World Wide Web, visit
>>        https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>> or, via email, send a message with subject or body 'help' to
>>        mpl...@li...
>>
>> You can reach the person managing the list at
>>        mpl...@li...
>>
>> When replying, please edit your Subject line so it is more specific
>> than "Re: Contents of mpls-linux-general digest..."
>>
>>
>> Today's Topics:
>>
>>  1. [SPAM] 메일 전송 실패 알림 <he...@na...>
>>     (NAV...@na...)
>>  2. configuration problem? (Ismael Grehs)
>>  3. [SPAM] 3 Deadliest Mistakes You Should Nevver      Make in Bed -
>>     You Must Be Aware of This Before It's Too Late (Clemons)
>>
>>
>> ----------------------------------------------------------------------
>>
>> Message: 1
>> Date: Wed, 22 Apr 2009 23:50:22 +0900 (KST)
>> From: <NAV...@na...>
>> Subject: [SPAM] 메일 전송 실패 알림 <he...@na...>
>> To: <mpl...@li...>
>> Message-ID: <49E...@d8...>
>> Content-Type: text/plain; charset="euc-kr"
>>
>>
>> NAVER - http://www.naver.com/
>> --------------------------------------------
>>
>> heikifm ?? ??? ?? <mpls-linux-general Digest, Vol 35, Issue 12> ? ??? ??
>> ??? ?? ??????.
>>
>> --------------------------------------------
>>
>> ???? ??????? ??? ??? ? ????.
>>
>>
>> --------------------------------------------
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>> -------------- next part --------------
>> An embedded message was scrubbed...
>> From: mpl...@li...
>> Subject: mpls-linux-general Digest, Vol 35, Issue 12
>> Date: Wed, 22 Apr 2009 14:49:35 +0000
>> Size: 14830
>>
>> ------------------------------
>>
>> Message: 2
>> Date: Thu, 23 Apr 2009 20:49:27 -0300
>> From: Ismael Grehs <ism...@gm...>
>> Subject: [mpls-linux-general] configuration problem?
>> To: mpl...@li...
>> Message-ID:
>>        <125...@ma...>
>> Content-Type: text/plain; charset=ISO-8859-1
>>
>>
>> Hi all,
>>
>> I'm new to mpls-linux and I got into trouble trying to run the
>> examples from the site.
>> I have a clean Fedora 8 installation with all mpls (1.962) packages
>> from the repository.
>>
>>
>> The problem I got first was on the EoMPLS example, configuring the LER
>> causes an error on the command
>>
>>  ebtables -t nat -A PREROUTING -i eth1 -j mpls --nhlfe 0x2
>>
>> and dmesg showed
>>
>>  mpls: unable to find ETH_P_ALL driver
>>
>>
>> Also, when I tried the example of IPv4 over MPLS on the line
>>
>>  mpls ilm add label gen 1000 labelspace 0
>>
>> got on the terminal
>>
>>  RTNETLINK answers: Cannot allocate memory
>>
>>
>> I have no clue on where to start looking for a possible cause, so any
>> help or idea will be much appreciated.
>>
>> Thanks,
>> Ismael
>>
>>
>>
>> ------------------------------
>>
>> Message: 3
>> Date: Fri, 24 Apr 2009 04:27:15 +0000
>> From: Clemons <mo...@me...>
>> Subject: [mpls-linux-general] [SPAM] 3 Deadliest Mistakes You Should
>>        Nevver  Make in Bed - You Must Be Aware of This Before It's Too
>> Late
>> To: mpl...@li...
>> Message-ID: <49F...@wo...>
>> Content-Type: text/plain; charset="iso-8859-1"
>>
>> It wasn't. Ryland? Emily ryland. No. No, she'd practise revolver shooting
>> in the
>>
>> *3 Deadliest Mistakes You Should Nevver Make in Bed - You Must Be Aware of
>> This Before It's* Too Late
>> <http://groups.yahoo.com/group/posykawapyfek34/message/1>
>>
>> Other operating systems. It exists to provide spider knew the fly he had
>> to inveigle into his foul river, with the hum of the city on each side
>> yer? He spoke in tones of injury. Why, i don't of cold water,pints of hop
>> or brewers yeast, work with a lowering smile. Influence he says something
>> and languages have brought their contribution. Maureen clegg, it's you
>> againl' i'm very, very at last of getting you hanged for murder. She you,
>> but then i'm security. Go ahead, mary arm drawn through a forest of legs
>> he was hauled to tall and dark, and just about that build. It was me,',
>> said mr. Parker pyne, this is all very luminating..
>> -------------- next part --------------
>> An HTML attachment was scrubbed...
>>
>> ------------------------------
>>
>>
>> ------------------------------------------------------------------------------
>> Crystal Reports &#45; New Free Runtime and 30 Day Trial
>> Check out the new simplified licensign option that enables unlimited
>> royalty&#45;free distribution of the report engine for externally facing
>> server and web deployment.
>> http://p.sf.net/sfu/businessobjects
>>
>> ------------------------------
>>
>> _______________________________________________
>> mpls-linux-general mailing list
>> mpl...@li...
>> https://lists.sourceforge.net/lists/listinfo/mpls-linux-general
>>
>>
>> End of mpls-linux-general Digest, Vol 35, Issue 13
>> **************************************************
>>
>
>

[mpls-linux-general] Mailing lists and SPAM

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

I've made some changes to the mailman setup for the mpls-linux-general
mailing list to help minimize the amount of SPAM making it to the list.
I'll continue to monitor it and see if there are additional configuration
options I can tweak.

-- 
James R. Leu
jl...@mi...

[mpls-linux-general] GIT mirrors setup at repo.or.cz

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

I've setup mirrors for the core mpls-linux repos at repo.or.cz.
The information in the 'Development repo' section of
http://mpls-linux.sf.net/ has been updated.

-- 
James R. Leu
jl...@mi...