This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.
Hi Jay and Gregg, re: > sbn1 has been configured to support multicast routing: > > 224.0.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 em2 > 224.0.1.2 0.0.0.0 255.255.255.255 UH 0 0 0 em2 > 224.0.1.3 0.0.0.0 255.255.255.255 UH 0 0 0 em2 > 224.0.1.4 0.0.0.0 255.255.255.255 UH 0 0 0 em2 > 224.0.1.5 0.0.0.0 255.255.255.255 UH 0 0 0 em2 > 224.0.1.6 0.0.0.0 255.255.255.255 UH 0 0 0 em2 > 224.0.1.7 0.0.0.0 255.255.255.255 UH 0 0 0 em2 > 224.0.1.8 0.0.0.0 255.255.255.255 UH 0 0 0 em2 > 224.0.1.9 0.0.0.0 255.255.255.255 UH 0 0 0 em2 > 224.0.1.10 0.0.0.0 255.255.255.255 UH 0 0 0 em2 Sounds good! Out of curiosity and "for the files", was this done by creating a route-em2 file in /etc/sysconfig/network-scripts and then bouncing the em2 interface? Gregg: Will you be able to change the LDM configuration file setup for sbn1 today and let us now the results of the change? Thanks for the information! Cheers, Tom -- **************************************************************************** Unidata User Support UCAR Unidata Program (303) 497-8642 P.O. Box 3000 address@hidden Boulder, CO 80307 ---------------------------------------------------------------------------- Unidata HomePage http://www.unidata.ucar.edu **************************************************************************** Ticket Details =================== Ticket ID: HDQ-517625 Department: Support NOAAPORT Priority: Normal Status: Closed =================== NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.