From bms at incunabulum.net  Tue Nov  4 05:18:54 2008
From: bms at incunabulum.net (Bruce M Simpson)
Date: Tue, 04 Nov 2008 13:18:54 +0000
Subject: [Xorp-hackers] FYI: C++0x language standard is now ratified
Message-ID: <49104BBE.8090101@incunabulum.net>

Hi,

This is just to propagate the announcement that the next version of the 
C++ language standard, C++0x, has now been ratified.

Links:

 General announcements:
   
http://herbsutter.wordpress.com/2008/10/28/september-2008-iso-c-standards-meeting-the-draft-has-landed-and-a-new-convener/
  http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2784.html

 The working draft itself:
   http://www.open-std.org/jtc1/sc22/wg21/docs/papers/2008/n2798.pdf

 GNU C++0x status here:
   http://gcc.gnu.org/projects/cxx0x.html

 The Wikipedia article is a useful summary which fluctuates:
  http://en.wikipedia.org/wiki/C%2B%2B0x

What this means for XORP:

 There are a number of places in the XORP code base which could benefit 
from using some of the idioms introduced within the new C++0x 
specification. Some of these are derived from the Boost++ project.

 * std::shared_ptr is a possible fit for the OLSR and OSPF message 
handling code.
   Note that it's really easy to introduce memory leaks using ref_ptr; 
every time one is passed to a new scope, the refcount is bumped, even if 
it's "Just passing through".
   Boost++'s weak_ptr exists to allow refcounted pointers to be passed 
between subsystems WITHOUT losing their refcounted nature, and WITHOUT 
bumping the refcount until the ref is actually ACQUIRED.

 * Concept checks are being formalized as part of the language, these 
are very useful for metaprogramming, i.e. building your own extensions 
to the STL containers.

 * Variadic macros are now part of the standard. XORP uses these in a 
number of places.
Microsoft's native toolchains for example, did not support them until 
Visual Studio 2005 was released, and even then as a non-standard 
extension to the C99 preprocessor.

 * Tuple is syntactic sugar, but welcome nonetheless, we use struct 
types in a number of places and tuples would no doubt make things more 
readable.

thanks
BMS



From alancyang at gmail.com  Wed Nov  5 15:38:23 2008
From: alancyang at gmail.com (alan yang)
Date: Wed, 5 Nov 2008 15:38:23 -0800
Subject: [Xorp-hackers] click configuration under FreeBSD
Message-ID: <290865fd0811051538p52963c79pfe92ee03e6759c12@mail.gmail.com>

hello,

under freebsd7, i am trying to config xorp click from within
config.boot file and have couple questions:
1.  it says for freebsd it only need the click.ko for kernel click
module, but in click readme it says "FreeBSD 4.5 kernel module driver
not working" that actually the bsdmodule cannot build.
2.  it seems xorp need click for FE plane, but without click.ko and
other driver, does xorp can really work under freebsd

thanks in advance for shed some light.

alan


From pavlin at ICSI.Berkeley.EDU  Wed Nov  5 15:53:58 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Wed, 05 Nov 2008 15:53:58 -0800
Subject: [Xorp-hackers] [Xorp-users] click configuration under FreeBSD
In-Reply-To: <290865fd0811051538p52963c79pfe92ee03e6759c12@mail.gmail.com> 
References: <290865fd0811051538p52963c79pfe92ee03e6759c12@mail.gmail.com>
Message-ID: <200811052353.mA5Nrw6Q029396@fruitcake.ICSI.Berkeley.EDU>

alan yang <alancyang at gmail.com> wrote:

> hello,
> 
> under freebsd7, i am trying to config xorp click from within
> config.boot file and have couple questions:
> 1.  it says for freebsd it only need the click.ko for kernel click
> module, but in click readme it says "FreeBSD 4.5 kernel module driver
> not working" that actually the bsdmodule cannot build.
> 2.  it seems xorp need click for FE plane, but without click.ko and
> other driver, does xorp can really work under freebsd

Click can be run in either user-mode or kernel-mode.

If Click can work on FreeBSD in kernel-mode (which was the case when
the XORP-Click support was added couple of years ago), then XORP
will be able to use Click. You might want to check with the Click
folks whether there is any recent activity of getting Click working
on FreeBSD in kernel mode.

I guess Click will work in user-mode on FreeBSD so you can try this
solution.

Pavlin



> thanks in advance for shed some light.
> 
> alan
> 
> _______________________________________________
> Xorp-users mailing list
> Xorp-users at xorp.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users


From bms at incunabulum.net  Thu Nov  6 03:05:18 2008
From: bms at incunabulum.net (Bruce M Simpson)
Date: Thu, 06 Nov 2008 11:05:18 +0000
Subject: [Xorp-hackers] [Xorp-users] click configuration under FreeBSD
In-Reply-To: <290865fd0811051538p52963c79pfe92ee03e6759c12@mail.gmail.com>
References: <290865fd0811051538p52963c79pfe92ee03e6759c12@mail.gmail.com>
Message-ID: <4912CF6E.1030303@incunabulum.net>

