This was working and now it has stopped.
Have a UDPcast server running on a HP DL360G5 with 4 NICS. One
connected to an internal infrastructure (eth2) and another connected
to a dedicated switch with the client systems on the same switch (eth3).
When i run the UDPcast send or receive, using the following command:
udp-sender -f /home/base.udpc --interface eth3 --point-to-point --full-
duplex --max-bitrate 600m --nokbd --portbase=9922 --min-receivers 1 --
rexmit-hello-interval 5000 --max-wait 300
I get the following error message:
No suitable network interface found
The following interfaces are available:
Interestingly, an ifconfig show eth3 as a valid network adapter, but
the udp-sender does not see the device. This was working last week,
and nothing has changed on the server
I have tried everything, restarting DHCP, removing the interface and
adding again. Rebooted the server, restarted the network stack
manually. nothing seems to help.
Using SUSE linux 10 as the base server OS.
I'd like to use udp-sender with async and a unicast address instead of
multicast so that unicast at the MAC layer is actually used.
Ive tried using the pointopoint switch, but I get the message "pointopoint
mode set, and 0 participants instead of 1".
Is there a way to do this with udpcast?
I've been using UDP Cast extensively for a while now and I love it, but I
had an issue last week and I want to share it witou you.
The UDP Cast website provides handy ready-made boot images. Apparently,
those images are compiled for i686 and I couldn't make them work on an
older machine because the processor doesn't implement the CMOV operation.
The problem seem to belong to GCC, because it thinks that every i686
processor implements the optional CMOV operation, which is not true.
I solved the problem by compiling my own UDP Cast kernel, but I suggest
that the next UDP Cast ready-made boot images drop the i686 requirement
and stick to i386, for compatibility reasons.
Is this a reasonable request?
Thank you and best regards,
Engenharia Informatica e de Computadores - Instituto Superior Tecnico
On Tue, Apr 28, 2009 at 2:50 PM, Autuori Gianluigi
> I start the first pc with iso image of udpcast.
> I configure eth manualy
> Then I start sender and it waits for connection
> Now I switch on second pc and I select boot from network, but it doesn't find any dhcp server available
udpcast does neither include a dhcp server nor a tftp server.
As PXE booting is a somewhat more complex setup, you would need a
separate PC (besides your udpsender and udpreceiver) which should run
a (configured) tftpd and a (configured) dhcpd.
Maybe you would be able to use Udpcast Image Generator to embed tftpd
and dhcpd into udpcast. However, I would consider this a a pretty much
time consuming task. So you really should try to get a third machine
as a real server.
Hello, I'm Spanish and I work in the La Laguna University. I love this tool,
I never see another like this, it is simple and useful. BUT there isn't a
atl2 network driver and it not works on we new computers. We try to use the
udpcast boot image generator, but an kernel panic error is given. I'll like
you can add de atl2 driver to the ready made boot images. Thanks.
Cristo Javier Reyes Rodríguez
ULL, Tenerife, España.
I have some problems with udpcast and quite a few computers using this network card:
01:0d.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
the right module for it is 8139too that I can use by doing:
/usr/lib/udpcast/makeImage -k vmlinuz-126.96.36.199udpcast -i initRd -m 8139too --fullbox
and if I boot with this kernel and initrd (using PXE) eth0 gets detected and seems to work (i can se a bunch of ethernet related messages on F6.
of course then nothing works becouse hdd is not available...
If I include modules for ata controller like this:
/usr/lib/udpcast/kernel# /usr/lib/udpcast/makeImage -k vmlinuz-188.8.131.52udpcast -i initRd -m libata ata_generic ata_piix 8139too --fullbox
Then even if I select 8139too when it asks me which module to use it complains that network is not available :(
Attached are results of lspci and lsmod commands on ubuntu installed on this machine.