Skip to contentSkip to conversation

UDP packet sender

U-Boot Gaëtan Carlier 3 participants 9 messages Jan 18, 2018 – Feb 6, 2018

lore
Share & tools
lore
#0 lore raw

Hi,
I would like to implement a new command and submit it to the mailing list. The command will have the following format:
udpsend <destination/broadcast ip> <destination port> <source port> <text to send>

udpsend 255.255.255.255 4040 0 hello world

If source port is 0, a random port will be used (11000 + (get_timer(0) % 4096))

Where do I have to place my code : cmd or net directory ?
For me cmd will be the better directory to keep it away from all more complex stuff like DHCP, TFTP, ...

Thank you for these informations.
Regards,
Gaëtan.

#1 lore raw

Hi,

Quoted 7 lines · Gaëtan Carlier

Hi,
I would like to implement a new command and submit it to the mailing list. The command will have the following format:
udpsend <destination/broadcast ip> <destination port> <source port> <text to send>

udpsend 255.255.255.255 4040 0 hello world

Quoted 9 lines

If source port is 0, a random port will be used (11000 + (get_timer(0) % 4096))

Where do I have to place my code : cmd or net directory ?
For me cmd will be the better directory to keep it away from all more complex stuff like DHCP, TFTP, ...

Thank you for these informations.
Regards,
Gaëtan.

Ping ?

#2 lore raw

Hi.

Quoted 17 lines

Hi,

Quoted 15 lines · Gaëtan Carlier

Hi,
I would like to implement a new command and submit it to the mailing list. The command will have the following format:
udpsend <destination/broadcast ip> <destination port> <source port> <text to send>

udpsend 255.255.255.255 4040 0 hello world

If source port is 0, a random port will be used (11000 + (get_timer(0) % 4096))

Where do I have to place my code : cmd or net directory ? For me cmd will be the better directory to keep it away from all more complex stuff like DHCP, TFTP, ...

Quoted 6 lines
Quoted 4 lines

Thank you for these informations.
Regards,
Gaëtan.

Ping ?

You should write directly to network u-boot maintainer and add list to CC.

Joe Hershberger <[email protected]>

Quoted 4 lines

_______________________________________________
U-Boot mailing list
U-Boot at lists.denx.de
https://lists.denx.de/listinfo/u-boot

Best regards,

Lukasz Majewski

--

DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Phone: (+49)-8142-66989-10 Fax: (+49)-8142-66989-80 Email: wd at denx.de -------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: application/pgp-signature
Size: 488 bytes
Desc: OpenPGP digital signature
URL: <http://lists.denx.de/pipermail/u-boot/attachments/20180122/e44f25e1/attachment.sig>

#3 lore raw
In reply to Gaëtan Carlier

Hi Gaëtan,

Quoted 8 lines · Gaëtan Carlier

Hi,
I would like to implement a new command and submit it to the mailing list. The command will have the following format:
udpsend <destination/broadcast ip> <destination port> <source port> <text to send>

udpsend 255.255.255.255 4040 0 hello world

If source port is 0, a random port will be used (11000 + (get_timer(0) % 4096))

I'd like to understand the purpose / use-case for this command? Maybe there is a more appropriate way to solve the problem you have instead.

Quoted 2 lines

Where do I have to place my code : cmd or net directory ?
For me cmd will be the better directory to keep it away from all more complex stuff like DHCP, TFTP, ...

That's probably true. cmd/ would be the appropriate place.

-Joe

#4 lore raw

Hi Joe,

Quoted 8 lines · Joe Hershberger

Hi Gaëtan,

Quoted 5 lines · Gaëtan Carlier

Hi,
I would like to implement a new command and submit it to the mailing list. The command will have the following format:
udpsend <destination/broadcast ip> <destination port> <source port> <text to send>

Quoted 7 lines
Quoted 3 lines

udpsend 255.255.255.255 4040 0 hello world

If source port is 0, a random port will be used (11000 + (get_timer(0) % 4096))

I'd like to understand the purpose / use-case for this command? Maybe there is a more appropriate way to solve the problem you have instead.

I want to send the current progression of an update script. As the board has no display/leds, the only way to get update progression is to broadcast UDP packet that a PC software will monitor. U-Boot will load/source a script from an ext4 partition. This script will load a rootfs image from update partition of an eMMC splitted into 10M chunks that will be written to an other partition of the eMMC. This is for update on site (by customer).

This UDP command will also be used in a closed production LAN to send Unique ID of the CPU (secret) and the MAC address to the monitoring production (burning) software that will feed a database to be able to generate license keys linked to hardware and print a label with the product name and the MAC address.

Maybe there is already existing command that I can use from a U-Boot script ?

Quoted 7 lines
Quoted 2 lines

Where do I have to place my code : cmd or net directory ?
For me cmd will be the better directory to keep it away from all more complex stuff like DHCP, TFTP, ...