alan yang wrote:
> hello,
>
> under freebsd7, i am trying to config xorp click from within
> config.boot file and have couple questions:
> 1.  it says for freebsd it only need the click.ko for kernel click
> module, but in click readme it says "FreeBSD 4.5 kernel module driver
> not working" that actually the bsdmodule cannot build.
> 2.  it seems xorp need click for FE plane, but without click.ko and
> other driver, does xorp can really work under freebsd
>   

XORP does not require Click for the forwarding plane, its use is purely 
optional and is not required, you can also run Click in user space.

I believe the kernel-space Click port to FreeBSD 6.x+ up wasn't finished.

There were a number of technical issues which needed to be solved and 
whilst I myself got involved (by sending a patch 18 months ago), I don't 
use Click for anything myself, and there hasn't been any line of funding 
or other incentive for me to continue to work on it.

thanks
BMS


From alancyang at gmail.com  Thu Nov  6 10:49:10 2008
From: alancyang at gmail.com (alan yang)
Date: Thu, 6 Nov 2008 10:49:10 -0800
Subject: [Xorp-hackers] [Xorp-users] click configuration under FreeBSD
In-Reply-To: <4912CF6E.1030303@incunabulum.net>
References: <290865fd0811051538p52963c79pfe92ee03e6759c12@mail.gmail.com>
	<4912CF6E.1030303@incunabulum.net>
Message-ID: <290865fd0811061049q3178014di1478df469611c5ed@mail.gmail.com>

Good to know that Click is only optional and not required for XORP.
Without click, how FEA interact with underneath forwarding plane any
doc or pointer you could refer.

Many thanks!

On Thu, Nov 6, 2008 at 3:05 AM, Bruce M Simpson <bms at incunabulum.net> wrote:
> alan yang wrote:
>>
>> hello,
>>
>> under freebsd7, i am trying to config xorp click from within
>> config.boot file and have couple questions:
>> 1.  it says for freebsd it only need the click.ko for kernel click
>> module, but in click readme it says "FreeBSD 4.5 kernel module driver
>> not working" that actually the bsdmodule cannot build.
>> 2.  it seems xorp need click for FE plane, but without click.ko and
>> other driver, does xorp can really work under freebsd
>>
>
> XORP does not require Click for the forwarding plane, its use is purely
> optional and is not required, you can also run Click in user space.
>
> I believe the kernel-space Click port to FreeBSD 6.x+ up wasn't finished.
>
> There were a number of technical issues which needed to be solved and whilst
> I myself got involved (by sending a patch 18 months ago), I don't use Click
> for anything myself, and there hasn't been any line of funding or other
> incentive for me to continue to work on it.
>
> thanks
> BMS
>


From bms at incunabulum.net  Thu Nov  6 14:59:42 2008
From: bms at incunabulum.net (Bruce M Simpson)
Date: Thu, 06 Nov 2008 22:59:42 +0000
Subject: [Xorp-hackers] [Xorp-users] click configuration under FreeBSD
In-Reply-To: <290865fd0811061049q3178014di1478df469611c5ed@mail.gmail.com>
References: <290865fd0811051538p52963c79pfe92ee03e6759c12@mail.gmail.com>	
	<4912CF6E.1030303@incunabulum.net>
	<290865fd0811061049q3178014di1478df469611c5ed@mail.gmail.com>
Message-ID: <491376DE.4070307@incunabulum.net>

alan yang wrote:
> Good to know that Click is only optional and not required for XORP.
> Without click, how FEA interact with underneath forwarding plane any
> doc or pointer you could refer.
>   

The FEA uses various 'control plane' and 'data plane' plugins to talk to 
the underlying OS. Please see: 
http://www.xorp.org/releases/1.5/docs/fea/fea.pdf

thanks
BMS


From alancyang at gmail.com  Tue Nov 11 10:59:43 2008
From: alancyang at gmail.com (alan yang)
Date: Tue, 11 Nov 2008 10:59:43 -0800
Subject: [Xorp-hackers] [Click] Fwd: [Xorp-users] click configuration
	under FreeBSD
In-Reply-To: <4917DAC2.8030100@cs.ucla.edu>
References: <290865fd0811051538p52963c79pfe92ee03e6759c12@mail.gmail.com>
	<200811052353.mA5Nrw6Q029396@fruitcake.ICSI.Berkeley.EDU>
	<290865fd0811051937sa12996csba1417324de619e7@mail.gmail.com>
	<4917DAC2.8030100@cs.ucla.edu>
Message-ID: <290865fd0811111059l57a25391qf00d139c65c3b31c@mail.gmail.com>

Thanks Eddie, for the info.

