I also just noticed your application when i needed to
distribute some source to a few machines for testing
and the speed of unicast SCPs seemed to be a bad idea.
Only problem is I have a heterogeneous environment --
so i needed the build to work under solaris. Well, i
suppose the authors know -- it doesn't.
I cooked up a few changes so that it appears to work
for me and i wanted to contribute it to you.
Where do I send it?
Mike
__________________________________
Do you Yahoo!?
Yahoo! Mail SpamGuard - Read only the mail you want.
http://antispam.yahoo.com/tools
Has anyone used udpcast under Solaris?
I am trying to compile under Solaris 9 and have worked out the compile errors (I hope) and am resolving linker problems now. The hacks I've made aren't pretty and would break under IPv6 but. I was hoping someone may have already done a port. Thanks for any assistance.
John
I tried udpcast a few days ago and it worked well. The full duplex
option to udp-sender was important to making it stable in my test.
I have a couple of questions...
1. (not exactly a udpcast question, but related...)
How can I set up DHCP/TFTP so that it doesn't require a
specific MAC address to direct a machine to the pxeboot image?
2. How can I provide the etherboot/PXE client machine with the
menu file for udp-receiver?
3. Can the DHCP/TFTP server be different than the box
running udp-sender? (Were the same in my test).
I'm investigating how this can be used to image 4000 laptops
for a University, and in this case a bootable floppy or
CDROM is too cumbersome.
--Donald Teed
[Bringing message back on-list.]
Back in the annals of history,
Alain Knaff wrote:
>On Saturday 18 October 2003 00:39, you wrote:
>
>
> [I wrote something here]
>
>The only difference is a difference in network distance: most current
>users use udpcast on a LAN (traffic needs to cross no routers),
>whereas you seem to plan a usage on a WAN. That is fine, the only
>difference is that in such case some tweaking with the mcast-addr and
>--mcast-all-addr settings might be needed to help the multicast
>traffic traverse the routers.
>
>
Having spent a great deal of time of enery of my own, my coworkers, and
the nice folks at Cisco, I just wanted to post this to the archives that
the statement "--mcast-all-addr settings *might* be needed" should
really read "IS needed". Cisco routers, at the least, do not forward
packets destined for 224.0.0.1, which is the default for udpcast.
Changing this is required for clients to find one another.
That point aside, thanks for the useful software and for bearing me out
these 5 months ago.
regards,
Chris
Hi,
I would like to know if there is a solution to get udpcast
working with NVIDIA nForce MCP Networking Controller.
SysRescCD uses nvnet driver with this card.
I didn't find it on cast-o-matic.
Can you help me?
Thank you very much.
--
Stephane
********** PROTEGEZ VOS E-MAILS !**********
Avec Tiscali SuperMail, vos e-mails en toute sécurité !
Anti Spam personnalisable
Anti Virus actualisé en permanence
et de nombreux bonus...
Pour en savoir plus, rendez-vous sur http://www.tiscali.fr/supermail/
Hi,
I can't find net driver for nForce chipset on
http://www.udpcast.linux.lu/cast-o-matic/
SysRescCD uses nvnet module for this card.
Can you help me?
Thank you very much!
--
Stephane.