That's probably true. cmd/ would be the appropriate place.

-Joe

Regards,
Gaëtan

#5 lore raw
Quoted 19 lines · Gaëtan Carlier

Hi Joe,

Quoted 8 lines · Joe Hershberger

Hi Gaëtan,

Quoted 5 lines · Gaëtan Carlier

Hi,
I would like to implement a new command and submit it to the mailing list. The command will have the following format:
udpsend <destination/broadcast ip> <destination port> <source port> <text to send>

Quoted 7 lines
Quoted 3 lines

udpsend 255.255.255.255 4040 0 hello world

If source port is 0, a random port will be used (11000 + (get_timer(0) % 4096))

I'd like to understand the purpose / use-case for this command? Maybe there is a more appropriate way to solve the problem you have instead.

Quoted 6 lines

I want to send the current progression of an update script. As the board has no display/leds, the only way to get update progression is to broadcast UDP packet that a PC software will monitor. U-Boot will load/source a script from an ext4 partition. This script will load a rootfs image from update partition of an eMMC splitted into 10M chunks that will be written to an other partition of the eMMC. This is for update on site (by customer).

This UDP command will also be used in a closed production LAN to send Unique ID of the CPU (secret) and the MAC address to the monitoring production (burning) software that will feed a database to be able to generate license keys linked to hardware and print a label with the product name and the MAC address.

Maybe there is already existing command that I can use from a U-Boot script ?

I think this is commonly done by enabling netconsole and controlling / monitoring progress based on console output sent over UDP.

Cheers,
-Joe

Quoted 10 lines
Quoted 7 lines
Quoted 2 lines

Where do I have to place my code : cmd or net directory ?
For me cmd will be the better directory to keep it away from all more complex stuff like DHCP, TFTP, ...

That's probably true. cmd/ would be the appropriate place.

-Joe

Regards,
Gaëtan

#6 lore raw

Joe,

Quoted 23 lines · Joe Hershberger
Quoted 22 lines · Gaëtan Carlier

Hi Joe,

Quoted 8 lines · Joe Hershberger

Hi Gaëtan,

Quoted 5 lines · Gaëtan Carlier

Hi,
I would like to implement a new command and submit it to the mailing list. The command will have the following format:
udpsend <destination/broadcast ip> <destination port> <source port> <text to send>

Quoted 7 lines
Quoted 3 lines

udpsend 255.255.255.255 4040 0 hello world

If source port is 0, a random port will be used (11000 + (get_timer(0) % 4096))

I'd like to understand the purpose / use-case for this command? Maybe there is a more appropriate way to solve the problem you have instead.

I want to send the current progression of an update script. As the board has no display/leds, the only way to get update progression is to broadcast UDP packet that a PC software will monitor. U-Boot will load/source a script from an ext4 partition. This script will load a rootfs image from update partition of an eMMC splitted into 10M chunks that will be written to an other partition of the eMMC. This is for update on site (by customer).

Quoted 6 lines
Quoted 3 lines

This UDP command will also be used in a closed production LAN to send Unique ID of the CPU (secret) and the MAC address to the monitoring production (burning) software that will feed a database to be able to generate license keys linked to hardware and print a label with the product name and the MAC address.

Maybe there is already existing command that I can use from a U-Boot script ?

I think this is commonly done by enabling netconsole and controlling / monitoring progress based on console output sent over UDP.

a) I can/want not enable netconsole when the product is on the network of the customer.
b) Once on customer LAN, everything is DHCP.
c) I don't want to increase load of CPU because updating software on customer's computer has to decode all UDP frames sent by U-Boot while 10% of UDP are really needed (several boards can be on the same network).

Quoted 14 lines

Cheers,
-Joe

Quoted 10 lines
Quoted 7 lines
Quoted 2 lines

Where do I have to place my code : cmd or net directory ?
For me cmd will be the better directory to keep it away from all more complex stuff like DHCP, TFTP, ...

That's probably true. cmd/ would be the appropriate place.

-Joe

Regards,
Gaëtan

Regards,
Gaëtan.

#7 lore raw
Quoted 17 lines · Gaëtan Carlier

Joe,

Quoted 15 lines · Joe Hershberger
Quoted 14 lines · Gaëtan Carlier

Hi Joe,

Quoted 11 lines · Joe Hershberger

Hi Gaëtan,

Quoted 8 lines · Gaëtan Carlier

Hi,
I would like to implement a new command and submit it to the mailing list. The command will have the following format:
udpsend <destination/broadcast ip> <destination port> <source port> <text to send>

udpsend 255.255.255.255 4040 0 hello world

If source port is 0, a random port will be used (11000 + (get_timer(0) % 4096))

If you want to add this, add it as a command in cmd/netcat.c and use the same semantics as netcat as much as possible. Since there is no pipe support in U-Boot's shell, the data to send will have to be a parameter. Best to make it something that does not collide with netcat.