Another Q on Xory: while Xorp running under FreeBSD, is it a complete
replacement of the original FreeBSD routing code for static, multicast
routing for instance...?  If the case, how the packet flow looks like,
where could I start tracing... could you point some pointers...

Many thanks!

On Sun, Nov 9, 2008 at 10:54 PM, Eddie Kohler <kohler at cs.ucla.edu> wrote:
> Alan,
>
> The easiest way to get xorp running on FreeBSD is to use Xorp's support for
> the default FreeBSD kernel forwarding engine.  Don't involve Click unless
> you need to (because you are writing special code).
>
> Eddie
>
>
> alan yang wrote:
>>
>> hello,
>>
>> wonder people can help shed some light on click support under freebsd.
>> thanks in advance.
>>
>>
>> ---------- Forwarded message ----------
>> From: Pavlin Radoslavov <pavlin at icsi.berkeley.edu>
>> Date: Wed, Nov 5, 2008 at 3:53 PM
>> Subject: Re: [Xorp-users] click configuration under FreeBSD
>> To: alan yang <alancyang at gmail.com>
>> Cc: xorp-users at xorp.org, xorp-hackers at xorp.org
>>
>>
>> alan yang <alancyang at gmail.com> wrote:
>>
>>> hello,
>>>
>>> under freebsd7, i am trying to config xorp click from within
>>> config.boot file and have couple questions:
>>> 1.  it says for freebsd it only need the click.ko for kernel click
>>> module, but in click readme it says "FreeBSD 4.5 kernel module driver
>>> not working" that actually the bsdmodule cannot build.
>>> 2.  it seems xorp need click for FE plane, but without click.ko and
>>> other driver, does xorp can really work under freebsd
>>
>> Click can be run in either user-mode or kernel-mode.
>>
>> If Click can work on FreeBSD in kernel-mode (which was the case when
>> the XORP-Click support was added couple of years ago), then XORP
>> will be able to use Click. You might want to check with the Click
>> folks whether there is any recent activity of getting Click working
>> on FreeBSD in kernel mode.
>>
>> I guess Click will work in user-mode on FreeBSD so you can try this
>> solution.
>>
>> Pavlin
>>
>>
>>
>>> thanks in advance for shed some light.
>>>
>>> alan
>>>
>>> _______________________________________________
>>> Xorp-users mailing list
>>> Xorp-users at xorp.org
>>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-users
>>
>> _______________________________________________
>> click mailing list
>> click at amsterdam.lcs.mit.edu
>> https://amsterdam.lcs.mit.edu/mailman/listinfo/click
>


From eshe168 at gmail.com  Tue Nov 11 22:03:54 2008
From: eshe168 at gmail.com (=?GB2312?B?0e7Qocun?=)
Date: Wed, 12 Nov 2008 14:03:54 +0800
Subject: [Xorp-hackers] About op command!
Message-ID: <56f9e0990811112203q33a32fcqa4be2d68c02381ee@mail.gmail.com>

Hi,

     When I studied the popen.cc, there is a question to me. Why using
_exit(127) in the line 390, and what's mean the 127. I always see
_exit(0) after exec function.

B.R.
Xiaoshuai Yang


From pavlin at ICSI.Berkeley.EDU  Tue Nov 11 22:26:10 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Tue, 11 Nov 2008 22:26:10 -0800
Subject: [Xorp-hackers] About op command!
In-Reply-To: <56f9e0990811112203q33a32fcqa4be2d68c02381ee@mail.gmail.com> 
References: <56f9e0990811112203q33a32fcqa4be2d68c02381ee@mail.gmail.com>
Message-ID: <200811120626.mAC6QA21001137@fruitcake.ICSI.Berkeley.EDU>

??? <eshe168 at gmail.com> wrote:

> Hi,
> 
>      When I studied the popen.cc, there is a question to me. Why using
> _exit(127) in the line 390, and what's mean the 127. I always see
> _exit(0) after exec function.

The libxorp/popen.cc code is derived from the FreeBSD popen(3)
implementation. The _exit(127) statement actually comes from the
original FreeBSD code. The following text from the popen(3) manual
page suggests the purpose of 127:

=====
Failure to execute the shell is indistinguishable from the shell's fail-
ure to execute command, or an immediate exit of the command.  The only
hint is an exit status of 127.
=====

Hope that helps,
Pavlin


From eshe168 at gmail.com  Wed Nov 12 00:04:30 2008
From: eshe168 at gmail.com (=?GB2312?B?0e7Qocun?=)
Date: Wed, 12 Nov 2008 16:04:30 +0800
Subject: [Xorp-hackers] About op command!
In-Reply-To: <200811120626.mAC6QA21001137@fruitcake.ICSI.Berkeley.EDU>
References: <56f9e0990811112203q33a32fcqa4be2d68c02381ee@mail.gmail.com>
	<200811120626.mAC6QA21001137@fruitcake.ICSI.Berkeley.EDU>
Message-ID: <56f9e0990811120004s143a412dxfa4182e506f80ada@mail.gmail.com>

