Thread: Re: [mpls-linux-general] packets not delivered to layer 3 (??)
Status: Beta
Brought to you by:
jleu
Menu
▾
▴
mpls-linux-general
|
From: Sameer G. <sam...@ya...> - 2002-09-12 13:09:26
|
Hello James and everybody, Thanks a ton James for the prompt response. I got 1.170 and patched it onto a 2.4.19 kernel and duplicated the tests. And guess what, it worked!! But I believe that the earlier fault was due to my fault. I wrongly entered the instruction on B as DLV instead of POP:DLV or POP:PEEK. So, i guess the packets were apparently being delivered to layer 3 without popping off the label. And hence the dropping of packets. But now a different problem has cropped up. LSP from A to B works fine. But when I try to setup an LSP from B to A, it gives an error. the command I give is... mplsadm2 -A -O 0 -o push:gen:100:set:eth0:ipv4:10.3.8.198 You can refer below in the mail to check out the topology and the addresses... the example is the same. So, when I give this command, I get... Key: 0x00000000 Out Segment add: Success Out Instr: Illegal seek And /proc/net/mpls_out contains the following line after tha above command is executed... 0x00000002 0/0/0 1 What could be the problem here? Thanking you in anticipation cheers, Sameer --- "James R. Leu" <jl...@mi...> wrote: > You can make sure the packets are being sent/recv'd > on the LSP by looking > at the counters in /proc/net/mpls_in and > /proc/net/mpls_out. After you > have verified that, then you can try turning on mpls > kernel debugging > by doing a 'mplsadm2 -d' this will toggle debuggin > to on. execute again to > turn it off. Look to you kernel console log for the > output or just do dmesg. > > Jim > > On Wed, Sep 11, 2002 at 06:59:26AM +0100, Sameer > Gharat wrote: > > Hello James and all, > > > > I have set up 1.152 on two Linux boxes running > kernel > > ver. 2.4.18-3. The two boxes are set up as... > > --------- --------- > > | A | | B | > > --------- --------- > > |eth0 |eth0 > > |10.3.8.198 |10.3.8.93 > > ----------------------------------- > > > > And the lsp was created b/w A and B using... > > On A : > > mplsadm2 -A -O -o > push:gen:200:set:eth0:ipv4:10.3.8.93 > > ip2 route add 10.3.8.93 dev eth0 lsp 0x00000002 > > mpls -L eth0:0 > > > > On B: > > mplsadm2 -A -I gen:200:0 > > mpls -L eth0:0 > > > > I believe these commands are enough to create an > LSP > > between A & B... or at least I hope so. > > > > Now, when I try to Ping B from A, the packets > reach B, > > but it seems the packets are not delivered > correctly > > up to layer 3 on B. The result is that the > > acknowledgement doesn't reach back to A and A > shows > > 100% packet loss. If I try to ping A from B, then > the > > ping packets reach A and come back to B (taking > the > > lsp from A to B). But again, the packets aren't > > recognized by B and again ping shows 100% packet > loss. > > Similar thing happens when I tried injecting > packets > > using nemesis tools. > > > > Is there any problem with the way I've set up the > LSP > > or is it some other problem? > > > > Any help would be greatly appreciated. > > > > Cheers, > > Sameer > > > > > > > -- > James R. Leu __________________________________________________ Do you Yahoo!? Yahoo! News - Today's headlines http://news.yahoo.com |
|
From: James R. L. <jl...@mi...> - 2002-09-12 18:59:57
|
I think I have a bug in mplsadm2. try doing the command as two steps: mplsadm2 -A -O 0 <returns key> mplsadm2 -O key -o push:gen:100:set:eth0:ipv4:10.3.8.198 Jim > mplsadm2 -A -O 0 -o > push:gen:100:set:eth0:ipv4:10.3.8.198 > You can refer below in the mail to check out the > topology and the addresses... the example is the same. > So, when I give this command, I get... > Key: 0x00000000 > Out Segment add: Success > Out Instr: Illegal seek > > And /proc/net/mpls_out contains the following line > after tha above command is executed... > 0x00000002 0/0/0 1 > > What could be the problem here? > > Thanking you in anticipation > > cheers, > Sameer > > > --- "James R. Leu" <jl...@mi...> wrote: > > You can make sure the packets are being sent/recv'd > > on the LSP by looking > > at the counters in /proc/net/mpls_in and > > /proc/net/mpls_out. After you > > have verified that, then you can try turning on mpls > > kernel debugging > > by doing a 'mplsadm2 -d' this will toggle debuggin > > to on. execute again to > > turn it off. Look to you kernel console log for the > > output or just do dmesg. > > > > Jim > > > > On Wed, Sep 11, 2002 at 06:59:26AM +0100, Sameer > > Gharat wrote: > > > Hello James and all, > > > > > > I have set up 1.152 on two Linux boxes running > > kernel > > > ver. 2.4.18-3. The two boxes are set up as... > > > --------- --------- > > > | A | | B | > > > --------- --------- > > > |eth0 |eth0 > > > |10.3.8.198 |10.3.8.93 > > > ----------------------------------- > > > > > > And the lsp was created b/w A and B using... > > > On A : > > > mplsadm2 -A -O -o > > push:gen:200:set:eth0:ipv4:10.3.8.93 > > > ip2 route add 10.3.8.93 dev eth0 lsp 0x00000002 > > > mpls -L eth0:0 > > > > > > On B: > > > mplsadm2 -A -I gen:200:0 > > > mpls -L eth0:0 > > > > > > I believe these commands are enough to create an > > LSP > > > between A & B... or at least I hope so. > > > > > > Now, when I try to Ping B from A, the packets > > reach B, > > > but it seems the packets are not delivered > > correctly > > > up to layer 3 on B. The result is that the > > > acknowledgement doesn't reach back to A and A > > shows > > > 100% packet loss. If I try to ping A from B, then > > the > > > ping packets reach A and come back to B (taking > > the > > > lsp from A to B). But again, the packets aren't > > > recognized by B and again ping shows 100% packet > > loss. > > > Similar thing happens when I tried injecting > > packets > > > using nemesis tools. > > > > > > Is there any problem with the way I've set up the > > LSP > > > or is it some other problem? > > > > > > Any help would be greatly appreciated. > > > > > > Cheers, > > > Sameer > > > > > > > > > > > -- > > James R. Leu > > > __________________________________________________ > Do you Yahoo!? > Yahoo! News - Today's headlines > http://news.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 |
|
From: <sam...@ya...> - 2002-09-13 04:19:39
|
Hi James,
I tried executing the command in two steps. But no
luck! This is what I get...
#mplsadm2 -A -O 0
Key: x00000000 (all zeroes!!)
Out Segment add: Success
But it adds an entry to /cat/proc/mpls_out i.e.
0x00000007 0/0/0 1
Then,
#mplsadm2 -O 0x00000007 -o
push:gen:100:set:eth0:ipv4:10.3.8.198
Out Instr: Success
But the entry in /cat/proc/mpls_out remains
0x00000007 0/0/0 1
So, the two step process didn't work. But, could you
explain, why is this happening only on machine B?! Set
up of LSP works fine on machine A. Moreover the
addition of incoming label on machine B works fine
too. Only the addition of outgoing label on machine B
causes problem!
Strange!
Again, thanking in anticipation! :-)
cheers,
Sameer
--- "James R. Leu" <jl...@mi...> wrote: > I
think I have a bug in mplsadm2.
>
> try doing the command as two steps:
>
> mplsadm2 -A -O 0
> <returns key>
> mplsadm2 -O key -o
> push:gen:100:set:eth0:ipv4:10.3.8.198
>
> Jim
>
> > mplsadm2 -A -O 0 -o
> > push:gen:100:set:eth0:ipv4:10.3.8.198
> > You can refer below in the mail to check out the
> > topology and the addresses... the example is the
> same.
> > So, when I give this command, I get...
> > Key: 0x00000000
> > Out Segment add: Success
> > Out Instr: Illegal seek
> >
> > And /proc/net/mpls_out contains the following line
> > after tha above command is executed...
> > 0x00000002 0/0/0 1
> >
> > What could be the problem here?
> >
> > Thanking you in anticipation
> >
> > cheers,
> > Sameer
> >
> >
> > > On Wed, Sep 11, 2002 at 06:59:26AM +0100, Sameer
> > > Gharat wrote:
> > > > Hello James and all,
> > > >
> > > > I have set up 1.152 on two Linux boxes running
> > > kernel
> > > > ver. 2.4.18-3. The two boxes are set up as...
> > > > --------- ---------
> > > > | A | | B |
> > > > --------- ---------
> > > > |eth0 |eth0
> > > > |10.3.8.198 |10.3.8.93
> > > > -----------------------------------
> > > >
> > > > And the lsp was created b/w A and B using...
> > > > On A :
> > > > mplsadm2 -A -O -o
> > > push:gen:200:set:eth0:ipv4:10.3.8.93
> > > > ip2 route add 10.3.8.93 dev eth0 lsp
> 0x00000002
> > > > mpls -L eth0:0
> > > >
> > > > On B:
> > > > mplsadm2 -A -I gen:200:0
> > > > mpls -L eth0:0
> > > >
________________________________________________________________________
Missed your favourite TV serial last night? Try the new, Yahoo! TV.
visit http://in.tv.yahoo.com
|
|
From: James R. L. <jl...@mi...> - 2002-09-13 21:54:04
|
Can you turn on kernel debugging ('mplsadm2 -d') and sent me the output
(you'll have to execute 'dmesg' to see the output)
What plateform are you running this on? i386?
Jim
On Fri, Sep 13, 2002 at 05:19:26AM +0100, Sameer Gharat wrote:
> Hi James,
> I tried executing the command in two steps. But no
> luck! This is what I get...
>
> #mplsadm2 -A -O 0
> Key: x00000000 (all zeroes!!)
> Out Segment add: Success
>
> But it adds an entry to /cat/proc/mpls_out i.e.
> 0x00000007 0/0/0 1
>
> Then,
> #mplsadm2 -O 0x00000007 -o
> push:gen:100:set:eth0:ipv4:10.3.8.198
> Out Instr: Success
>
> But the entry in /cat/proc/mpls_out remains
> 0x00000007 0/0/0 1
>
> So, the two step process didn't work. But, could you
> explain, why is this happening only on machine B?! Set
> up of LSP works fine on machine A. Moreover the
> addition of incoming label on machine B works fine
> too. Only the addition of outgoing label on machine B
> causes problem!
> Strange!
>
> Again, thanking in anticipation! :-)
> cheers,
> Sameer
>
>
> --- "James R. Leu" <jl...@mi...> wrote: > I
> think I have a bug in mplsadm2.
> >
> > try doing the command as two steps:
> >
> > mplsadm2 -A -O 0
> > <returns key>
> > mplsadm2 -O key -o
> > push:gen:100:set:eth0:ipv4:10.3.8.198
> >
> > Jim
> >
> > > mplsadm2 -A -O 0 -o
> > > push:gen:100:set:eth0:ipv4:10.3.8.198
> > > You can refer below in the mail to check out the
> > > topology and the addresses... the example is the
> > same.
> > > So, when I give this command, I get...
> > > Key: 0x00000000
> > > Out Segment add: Success
> > > Out Instr: Illegal seek
> > >
> > > And /proc/net/mpls_out contains the following line
> > > after tha above command is executed...
> > > 0x00000002 0/0/0 1
> > >
> > > What could be the problem here?
> > >
> > > Thanking you in anticipation
> > >
> > > cheers,
> > > Sameer
> > >
> > >
> > > > On Wed, Sep 11, 2002 at 06:59:26AM +0100, Sameer
> > > > Gharat wrote:
> > > > > Hello James and all,
> > > > >
> > > > > I have set up 1.152 on two Linux boxes running
> > > > kernel
> > > > > ver. 2.4.18-3. The two boxes are set up as...
> > > > > --------- ---------
> > > > > | A | | B |
> > > > > --------- ---------
> > > > > |eth0 |eth0
> > > > > |10.3.8.198 |10.3.8.93
> > > > > -----------------------------------
> > > > >
> > > > > And the lsp was created b/w A and B using...
> > > > > On A :
> > > > > mplsadm2 -A -O -o
> > > > push:gen:200:set:eth0:ipv4:10.3.8.93
> > > > > ip2 route add 10.3.8.93 dev eth0 lsp
> > 0x00000002
> > > > > mpls -L eth0:0
> > > > >
> > > > > On B:
> > > > > mplsadm2 -A -I gen:200:0
> > > > > mpls -L eth0:0
> > > > >
>
>
> ________________________________________________________________________
> Missed your favourite TV serial last night? Try the new, Yahoo! TV.
> visit http://in.tv.yahoo.com
--
James R. Leu
|
×
Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.
Thanks for helping keep SourceForge clean.
X