On 12/07/2011 07:13 PM, Ray Soucy wrote: > I haven't had good luck with default-system-configuration and VLAN > interfaces; especially where PIM is concerned. > > You likely need to specify the addresses manually (in addition to > creating the VLAN interfaces manually with vconfig). > > The XORP handling of VLANs has never been great; recent patches have > been made to try an improve it; but it's still has work to be done > before it's up to user expectations.
I don't ever test using default-system-config, but if you find problems when using config from within Xorp, please report the bug. In general, I'd suggest you drive all changes through xorp..ie, tell it to set the IP instead of hoping it will figure things out when you set it outside of xorp. You can script xorpsh using multiple -c 'command 1' -c 'command 2' .... It's not exactly user-friendly, but it works (for my uses, at least). And as always, patches are welcome, as are detailed bug reports with xorp logs, OS & kernel version, etc. Please submit such bug reports to the bugzilla so we don't loose track of it. >> Being familiar with the Cisco routing CLI, these caveats seem quite >> counter-intuitive... Could anybody help me understand if XORP was deployed >> outside the research/academia community? Probably not so much. We use it in our LANforge product, but we drive xorp from our program (which builds networks with a GUI) using programatically created xorpsh commands and xorp config files. Those code paths are pretty well tested, but I'm certain bugs remain to be uncovered. Thanks, Ben -- Ben Greear <[email protected]> Candela Technologies Inc http://www.candelatech.com _______________________________________________ Xorp-hackers mailing list [email protected] http://mailman.ICSI.Berkeley.EDU/mailman/listinfo/xorp-hackers