Hello,

If the libxorp/popen.cc code is derived from the FreeBSD popen(3)
implementation, I think that the "setpgid(0, 0)" in the line 382 of
popen.cc should not be existed.

Thanks,
Xiaoshuai Yang


2008/11/12 Pavlin Radoslavov <pavlin at icsi.berkeley.edu>:
> ??? <eshe168 at gmail.com> wrote:
>
>> Hi,
>>
>>      When I studied the popen.cc, there is a question to me. Why using
>> _exit(127) in the line 390, and what's mean the 127. I always see
>> _exit(0) after exec function.
>
> The libxorp/popen.cc code is derived from the FreeBSD popen(3)
> implementation. The _exit(127) statement actually comes from the
> original FreeBSD code. The following text from the popen(3) manual
> page suggests the purpose of 127:
>
> =====
> Failure to execute the shell is indistinguishable from the shell's fail-
> ure to execute command, or an immediate exit of the command.  The only
> hint is an exit status of 127.
> =====
>
> Hope that helps,
> Pavlin
>


From bms at incunabulum.net  Wed Nov 12 04:54:26 2008
From: bms at incunabulum.net (Bruce M Simpson)
Date: Wed, 12 Nov 2008 12:54:26 +0000
Subject: [Xorp-hackers] [Click] Fwd: [Xorp-users] click configuration
 under FreeBSD
In-Reply-To: <290865fd0811111059l57a25391qf00d139c65c3b31c@mail.gmail.com>
References: <290865fd0811051538p52963c79pfe92ee03e6759c12@mail.gmail.com>	<200811052353.mA5Nrw6Q029396@fruitcake.ICSI.Berkeley.EDU>	<290865fd0811051937sa12996csba1417324de619e7@mail.gmail.com>	<4917DAC2.8030100@cs.ucla.edu>
	<290865fd0811111059l57a25391qf00d139c65c3b31c@mail.gmail.com>
Message-ID: <491AD202.4070509@incunabulum.net>

alan yang wrote:
> Thanks Eddie, for the info.
>
> Another Q on Xory: while Xorp running under FreeBSD, is it a complete
> replacement of the original FreeBSD routing code for static, multicast
> routing for instance...?  If the case, how the packet flow looks like,
> where could I start tracing... could you point some pointers...
>   

No, XORP hosted on FreeBSD uses FreeBSD's kernel forwarding plane.

thanks
BMS


From pavlin at ICSI.Berkeley.EDU  Wed Nov 12 09:52:19 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Wed, 12 Nov 2008 09:52:19 -0800
Subject: [Xorp-hackers] About op command!
In-Reply-To: <56f9e0990811120004s143a412dxfa4182e506f80ada@mail.gmail.com> 
References: <56f9e0990811112203q33a32fcqa4be2d68c02381ee@mail.gmail.com>
	<200811120626.mAC6QA21001137@fruitcake.ICSI.Berkeley.EDU>
	<56f9e0990811120004s143a412dxfa4182e506f80ada@mail.gmail.com>
Message-ID: <200811121753.mACHqJRb025900@fruitcake.ICSI.Berkeley.EDU>

??? <eshe168 at gmail.com> wrote:

> If the libxorp/popen.cc code is derived from the FreeBSD popen(3)
> implementation, I think that the "setpgid(0, 0)" in the line 382 of
> popen.cc should not be existed.

Why?

Pavlin


From eshe168 at gmail.com  Wed Nov 12 21:46:50 2008
From: eshe168 at gmail.com (=?GB2312?B?0e7Qocun?=)
Date: Thu, 13 Nov 2008 13:46:50 +0800
Subject: [Xorp-hackers] About op command!
In-Reply-To: <200811121753.mACHqJRb025900@fruitcake.ICSI.Berkeley.EDU>
References: <56f9e0990811112203q33a32fcqa4be2d68c02381ee@mail.gmail.com>
	<200811120626.mAC6QA21001137@fruitcake.ICSI.Berkeley.EDU>
	<56f9e0990811120004s143a412dxfa4182e506f80ada@mail.gmail.com>
	<200811121753.mACHqJRb025900@fruitcake.ICSI.Berkeley.EDU>
Message-ID: <56f9e0990811122146k151ffd51t8b9de03d9509c027@mail.gmail.com>

I have a more question.
Can the XORP record idle time for a xorpsh user? If there is a long
time for a user did not input any instruction, the xorp_rtrmgr will
kick the user off.

B.R.
Xiaoshuai Yang


From pavlin at ICSI.Berkeley.EDU  Wed Nov 12 22:39:38 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Wed, 12 Nov 2008 22:39:38 -0800
Subject: [Xorp-hackers] About op command!
In-Reply-To: <56f9e0990811122146k151ffd51t8b9de03d9509c027@mail.gmail.com> 
References: <56f9e0990811112203q33a32fcqa4be2d68c02381ee@mail.gmail.com>
	<200811120626.mAC6QA21001137@fruitcake.ICSI.Berkeley.EDU>
	<56f9e0990811120004s143a412dxfa4182e506f80ada@mail.gmail.com>
	<200811121753.mACHqJRb025900@fruitcake.ICSI.Berkeley.EDU>
	<56f9e0990811122146k151ffd51t8b9de03d9509c027@mail.gmail.com>
