Sponsored Content
Special Forums IP Networking Discover Windows machines in other network Post 302910154 by gjws on Tuesday 22nd of July 2014 08:02:53 PM
Old 07-22-2014
I believe that DLNA uses Multicast to advertise itself, so depending on the router you are using you may be able to configure something like IGMP to enable multicast routing.
 

9 More Discussions You Might Find Interesting

1. IP Networking

what can i use to network between windows and solaris.

Hi.. i tring to file share between microsoft and sun solaris, i heard of samba but what can i do with it.. is it easy to use or to understand, where can i get the software, any information will be a great help.. thanks (3 Replies)
Discussion started by: souldier
3 Replies

2. IP Networking

troubles networking Windows machines to RH7.1 Linux

i hear everyone talking about this SAMBA "service" that comes with Linux distros...im having no luck getting this to work, neither one of the boxes on the network sees each other. im only an intermediate level user of Linux...Networking with Windows machines is relatively new to me, so you can... (3 Replies)
Discussion started by: fuji250
3 Replies

3. Linux

Linux on Windows network

Hey all. I want to connect my Linux box on the work network (I'm on-site support, so I'm allowed to :) ). I can login as root (or any other user) and get my IP which I want, browse the web as I've set the box up for that. But what I want to do now is authenticate myself on the network so I... (3 Replies)
Discussion started by: woofie
3 Replies

4. IP Networking

How can i simulate network problems between unix machines ?

Hello all i need to simulate method invocations between 2 machine ( using corba ) now i like to test the method invoke timeout from machine1 to machine2 for that i need to simulate network being busy , can it be done some how ? (2 Replies)
Discussion started by: umen
2 Replies

5. HP-UX

Windows and Linux OS for HP-UX machines

Hi All, I'm not sure if this has been posted before. Anyone knows a site how to do a hardware check (ex. ioscan) on an HP-UX machine that runs in Linux,Solaris and Windows? I'm checking the docs.hp.com and it gives me HP-UX stuff. does HP even supports such highlevel commands we use on HP-UX OS?... (2 Replies)
Discussion started by: grumash
2 Replies

6. UNIX for Advanced & Expert Users

ping all the machines in the network

Is there any option for the utility "ping" , which can ping all the machines in the network? (5 Replies)
Discussion started by: praveen_b744
5 Replies

7. UNIX for Dummies Questions & Answers

output of file from several machines written to network share, then emailed to group.

I have a script on all the machines on my network that lists how many updates are available for each machine, and then outputs the answer to a file called updates.txt the output shows the hostname and the number of updates, like: computer_A 7 I want all these machines to output the data to... (1 Reply)
Discussion started by: glev2005
1 Replies

8. Red Hat

application to be run on machines connected in same network

I have a set up of 5 machines which are connected in same network. Now i want to run a small application so that those machines are not ideal. (0 Replies)
Discussion started by: pradeepreddy
0 Replies

9. Windows & DOS: Issues & Discussions

How to Install Windows Xp on Network?

If you don't have DVD-Rom then how would you install windows Xp on Network? (2 Replies)
Discussion started by: karman0931
2 Replies
in.rdisc(1M)						  System Administration Commands					      in.rdisc(1M)

NAME
in.rdisc, rdisc - network router discovery daemon SYNOPSIS
/usr/sbin/in.rdisc [-a] [-f] [-s] [send-address] [receive-address] /usr/sbin/in.rdisc -r [-p preference] [-T interval] [send-address] [receive-address] DESCRIPTION
in.rdisc remains part of the software distribution of the Solaris Operating Environment. It is, however, not used by default. in.routed(1M) includes the functionality provided by in.rdisc. See routeadm(1M) for details of how to specify the IPV4 routing daemon. in.rdisc implements the ICMP router discovery protocol. The first form of the command is used on hosts and the second form is used on routers. in.rdisc can be invoked in either the first form (host mode) or second form (router mode). On a host, in.rdisc populates the network routing tables with default routes. On a router, advertises the router to all the hosts. Host (First Form) On a host, in.rdisc listens on the ALL_HOSTS (224.0.0.1) multicast address for ROUTER_ADVERTISE messages from routers. The received mes- sages are handled by first ignoring those listed router addresses with which the host does not share a network. Among the remaining addresses, the ones with the highest preference are selected as default routers and a default route is entered in the kernel routing table for each one of them. Optionally, in.rdisc can avoid waiting for routers to announce themselves by sending out a few ROUTER_SOLICITATION messages to the ALL_ROUTERS (224.0.0.2) multicast address when it is started. A timer is associated with each router address. The address will no longer be considered for inclusion in the routing tables if the timer expires before a new advertise message is received from the router. The address will also be excluded from consideration if the host receives an advertise message with the preference being maximally negative or with a lifetime of zero. Router (Second Form) When in.rdisc is started on a router, it uses the SIOCGIFCONF ioctl(2) to find the interfaces configured into the system and it starts lis- tening on the ALL_ROUTERS multicast address on all the interfaces that support multicast. It sends out advertise messages to the ALL_HOSTS multicast address advertising all its IP addresses. A few initial advertise messages are sent out during the first 30 seconds and after that it will transmit advertise messages approximately every 600 seconds. When in.rdisc receives a solicitation message, it sends an advertise message to the host that sent the solicitation message. When in.rdisc is terminated by a signal, it sends out an advertise message with the preference being maximally negative. OPTIONS
-a Accept all routers independent of the preference they have in their advertise messages. Normally, in.rdisc only accepts (and enters in the kernel routing tables) the router or routers with the highest preference. -f Run in.rdisc forever even if no routers are found. Normally, in.rdisc gives up if it has not received any advertise message after soliciting three times, in which case it exits with a non-zero exit code. If -f is not specified in the first form then -s must be specified. -r Act as a router, rather than a host. -s Send three solicitation messages initially to quickly discover the routers when the system is booted. When -s is specified, in.rdisc exits with a non-zero exit code if it can not find any routers. This can be overridden with the -f option. -p preference Set the preference transmitted in the solicitation messages. The default is zero. -T interval Set the interval between transmitting the advertise messages. The default time is 600 seconds. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWroute | +-----------------------------+-----------------------------+ SEE ALSO
in.routed(1M), routeadm(1M), ioctl(2), gateways(4), attributes(5), icmp(7P), inet(7P) Deering, S.E., editor, ICMP Router Discovery Messages, RFC 1256, Network Information Center, SRI International, Menlo Park, California, September 1991. SunOS 5.10 5 Nov 2004 in.rdisc(1M)
All times are GMT -4. The time now is 07:14 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy