[Xorp-hackers] De-facto xorprtm dll / "RTMv2" -- is [IMHO] very _experimenal_ feature Re: xorprtm dll.

Victor Miasnikov vvm at tut.by
Thu Mar 15 09:34:23 PDT 2012


Hi!

> Do you think you

 I'm think what .dll / module(!) for MS Software ( RRAS) need be compile with MS VC ,  and _best_ with version what 
corresponded Windows

IMHO, need personal .dll for NT52 / NT60 / NT61 / NT62 and may be for even(!) SP / HotFix


> could get it to compile using the mingw cross-compiler
> so that it's automatically compiled?

 In any case for build xorprtm dll need *..h and *.lib from MS Platform SDK  . . .



http://mailman.icsi.berkeley.edu/pipermail/xorp-users/2009-May/003172.html
===
...
 From this point I decided to go back to Routing and Remote Access, and
had it running doing OSPF

2012-03-15 VVM: In Windows 2008  RRAS not contain(!) OSPF  ( in Win 2003 -- RRAS can work with OSPF)

while I tried to convince Xorp to just do the
multicast stuff.  Sadly all 3 versions complained about not having an
RTMv2 pipe available.  I found the source code for the relevant dll in
contrib/win32/xorprtm, convinced it to compile (using the suggested
Visual C++ Toolkit 2003, and the Windows Server 2003 R2 Platform SDK,
after having to add some #include lines to bsdroute.h), and put that in,
at which point I was able to get Xorp running again. It's at this point
I hit what seems to be my final roadblock, and sadly it wasn't in the
release notes (though I've since found it in the build notes): Multicast
routing is not supported on Windows.
...

So at the moment, I'm stuck.  I'm wondering if it's possible to just get
Xorp to handle the PIM stuff on it's own, though to be honest, I don't
know enough about multicast to know if that would be sufficient.

Does anyone have any ideas about a solution to this mess?  Aside from
using a different operating system, of course, as I'm stuck with Windows
on this one.

 . . .
===




> That would be the best way to support the dll

 Yes . . . But . . .

>  I think, and then we can just package it up with
> the xorp executables.

 De-facto xorprtm dll / "RTMv2" -- is [IMHO] very _experimenal_ feature

For example:
BUGS
==
 - Routes appear in the RTM routing table but do not propagate to  the FIB.
   This can be verified by comparing the output of 'route print'
   with that of 'netsh routing ip show rtmroutes'.
==

 I.e. xorprtm dll itself work as need ( if run ( in OS shell ) 'netsh routing ip show rtmroutes' -- all Ok ),
but 'route print' not show new routes! :-(



[IMHO] xorprtm dll / "RTMv2"  need some [big] improvements /  see TODO :
==
Tasks depending on Microsoft feedback:
 Fix route adds so they are pushed to the FIB.
  Blocked awaiting feedback.
 Refine and test IPv6 support.
  Blocked on missing defines in SDK.
  Blocked awaiting feedback.
==
 +
BUGS
==
  . . .

 * XXX: The following identifiers seem to be missing from the Windows SDK
   build 5284 headers:
 IPV6_ADDRESS_LEN_IN_BYTES
 ConvertAddressAndLengthToNetAddress()
 ConvertNetAddressToAddressAndLength()
   referenced by:
 RTM_IPV6_SET_ADDR_AND_LEN()
 RTM_IPV6_GET_ADDR_AND_LEN()
   There also seems to be no RTM_IPV6_MASK_FROM_LEN() function, which
   we'd need for converting our IPv6 prefix lengths to socket address
   structures for the modified BSD message format we currently use.
==

 IMHO at this time need be do:

>> May be turn off windows_rras_support by default?
>>
>> Who can compile xorprtm dll -- can be simply turn on feature by recompile XORP
>>
>> And not-developer can be work with XORP on windows comps with RRAS component
>> ( RRAS very offten not configure as _router_ , usual it simply installed by other MS software )



 and in [near]  future -- start work with upgrade "xorprtm dll" . . .


Best regards, Victor Miasnikov
Blog:  http://vvm.blog.tut.by/


----- Original Message ----- 
From: "Ben Greear" greearb
To: "Victor Miasnikov" vvm
Cc: xorp-hackers
Sent: Thursday, March 15, 2012 6:57 PM
Subject: xorprtm dll.


> On 03/15/2012 08:46 AM, Victor Miasnikov wrote:

  . . .

>> + // VVM 2012-03-15 first // -- need skipped, ZZZZZZ -- is very trivial "copy & paste", but at this moment
>> xorprtm4.dll may be solved problem by traditial way, if not success -- i'm public [PATCH]
>> ==
>>
>> May be turn off windows_rras_support by default?
>>
>> Who can compile xorprtm dll -- can be simply turn on feature by recompile XORP
>>
>> And not-developer can be work with XORP on windows comps with RRAS component
>> ( RRAS very offten not configure as _router_ , usual it simply installed by other MS software )
>
>
> Do you think you could get it to compile using the mingw cross-compiler
> so that it's automatically compiled?  That would be the best way to
> support the dll I think, and then we can just package it up with
> the xorp executables.
>
> Thanks,
> Ben



More information about the Xorp-hackers mailing list