Message-ID: <200811130639.mAD6dcXG021724@fruitcake.ICSI.Berkeley.EDU>

??? <eshe168 at gmail.com> wrote:

> I have a more question.
> Can the XORP record idle time for a xorpsh user? If there is a long
> time for a user did not input any instruction, the xorp_rtrmgr will
> kick the user off.

No, the CLI doesn't record the idle time for an user.

I think this is a good suggestion, so please submit a Bugzilla entry
about this feature.

Pavlin

> B.R.
> Xiaoshuai Yang
> 
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers


From bms at incunabulum.net  Thu Nov 13 03:52:02 2008
From: bms at incunabulum.net (Bruce M Simpson)
Date: Thu, 13 Nov 2008 11:52:02 +0000
Subject: [Xorp-hackers] About op command!
In-Reply-To: <56f9e0990811120004s143a412dxfa4182e506f80ada@mail.gmail.com>
References: <56f9e0990811112203q33a32fcqa4be2d68c02381ee@mail.gmail.com>	<200811120626.mAC6QA21001137@fruitcake.ICSI.Berkeley.EDU>
	<56f9e0990811120004s143a412dxfa4182e506f80ada@mail.gmail.com>
Message-ID: <491C14E2.7040604@incunabulum.net>

[Resending from correct alias to make sure this is archived]

?????? wrote:
> Hello,
>
> If the libxorp/popen.cc code is derived from the FreeBSD popen(3)
> implementation, I think that the "setpgid(0, 0)" in the line 382 of
> popen.cc should not be existed.
>   

popen2() is normally used to run operational mode commands.

The use of setpgid(0,0) is to ensure child processes run with popen2()
are run in their own new process group, and that they are detached from
the controlling terminal.

The POSIX setsid() call might be more appropriate, however setpgid() is
slightly more widely available.

thanks
BMS


From bms at incunabulum.net  Thu Nov 13 10:48:39 2008
From: bms at incunabulum.net (Bruce M Simpson)
Date: Thu, 13 Nov 2008 18:48:39 +0000
Subject: [Xorp-hackers] About op command!
In-Reply-To: <491C14E2.7040604@incunabulum.net>
References: <56f9e0990811112203q33a32fcqa4be2d68c02381ee@mail.gmail.com>	<200811120626.mAC6QA21001137@fruitcake.ICSI.Berkeley.EDU>	<56f9e0990811120004s143a412dxfa4182e506f80ada@mail.gmail.com>
	<491C14E2.7040604@incunabulum.net>
Message-ID: <491C7687.3080007@incunabulum.net>

Bruce M Simpson wrote:
>> If the libxorp/popen.cc code is derived from the FreeBSD popen(3)
>> implementation, I think that the "setpgid(0, 0)" in the line 382 of
>> popen.cc should not be existed.
>>  

Sorry, I just re-read your question.

Whilst it was inspired by FreeBSD's popen(), popen2() is *not* intended 
as a drop-in replacement for popen().

RunCommand requires specific semantics to run the child process in a 
controlled way which can be integrated with the XORP EventLoop. This is 
particularly important for the Windows port as the underlying APIs there 
are totally different.

thanks
BMS


From eshe168 at gmail.com  Thu Nov 13 17:01:49 2008
From: eshe168 at gmail.com (=?GB2312?B?0e7Qocun?=)
Date: Fri, 14 Nov 2008 09:01:49 +0800
Subject: [Xorp-hackers] About op command!
In-Reply-To: <491C7687.3080007@incunabulum.net>
References: <56f9e0990811112203q33a32fcqa4be2d68c02381ee@mail.gmail.com>
	<200811120626.mAC6QA21001137@fruitcake.ICSI.Berkeley.EDU>
	<56f9e0990811120004s143a412dxfa4182e506f80ada@mail.gmail.com>
	<491C14E2.7040604@incunabulum.net> <491C7687.3080007@incunabulum.net>
Message-ID: <56f9e0990811131701s371837daj88eec3fb9e55afa8@mail.gmail.com>

Thanks for your work.
I got it. When I try to add the telnet into op commands list, I found
something wrong. If I delelte the setpgid(0, 0), the telnet can work
normally. But when I exit the telnet, the xorpsh exit too. I cannot
find out.