In netcat, you specify a "-u" switch to enable UDP, so your command would require that switch (so TCP could be added later).

So that means your invocation should be "nc -u -p <srcport> <host> <dstport> -- Text to send"

Quoted 36 lines
Quoted 7 lines
Quoted 7 lines
Quoted 3 lines

I'd like to understand the purpose / use-case for this command? Maybe there is a more appropriate way to solve the problem you have instead.

I want to send the current progression of an update script. As the board has no display/leds, the only way to get update progression is to broadcast UDP packet that a PC software will monitor. U-Boot will load/source a script from an ext4 partition. This script will load a rootfs image from update partition of an eMMC splitted into 10M chunks that will be written to an other partition of the eMMC. This is for update on site (by customer).

Quoted 6 lines
Quoted 3 lines

This UDP command will also be used in a closed production LAN to send Unique ID of the CPU (secret) and the MAC address to the monitoring production (burning) software that will feed a database to be able to generate license keys linked to hardware and print a label with the product name and the MAC address.

Maybe there is already existing command that I can use from a U-Boot script ?

I think this is commonly done by enabling netconsole and controlling / monitoring progress based on console output sent over UDP.

a) I can/want not enable netconsole when the product is on the network of the customer.
b) Once on customer LAN, everything is DHCP.
c) I don't want to increase load of CPU because updating software on customer's computer has to decode all UDP frames sent by U-Boot while 10% of UDP are really needed (several boards can be on the same network).

Quoted 14 lines

Cheers,
-Joe

Quoted 10 lines
Quoted 7 lines
Quoted 2 lines

Where do I have to place my code : cmd or net directory ?
For me cmd will be the better directory to keep it away from all more complex stuff like DHCP, TFTP, ...

That's probably true. cmd/ would be the appropriate place.

-Joe

Regards,
Gaëtan

Regards,
Gaëtan.

#8 lore raw

Hi Joe,

Quoted 25 lines · Joe Hershberger
Quoted 17 lines · Gaëtan Carlier

Joe,

Quoted 15 lines · Joe Hershberger
Quoted 14 lines · Gaëtan Carlier

Hi Joe,

Quoted 11 lines · Joe Hershberger

Hi Gaëtan,

Quoted 8 lines · Gaëtan Carlier

Hi,
I would like to implement a new command and submit it to the mailing list. The command will have the following format:
udpsend <destination/broadcast ip> <destination port> <source port> <text to send>

udpsend 255.255.255.255 4040 0 hello world

If source port is 0, a random port will be used (11000 + (get_timer(0) % 4096))

If you want to add this, add it as a command in cmd/netcat.c and use the same semantics as netcat as much as possible. Since there is no pipe support in U-Boot's shell, the data to send will have to be a parameter. Best to make it something that does not collide with netcat.

Quoted 6 lines

In netcat, you specify a "-u" switch to enable UDP, so your command would require that switch (so TCP could be added later).

So that means your invocation should be "nc -u -p <srcport> <host> <dstport> -- Text to send"

Thank you for these informations. I will do that.

Quoted 28 lines
Quoted 28 lines
Quoted 7 lines
Quoted 7 lines
Quoted 3 lines

I'd like to understand the purpose / use-case for this command? Maybe there is a more appropriate way to solve the problem you have instead.

I want to send the current progression of an update script. As the board has no display/leds, the only way to get update progression is to broadcast UDP packet that a PC software will monitor. U-Boot will load/source a script from an ext4 partition. This script will load a rootfs image from update partition of an eMMC splitted into 10M chunks that will be written to an other partition of the eMMC. This is for update on site (by customer).

Quoted 6 lines
Quoted 3 lines

This UDP command will also be used in a closed production LAN to send Unique ID of the CPU (secret) and the MAC address to the monitoring production (burning) software that will feed a database to be able to generate license keys linked to hardware and print a label with the product name and the MAC address.

Maybe there is already existing command that I can use from a U-Boot script ?

I think this is commonly done by enabling netconsole and controlling / monitoring progress based on console output sent over UDP.

a) I can/want not enable netconsole when the product is on the network of the customer.
b) Once on customer LAN, everything is DHCP.
c) I don't want to increase load of CPU because updating software on customer's computer has to decode all UDP frames sent by U-Boot while 10% of UDP are really needed (several boards can be on the same network).

Quoted 9 lines

Cheers,
-Joe

Quoted 5 lines
Quoted 5 lines
Quoted 2 lines

Where do I have to place my code : cmd or net directory ?
For me cmd will be the better directory to keep it away from all more complex stuff like DHCP, TFTP, ...

That's probably true. cmd/ would be the appropriate place.

Quoted 8 lines
Quoted 8 lines
Quoted 5 lines
Quoted 5 lines
Quoted 2 lines

-Joe

Regards,
Gaëtan

Regards,
Gaëtan.

Regards,
Gaëtan.