2008/11/14 Bruce M Simpson <bms at incunabulum.net>:
> Bruce M Simpson wrote:
>>>
>>> If the libxorp/popen.cc code is derived from the FreeBSD popen(3)
>>> implementation, I think that the "setpgid(0, 0)" in the line 382 of
>>> popen.cc should not be existed.
>>>
>
> Sorry, I just re-read your question.
>
> Whilst it was inspired by FreeBSD's popen(), popen2() is *not* intended as a
> drop-in replacement for popen().
>
> RunCommand requires specific semantics to run the child process in a
> controlled way which can be integrated with the XORP EventLoop. This is
> particularly important for the Windows port as the underlying APIs there are
> totally different.
>
> thanks
> BMS
>



-- 
Best Regard
Xiaoshuai Yang


From bms at incunabulum.net  Thu Nov 13 17:31:03 2008
From: bms at incunabulum.net (Bruce Simpson)
Date: Fri, 14 Nov 2008 01:31:03 +0000
Subject: [Xorp-hackers] About op command!
In-Reply-To: <56f9e0990811131701s371837daj88eec3fb9e55afa8@mail.gmail.com>
References: <56f9e0990811112203q33a32fcqa4be2d68c02381ee@mail.gmail.com>	
	<200811120626.mAC6QA21001137@fruitcake.ICSI.Berkeley.EDU>	
	<56f9e0990811120004s143a412dxfa4182e506f80ada@mail.gmail.com>	
	<491C14E2.7040604@incunabulum.net>
	<491C7687.3080007@incunabulum.net>
	<56f9e0990811131701s371837daj88eec3fb9e55afa8@mail.gmail.com>
Message-ID: <491CD4D7.7080103@incunabulum.net>

You're initiating telnet by forking it from the xorpsh?

That may not work, as telnet needs to use the controlling terminal.

Please raise this as an enhancement request at http://bugzilla.xorp.org/.

thanks!
BMS


??? wrote:
> Thanks for your work.
> I got it. When I try to add the telnet into op commands list, I found
> something wrong. If I delelte the setpgid(0, 0), the telnet can work
> normally. But when I exit the telnet, the xorpsh exit too. I cannot
> find out.
>   


From eshe168 at gmail.com  Thu Nov 13 17:51:50 2008
From: eshe168 at gmail.com (=?GB2312?B?0e7Qocun?=)
Date: Fri, 14 Nov 2008 09:51:50 +0800
Subject: [Xorp-hackers] About op command!
In-Reply-To: <491CD4D7.7080103@incunabulum.net>
References: <56f9e0990811112203q33a32fcqa4be2d68c02381ee@mail.gmail.com>
	<200811120626.mAC6QA21001137@fruitcake.ICSI.Berkeley.EDU>
	<56f9e0990811120004s143a412dxfa4182e506f80ada@mail.gmail.com>
	<491C14E2.7040604@incunabulum.net> <491C7687.3080007@incunabulum.net>
	<56f9e0990811131701s371837daj88eec3fb9e55afa8@mail.gmail.com>
	<491CD4D7.7080103@incunabulum.net>
Message-ID: <56f9e0990811131751k1a6f7e1cq6eb244e27a1c632f@mail.gmail.com>

Yes.
I have raised it. Bug No. is 825.

2008/11/14 Bruce Simpson <bms at incunabulum.net>:
> You're initiating telnet by forking it from the xorpsh?
>
> That may not work, as telnet needs to use the controlling terminal.
>
> Please raise this as an enhancement request at http://bugzilla.xorp.org/.
>
> thanks!
> BMS
>
>
> ??? wrote:
>>
>> Thanks for your work.
>> I got it. When I try to add the telnet into op commands list, I found
>> something wrong. If I delelte the setpgid(0, 0), the telnet can work
>> normally. But when I exit the telnet, the xorpsh exit too. I cannot
>> find out.
>>
>
>



-- 
Best Regard
Xiaoshuai Yang


From eshe168 at gmail.com  Tue Nov 25 22:14:09 2008
From: eshe168 at gmail.com (=?GB2312?B?0e7Qocun?=)
Date: Wed, 26 Nov 2008 14:14:09 +0800
Subject: [Xorp-hackers] About "u32range" Bug
Message-ID: <56f9e0990811252214w17f32661p9a68bbf9d3bcfaaf@mail.gmail.com>

Hi,

When I use a node whose type is "u32range", then I make the .xif file.
There is error information:

In Xrl starting at line 13 in cpl_ifmgr.xif:
        Atom type "u32range" not amongst those known ['binary',
'ipv4net', 'i32', 'list', 'i64', 'mac', 'ipv6net', 'bool', 'u32',
'ipv6', 'u64', 'txt', 'ipv4']


I have review the source code, maybe xrl_atom.hh xrl_atom.cc has bugs
in the libxipc. I want to fix it, but i need your help about add a new
type.

-- 
Best Regard
Xiaoshuai Yang


From pavlin at ICSI.Berkeley.EDU  Tue Nov 25 23:15:28 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Tue, 25 Nov 2008 23:15:28 -0800
Subject: [Xorp-hackers] About "u32range" Bug
In-Reply-To: <56f9e0990811252214w17f32661p9a68bbf9d3bcfaaf@mail.gmail.com> 
References: <56f9e0990811252214w17f32661p9a68bbf9d3bcfaaf@mail.gmail.com>
Message-ID: <200811260715.mAQ7FSAa006167@fruitcake.ICSI.Berkeley.EDU>

The XRLs don't have atom of type u32range.
The u32range type that you have probably seen in the
etc/templates/*.tp template files is actually transmit as a string
inside the XRLs.
Please use the libxorp/range.hh implementation for manipulating the
u32range encoding/decoding the string, etc.

Pavlin

??? <eshe168 at gmail.com> wrote:

> Hi,
> 
> When I use a node whose type is "u32range", then I make the .xif file.
> There is error information:
> 
> In Xrl starting at line 13 in cpl_ifmgr.xif:
>         Atom type "u32range" not amongst those known ['binary',
> 'ipv4net', 'i32', 'list', 'i64', 'mac', 'ipv6net', 'bool', 'u32',
> 'ipv6', 'u64', 'txt', 'ipv4']
> 
> 
> I have review the source code, maybe xrl_atom.hh xrl_atom.cc has bugs
> in the libxipc. I want to fix it, but i need your help about add a new
> type.
> 
> -- 
> Best Regard
> Xiaoshuai Yang
> 
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers


From eshe168 at gmail.com  Wed Nov 26 00:13:38 2008
From: eshe168 at gmail.com (=?GB2312?B?0e7Qocun?=)
Date: Wed, 26 Nov 2008 16:13:38 +0800
Subject: [Xorp-hackers] About "u32range" Bug
In-Reply-To: <200811260715.mAQ7FSAa006167@fruitcake.ICSI.Berkeley.EDU>
References: <56f9e0990811252214w17f32661p9a68bbf9d3bcfaaf@mail.gmail.com>
	<200811260715.mAQ7FSAa006167@fruitcake.ICSI.Berkeley.EDU>
Message-ID: <56f9e0990811260013v29f8c874nbca7648c29d394f4@mail.gmail.com>

That means that I should use "string" instead of "u32range" in .xrl files.

2008/11/26 Pavlin Radoslavov <pavlin at icsi.berkeley.edu>:
> The XRLs don't have atom of type u32range.
> The u32range type that you have probably seen in the
> etc/templates/*.tp template files is actually transmit as a string
> inside the XRLs.
> Please use the libxorp/range.hh implementation for manipulating the
> u32range encoding/decoding the string, etc.
>
> Pavlin
>
> ??? <eshe168 at gmail.com> wrote:
>
>> Hi,
>>
>> When I use a node whose type is "u32range", then I make the .xif file.
>> There is error information:
>>
>> In Xrl starting at line 13 in cpl_ifmgr.xif:
>>         Atom type "u32range" not amongst those known ['binary',
>> 'ipv4net', 'i32', 'list', 'i64', 'mac', 'ipv6net', 'bool', 'u32',
>> 'ipv6', 'u64', 'txt', 'ipv4']
>>
>>
>> I have review the source code, maybe xrl_atom.hh xrl_atom.cc has bugs
>> in the libxipc. I want to fix it, but i need your help about add a new
>> type.
>>
>> --
>> Best Regard
>> Xiaoshuai Yang
>>
>> _______________________________________________
>> Xorp-hackers mailing list
>> Xorp-hackers at icir.org
>> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
>



-- 
Best Regard
Xiaoshuai Yang


From pavlin at ICSI.Berkeley.EDU  Wed Nov 26 09:14:22 2008
From: pavlin at ICSI.Berkeley.EDU (Pavlin Radoslavov)
Date: Wed, 26 Nov 2008 09:14:22 -0800
Subject: [Xorp-hackers] About "u32range" Bug
In-Reply-To: <56f9e0990811260013v29f8c874nbca7648c29d394f4@mail.gmail.com> 
References: <56f9e0990811252214w17f32661p9a68bbf9d3bcfaaf@mail.gmail.com>
	<200811260715.mAQ7FSAa006167@fruitcake.ICSI.Berkeley.EDU>
	<56f9e0990811260013v29f8c874nbca7648c29d394f4@mail.gmail.com>
Message-ID: <200811261715.mAQHEMjQ011407@fruitcake.ICSI.Berkeley.EDU>

> That means that I should use "string" instead of "u32range" in .xrl files.

You should use the keyword "txt" instead of "u32range" in the .xrl
files.
Then on the sender/receiver side you should encode/decode the
u32range to/from a string.

Pavlin

> 2008/11/26 Pavlin Radoslavov <pavlin at icsi.berkeley.edu>:
> > The XRLs don't have atom of type u32range.
> > The u32range type that you have probably seen in the
> > etc/templates/*.tp template files is actually transmit as a string
> > inside the XRLs.
> > Please use the libxorp/range.hh implementation for manipulating the
> > u32range encoding/decoding the string, etc.
> >
> > Pavlin
> >
> > ??? <eshe168 at gmail.com> wrote:
> >
> >> Hi,
> >>
> >> When I use a node whose type is "u32range", then I make the .xif file.
> >> There is error information:
> >>
> >> In Xrl starting at line 13 in cpl_ifmgr.xif:
> >>         Atom type "u32range" not amongst those known ['binary',
> >> 'ipv4net', 'i32', 'list', 'i64', 'mac', 'ipv6net', 'bool', 'u32',
> >> 'ipv6', 'u64', 'txt', 'ipv4']
> >>
> >>
> >> I have review the source code, maybe xrl_atom.hh xrl_atom.cc has bugs
> >> in the libxipc. I want to fix it, but i need your help about add a new
> >> type.
> >>
> >> --
> >> Best Regard
> >> Xiaoshuai Yang
> >>
> >> _______________________________________________
> >> Xorp-hackers mailing list
> >> Xorp-hackers at icir.org
> >> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
> >
> 
> 
> 
> -- 
> Best Regard
> Xiaoshuai Yang
> 
> _______________________________________________
> Xorp-hackers mailing list
> Xorp-hackers at icir.org
> http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers


From xorp2008 at yahoo.com.cn  Wed Nov 26 17:14:39 2008
From: xorp2008 at yahoo.com.cn (=?gb2312?B?1ty93A==?=)
Date: Thu, 27 Nov 2008 09:14:39 +0800 (CST)
Subject: [Xorp-hackers] how to interact with rtrmgr
Message-ID: <235004.77831.qm@web15108.mail.cnb.yahoo.com>




Hi ,XORP,
?
?I am?working to add web interface for Xorp. 
I?want to?know how to interact with the 
rtrmgr.could I use the rgrmgr's xrl interface for 
xorpsh,while ,how?
could someone help me?
thank you very much!!


      ___________________________________________________________ 
  ????????????????? 
http://card.mail.cn.yahoo.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20081127/3eb8525e/attachment.html 

From vfaion at gmail.com  Fri Nov 28 07:32:09 2008
From: vfaion at gmail.com (Victor Faion)
Date: Fri, 28 Nov 2008 15:32:09 +0000
Subject: [Xorp-hackers] XORP and/or Click with an overlay protocol
Message-ID: <38f1dbe80811280732k221b904cx4db443ef6c0932e2@mail.gmail.com>

Hello,

I wanted to use my forwarding engine (which has its own forwarding table)
together with my own protocol (at the application layer, using sockets) with
XORP. I wasn't sure if it's better to implement a separate process that
interacts with XORP's FEA (this would be the forwarding engine) and another
process that represents the protocol or if I should implement all of this
using Click and then plug it into XORP (or just use it only with Click). In
other words, how much of XORP's code I would need to change to do this and
would it be easier to do it in Click or to use both?

Victor
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://mailman.ICSI.Berkeley.EDU/pipermail/xorp-hackers/attachments/20081128/09fa3192/attachment.html 

From bms at incunabulum.net  Sat Nov 29 11:27:06 2008
From: bms at incunabulum.net (Bruce M. Simpson)
Date: Sat, 29 Nov 2008 19:27:06 +0000
Subject: [Xorp-hackers] how to interact with rtrmgr
In-Reply-To: <235004.77831.qm@web15108.mail.cnb.yahoo.com>
References: <235004.77831.qm@web15108.mail.cnb.yahoo.com>
Message-ID: <4931978A.3010206@incunabulum.net>

?? wrote:
>
>         Hi ,XORP,
>         I am working to add web interface for Xorp.
>         I want to know how to interact with the
>         rtrmgr.could I use the rgrmgr's xrl interface for
>         xorpsh,while ,how?
>         could someone help me?
>         thank you very much!!
>


Sure, you could use the Router Manager's XRL interface. Just look at 
what xorpsh does.

The problem is, how are you going to handle callbacks. A lot is going to 
depend on the choice of your languge for implementation.

At the moment we have layers of C++ stub libraries around the XRL layer 
which are pretty much dependent on the use of the C++ language to 
service XRL callbacks..

One way of getting aroun this is to use the call_xrl binary, this avoids 
having to deal with C++ language bindings; instead you fork call_xrl to 
run the appropriate XRL. Obviously this isn't really useful apart from 
simple shell scripts, but it serves as an example.

If you implement your web front-end in C++, as an XRL capable process, 
then you side-step these problems. If on the other hand you wish to use 
a language which is perhaps more appropriate to web application 
development (e.g. Python, Ruby) then you have the problem of how to 
realize the C++ callbacks in your chosen language.

The alternative is to try to widen the scope of XRL and reduce its C++ 
dependence. I did start work on porting the XRL layer into Python in the 
summer, however, there have been so many changes to the code base since 
then, and not really enough interest from outside to justify the effort 
so I've shelved it.

thanks
BMS