EEM send UDP broadcast

I need an "action" statement that will send a UDP broadcast to port 1001 with a message of "restart". I have the rest of the EEM script created fine. I cannot seem to figure out how to do this. I have a BGP route that changes every once in a while and when it does the application seems to stop functioning correctly. A restart of the application fixes the issue. The vendor says that if I can send the UDP broadcast then he can program it to see the broadcast and restart iteself. I have created an EEM script that sees the syslog "%BGP-5-ADJCHANGE:" and currently sends an email. BUt we have to manually restart the app. If this is not possible within EEM could it be done with a TCL script and the EEM call the TCL script?
I appreciate any words of wisdom. Thank you in advance.

EEM currently does not support UDP. Yes, a tclsh called from EEM could do this assuming you have a new enough IOS. The UDP extension is documented at
http://www.cisco.com/en/US/docs/ios-xml/ios/ios_tcl/configuration/12-4t/nm-script-tcl.html .

Similar Messages

Unable to receive UDP broadcast packets on PPP connection

I am struggling for two days now with no success. I have two modems (do not ask, some special stuff), that uses dial up (PPP) connection. I tried this on windows XP and it works like a charm. I am sending unicast and broadcast UPD packets. If I
repeat that on Windows 7 i can send only unicast data, broadcast packets seems to be lost somewhere. I tried to use Microsoft Network Monitor and I can see that broadcasted packets are being received on my PPP connection. But after that, they are gone. Somewhere
in the kernel. I truly do not understand why. I disabled firewall, antivirus, base filtering engine, tried to log dropped packed in Windows
Filtering Platform, tried clean WIN7 machine and all that with no success.
Here is a sample packet received on interface, but it has newer reach my app:
No. Time Source Destination Protocol Length Info
1 13:20:56.093380000 192.168.1.50 192.168.1.255 UDP 49 Source port: x11 Destination port: x11
Frame 1: 49 bytes on wire (392 bits), 49 bytes captured (392 bits)
Encapsulation type: Ethernet (1)
Arrival Time: May 7, 2014 13:20:56.093380000 Central Europe Daylight Time
[Time shift for this packet: 0.000000000 seconds]
Epoch Time: 1399461656.093380000 seconds
[Time delta from previous captured frame: 0.000000000 seconds]
[Time delta from previous displayed frame: 0.000000000 seconds]
[Time since reference or first frame: 0.000000000 seconds]
Frame Number: 1
Frame Length: 49 bytes (392 bits)
Capture Length: 49 bytes (392 bits)
[Frame is marked: False]
[Frame is ignored: False]
[Protocols in frame: eth:ip:udp:data:vssmonitoring]
[Coloring Rule Name: UDP]
[Coloring Rule String: udp]
Ethernet II, Src: ae:4e:20:00:01:00 (ae:4e:20:00:01:00), Dst: Xerox_00:00:00 (01:00:01:00:00:00)
Destination: Xerox_00:00:00 (01:00:01:00:00:00)
Address: Xerox_00:00:00 (01:00:01:00:00:00)
.... ..0. .... .... .... .... = LG bit: Globally unique address (factory default)
.... ...1 .... .... .... .... = IG bit: Group address (multicast/broadcast)
Source: ae:4e:20:00:01:00 (ae:4e:20:00:01:00)
Address: ae:4e:20:00:01:00 (ae:4e:20:00:01:00)
.... ..1. .... .... .... .... = LG bit: Locally administered address (this is NOT the factory default)
.... ...0 .... .... .... .... = IG bit: Individual address (unicast)
Type: IP (0x0800)
Internet Protocol Version 4, Src: 192.168.1.50 (192.168.1.50), Dst: 192.168.1.255 (192.168.1.255)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00: Not-ECT (Not ECN-Capable Transport))
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..00 = Explicit Congestion Notification: Not-ECT (Not ECN-Capable Transport) (0x00)
Total Length: 34
Identification: 0x0032 (50)
Flags: 0x00
0... .... = Reserved bit: Not set
.0.. .... = Don't fragment: Not set
..0. .... = More fragments: Not set
Fragment offset: 0
Time to live: 126
Protocol: UDP (17)
Header checksum: 0xb817 [correct]
[Good: True]
[Bad: False]
Source: 192.168.1.50 (192.168.1.50)
Destination: 192.168.1.255 (192.168.1.255)
[Source GeoIP: Unknown]
[Destination GeoIP: Unknown]
User Datagram Protocol, Src Port: x11 (6001), Dst Port: x11 (6001)
Source port: x11 (6001)
Destination port: x11 (6001)
Length: 14
Checksum: 0xafd1 [validation disabled]
[Good Checksum: False]
[Bad Checksum: False]
Data (6 bytes)
0000 34 34 34 34 34 34 444444
Data: 343434343434
[Length: 6]
VSS-Monitoring ethernet trailer, Source Port: 127
Src Port: 127
I am running out of my ideas, if anyone could help, with any idea, please do. I am not sure if this feature is dropped in win7 or not.

Hi,
From your description, you may gather the network monitor traces to ensure which part lost UDP broadcast packets.
Thank you.
Best regards,
Stevens Song
Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

DatagramSocket not picking up UDP broadcasts

Hi All.
Opened a DatagramSocket on specific port. Verfied (w/ tcpdump) that other process is sending UDP packets to that port with broadcast address (128.0.3.255). {pseudocode}DatagramSocket.recieve(dgram) never picks up the packets.
If I change the sender to use specific IP (unicast), the recieve gets the packet and unblocks.
JRE1_5
Any ideas?
-K

Are you binding the socket to the wildcard address?
Is that really your broadcast address? The 128.0.0.0/16 address block is slightly unusual (RFC 3330). broadcast = ip_address | ~netmask; (or use 255.255.255.255).
Try these programs; do they work for you? If they do, what is different between these and your program:
import java.io.*;
import java.net.*;
public class BroadcastSend
    public static void main(String args[])
     throws Exception
     DatagramSocket socket = new DatagramSocket();
     socket.setBroadcast(true);
     socket.setReceiveBufferSize(64 * 1024);
     socket.setSendBufferSize(64 * 1024);
     int str_size = args.length == 0 ? 256 : Integer.parseInt(args[0]);
     StringBuffer str = new StringBuffer();
     while (str.length() < str_size)
         str.append("hello world");
     str.setLength(str_size);
     byte buf[] = str.toString().getBytes("ISO-8859-1");
     InetAddress address = InetAddress.getByName("255.255.255.255");
     DatagramPacket packet = new DatagramPacket(buf, buf.length, address, 6666);
     socket.send(packet);
import java.io.*;
import java.net.*;
public class BroadcastReceive
    public static void main(String args[])
     throws Exception
     DatagramSocket socket = new DatagramSocket(6666);
     socket.setBroadcast(true);
     socket.setReceiveBufferSize(64 * 1024);
     socket.setSendBufferSize(64 * 1024);
     while (true) {
         byte buf[] = new byte[64 * 1024];
         DatagramPacket packet = new DatagramPacket(buf, buf.length);
         socket.receive(packet);
         System.out.println("got " + packet.getLength() +
                      " bytes from " + packet.getAddress());
}

My controller seems to stop udp broadcast

Hello,
I have a remote control sending
UDP packet ->
src:172.17.1.173:1065 dst:255.255.255.255:30718
But the recepter (on wire network) do not receive anything.
Both are on same subnet -> 172.17.1.160/28
We do not use any ACL
idea why?
Many thanks for your precious help.
Cheers
Gael

Hi Gael,
Have you enabled broadcast on controller? Can you try "config network broadcast enable" and see if that resolves the issue.
Regards,
Ankur
*Pls rate all helpfull post

UDP BROADCAST

Hello,
is there any way to send one byte on udp broadcast
(255.255.255.255) port 8999 and listen the response with
actionscript.
Thanks a lot

You would need to either enable multicast-unicast on the WLC or the more preferred method would be to enable multicast-multicast on the WLC under CONTROLLER>General. Unicast is a lot of overhead on the WLC as the WLC has to replicate the packet for every AP that is joined to it. With multicast, you have to multicast routing on the network and PIM enabled on the WLC management interface VLAN, the AP VLAN(s), and the client VLAN(s).
Thanks,
Lee

Sending udp packets using java and receiving it using c

hi,
Is it possible to send udp packets using java and receive the same using c??????? if yes.... plz help immediately.

The biggest issue is data format. The JVM is big endian, with 16-bit characters. The machine running 'C' could be almost anything. A (signed!) byte array is probably the easiest unit of exchange.
The Java program has its own techniques for storing/retrieving data to/from the byte array - and the C program has its own techniques. ASCII Strings are often the easiest to exchange - just convert the java String objects to byte array and send them.
apaliwal1 has already given the UDP calls to send/receive the data.

UDP broadcast over multinetted VLAN

We're having an issue with UDP broadcast over a VLAN that has three IP's configured on it. This is on a Cat 6509.
interface Vlan11
description ZZZZ
ip address 10.10.249.1 255.255.255.0 secondary
ip address 10.10.250.1 255.255.255.0 secondary
ip address 192.168.101.1 255.255.255.0
no ip redirects
ip pim sparse-mode
The device broadcasting is 192.168.101.34.
We've added the global config:
ip forward-protocol udp 4444
And we've tried interface commands like:
ip helper-address 192.168.101.34
and
ip directed broadcast
Nothing seems to help, though. Are there any inherit limitations due to the multinet? Devices on the 192.168.101.0/24 subnet receive the broadcast fine. Devices on the other two subnets do not. Basic routing between all subnets is fine.
Thanks,
Joe

Hi John,
If you're running 2008R2 DHCP, you can fix the DHCP issue that you're having by configuring a DHCP super scope on the DHCP server. We ran into that problem too and managed to get DHCP working on all three subnets. I know it works on 2008R2 but not sure on other versions.
We're mandated to get off the 192.168.101.0 subnet; so, if we can't get it working this way we may need to do a complete cutover including re-IP-ing all devices involved in this dilemma. It's more complicated than I'm stating as this is basically a troubleshooting step to see why it broke. There's an application server involved, an audio streaming server, and some Barix devices. We're attempting to get all the workstations cutover first when we ran into this issue.
Thank you,
Joe

Sending UDP to WP8.1 emulator does not work

I have very simple test app that sends UDP data from Windows desktop app to the app on Windows Phone 8.1 emulator and it does not work for me. Here is desktop code that sends data:
UdpClient c = new UdpClient();
c.Connect(new IPEndPoint(IPAddress.Parse("127.0.0.1"), 49003));
byte[] b = new byte[] { 1,2,3,4 };
c.Send(b, b.Length);
And here is Windows Phone 8.1 app that should receive it.
private async void btnTest_Click(object sender, RoutedEventArgs e)
var h = new Windows.Networking.HostName("localhost");
DatagramSocket dss = new DatagramSocket();
dss.MessageReceived += dss_MessageReceived;
dss.Control.DontFragment = true;
await dss.BindEndpointAsync(h, "49003");
async void dss_MessageReceived(DatagramSocket sender, DatagramSocketMessageReceivedEventArgs args)
MessageDialog md = new MessageDialog("Received something");
await md.ShowAsync();
The very simple desktop app receives UDP data but the app in windows phone emulator does not receive anything. I tried changing IP addresses in sending app, changing port numbers, looked at windows firewall but nothing worked so far. Any ideas?

OK it worked. I can send data to emulator and the phone now. Here is what the code looks like on the phone side:
private async void btnTest_Click(object sender,RoutedEventArgs e)
DatagramSocket dss = new DatagramSocket();
dss.MessageReceived += dss_MessageReceived;
dss.Control.DontFragment = true;
await dss.BindServiceNameAsync("49003"); // Service name == port. Why use string instead of int is a mystery
async void dss_MessageReceived(DatagramSocket sender, DatagramSocketMessageReceivedEventArgs args)
MessageDialog md = new MessageDialog("Received something");
await md.ShowAsync(); // <---- this call causes exception but I have data and I am happy
Desktop app sender code is here.
UdpClient c = new UdpClient();
c.Connect(new IPEndPoint(IPAddress.Parse("1.1.1.1"), 49003)); // real IP address here + port 49003
byte[] b = new byte[] { 1,2,3,4};
c.Send(b, b.Length);
In case of emulator I used the second address from the network settings (desktop adapter #1). For the phone I retrieved IP address from the router.

Why WRT54G ver 7 blocks all UDP broadcasts?

My WRT54G seems to be blocking all UDP broadcasts in the intranet side. Is there an option somewhere, which controls this behaviour, because I have not found one.
It does not matter, if I connect my laptop with a cable or by WLAN, no UDP broadcast packets from my server to the laptop go through.
If I connect to either one of my regular switches, UDP broadcast works perfectly.
Note that I'm not using the WAN port at all, so I would expect no filtering on the traffic.

Interesting!
For sake of argument, can you try using the broadcast address of 255.255.255.255 - this is a limited (local network only) broadcast.
Can you see the MAC (layer 2/ethernet) portion with your tool?
The MAC of the destination needs to be all FFs (all ones) for broadcasts.
I am wondering if something is happening at a lower level - like in how switching is implemented in the linksys. I wonder if a linksys switch (only) also does this.
NOTE - ICMP echo (PINGS) do go through my WRV54G to specific addresses and broacdcast the x.x.x.255 addresses.

UDP Broadcast Traffic from Cisco ASA

Hi,
I want to know that, like Cisco IOS Router, Does Cisco ASA pass the UDP Broadcast traffic e.g., TFTP etc...?
Any thoughts ???
BR,
Mubasher Sultan

Hi Mubasher,
Unlike the router the ASA does not forward any kind of broadcast packet (with the exemption of the DHCP broadcasts when DHCP Relay is enabled).
I understand that your DHCP server is providing here the IP address for your TFTP servers. I guess you are using DHCP option 150.
So if the DHCP server is on one interface and the client is on another you can configure DHCP Relay on your ASA.
http://www.cisco.com/en/US/products/ps6120/products_configuration_example09186a008075fcfb.shtml
In regards of the TFTP requests these will be normal unicast packets as Cadet said so just make sure that you have the proper ACLs and NAT rules for that.

Can you send a broadcast text msg to several people at one time

How do you send a broadcast text message to several people at one time?

As already provided, this is not supported with the iPhone's SMS client at the present time but as a workaround, you can do the same via email - SMS is just very limited email sending/receiving anyway.
This requires knowing the recipient's cell phone provider and the provider's email domain and entering this as an email address for a contact.
Here are some common domains.
Alltel = [email protected]
AT&T = [email protected]
Boost Mobile = [email protected]
Cingular (AT&T) = [email protected]
Einstein PCS = [email protected]
Sprint = [email protected]
T-Mobile = [email protected]
US Cellular = [email protected]
Verizon Wireless = [email protected]
Virgin Mobile = [email protected]
With the x's representing the recipient's cell phone number beginning with the area code. You can also use the same for MMS - sending a photo via the iPhone's email client which is received by the recipient as an MMS on their iPhone.

Using UDP broadcast instead of UDP multicast on a LAN (multicast not working on a major UK ISP router)

I've built an Android app using Cirrus that allows users on a LAN to chat in Morse code! - You can find it on the Android Market by searching for 'Morse Intercom'.
It works fine on my network, lots of other networks, but not on probably the most popular fast broadband fibre network in the UK
A friend of mine has let me piggyback on her network from this provider, and the problem appears to be that the UDP multicast packets RTMFP transmits just aren't being put on the wireless network. FYI the multicast address I use is IP 225.226.227.1 port 32112 .
This is probably fixable in the router, but 99.5% of users will never mess around with the router (and why should they), and if possible I would like to fix this in RTMFP.
Is it possible for me to ask RTMFP to not use UDP multicast, but instead to use UDB broadcast for discovering peers on the LAN ? The problematical router (and all others?) supports UDP broadcasting.
I tried setting 'groupspec.ipMulticastMemberUpdatesEnabled = false;' but this just stopped the app working on anything! What is the purpose of this option?
FYI:
To connect without using Cirrus server assistance I use: nc.connect("rtmfp:");
The complete function I use for setting up multicasting is:
private function setupGroup():void
// Create a new Group Specifier object
//trace("setUpGroup: groupSpec = new GroupSpecifier('myGroup/groupA')");
trace("setUpGroup: groupSpec = new GroupSpecifier('" + MY_UNIQUE_GROUP_NAME + "')");
var groupspec:GroupSpecifier = new GroupSpecifier(MY_UNIQUE_GROUP_NAME);
// Enable posting
trace("setUpGroup: groupspec.postingEnabled = true");
groupspec.postingEnabled = true;
// Specifies whether information about group membership can be exchanged on IP multicast sockets
trace("setUpGroup: groupspec.ipMulticastMemberUpdatesEnabled = true");
groupspec.ipMulticastMemberUpdatesEnabled = true;
// Causes the associated NetStream or NetGroup to join the specified IP multicast group and listen to the specified UDP port.
//trace("setUpGroup: groupspec.addIPMulticastAddress('225.225.0.1:30000')");
trace("setUpGroup: groupspec.addIPMulticastAddress('" + MY_MULTICAST_ADDRESS + "')");
groupspec.addIPMulticastAddress(MY_MULTICAST_ADDRESS);
// Constructs a NetGroup on the specified NetConnection object and joins it to the group specified by groupspec.
trace("setUpGroup: group = new NetGroup(nc,groupspec.groupspecWithAuthorizations())");
group = new NetGroup(nc,groupspec.groupspecWithAuthorizations());
// Set the NET_STATUS event listener
trace("setUpGroup: group.addEventListener(NetStatusEvent.NET_STATUS,netStatus)");
group.addEventListener(NetStatusEvent.NET_STATUS,netStatus);
In conclusion - On a LAN with up to 250 or so hosts, I can't see why RTMFP shouldn't be able to use UDP broadcasting as an alternative to UDP Multicasting. Can it, and if so how?
Graham

Here's more information...
When trying to connect with a 3rd party product, the connection request is sent out to my ISP's DNS server with details of the service ID. Of course it won't find anything there.
So then is tries to use NBNS (Netbios Naming Service) on 192.168.1.255, and still can't connect. Then comes back with a TNS error. i tried TNSPING on this address, and it doesn't find it. I have no clue where it gets this address from.
WHY WON'T IT JUST CONNECT TO THE HOST MACHINE AS DEFINED IN THE TNSNAMES FILE???
PLEASE HELP!!!!

Programs try to send ARP broadcast to 32.2.192.88

Hi,
I have a new Lenovo T400, Windows Vista operating system with all usual Lenovo/IBM-programs installed. The only program installed further is Norton Internet Security 2008.
My problem is, that my computer tries to send ARP-broadcasts to 32.2.192.88 and I dont know why. It starts even with no Ethernet-Connection (so no virus possible). That wouldnt be so bad, but I am in a very strikt network in which I get locked down, when my computer does this.
I also tried to track the broadcast with my firewall. Unfortunetly it thinks, that the broadcasts is started by any program with tries to connect to the internet, so I cant figure out wich program it really is. Locking down all System-Services on startup didnt solve the problem.
I guess, that this problem has something to do with installed Lenovo-Software, because I am the only Vista-User in my Network with this problem and Norton Internet Security 2008 worked fine on my old notebook.
I hope somebody here has any idea.
Greetings
Kratze

Are your clients pointed at an internal DNS server, or your ISPs ?
If it's not a DNS server within your LAN (192.168.0.0/24), or (for example) you point them at your router which itself is using your ISPs DNS servers, this will be seen as a disallowed relay attempt.
On one of your clients, fire up the Terminal (Applications/Utilities) and type in:
dig youontheweb.net
What IP comes back for the answer ?
As for Jeff's suggestion, please note:
whatmask 192.168.0.0/24
TCP/IP NETWORK INFORMATION
IP Entered = ..................: 192.168.0.0
CIDR = ........................: /24
Netmask = .....................: 255.255.255.0
Wildcard Bits = ...............: 0.0.0.255
Network Address = .............: 192.168.0.0
Broadcast Address = ...........: 192.168.0.255
Usable IP Addresses = .........: 254
First Usable IP Address = .....: 192.168.0.1
Last Usable IP Address = ......: 192.168.0.254
whatmask 192.168.0.0/32
TCP/IP NETWORK INFORMATION
IP Entered = ..................: 192.168.0.0
CIDR = ........................: /32
Netmask = .....................: 255.255.255.255
Wildcard Bits = ...............: 0.0.0.0
Network Address = .............: 192.168.0.0
Broadcast Address = ...........: 192.168.0.0
Usable IP Addresses = .........: 0
First Usable IP Address = .....: <none>
Last Usable IP Address = ......: <none>
It was necessary to change your subnetting/netmask from /32 to /24 as you can see. With a CIDR setting of 24 (subnet mask of 255.255.255.0) the available IP range is 192.168.0.0 - 192.168.0.255.
See http://www.postfix.org/basic.html#mynetworks

LwIP + FreeRTOS + Zynq zc702 - erroneous data byte offset when sending UDP from Zynq

Hello,
I'm sending UDP successfully from my zc702 board to a PC. However if I send UDP datagrams larger than the Ethernet MTU, thus requiring lwIP to fragment my UDP datagram into multiple Ethernet frames, I get a mysterious data offset in received data seen in Wireshark. The offset is either 8,16,24,32,40,48, or 56 bytes (8 byte increments). The offset changes whenver I change code - even unrelated code in other FreeRTOS threads, but the offset is always one of those numbers. For now as a hack I'm adding the required offset to the data payload pointer I pass to the lwip_sendto() function, which works until I change any code, then I have to use a different offset.
I've increased stack and heap size but no effect. Again, it only happens when I send > Ethernet MTU (around 1500) bytes.
Has anyone seen this behaviour?
Thanks,
Randy

This reply is coming extremely late, so this is for the benefit of anyone else who is having a problem with IP fragmentation. I was able to fix this by modifying the pbuf.c file in the lwip140_v1_06_a source code. Just remove the call to the LWIP_MEM_ALIGN macro on line 379 -- delete the call but leave the rest of the line alone. It was starting each new fragment at a 64-byte aligned location. This caused the second fragment to start at the wrong location which then caused all of the other fragments to start at the wrong location. I think what they meant to do was to align the first fragment but leave the rest alone.

Does a UDP-broadcast limit datagram size?

I have posted this question in the Java Forum - Java Programming but there they recommended to post the question here.
I want to broadcast a datagram to all devices in a network. I have to use UDP-Communication. I'm using the following code for the sender:
public class Source {
public static void main(String[] args) throws IOException {
          Thread t = new Thread() {
               public void run() {
                    DatagramSocket socket = null;
                    try {
                         socket = new DatagramSocket();
                    catch (SocketException e) {
                         e.printStackTrace();
                    DatagramPacket paket = null;
                    try {
                         paket = new DatagramPacket(new byte[1472], 1472, InetAddress
                                   .getByName("255.255.255.255"), 3333);
                    catch (UnknownHostException e) {
                         e.printStackTrace();
                    try {
                         socket.send(paket);
                    catch (IOException e) {
                         e.printStackTrace();
          t.start();
}With the payload size of 1472 or lower everything works fine, the receiver receives the datagram. But if I'm increasing the payload size to 1473 or higher it seems that the sender never sends the datagram. The receiver receives nothing. No Exception is thrown.
The strange thing is, when I send a datagram which is bigger than 1472 bytes to an existing InetAddress and not to the broadcast-address everything works fine.
It seems to me that if a broadcast address is given the IP fragmentation fails and the conclusion is that the datagram doesn't fit the MTU and is never forwarded. But this is only an assumption.
I have a workaround yet so I'm not interested in a practical solution. Within my final year project I have to illustrate and explain it, so I'm looking only for an explanation.
Could anyone explain this phenomenon or give me a reference where I can find the explanation for it?
I'm using:
Windows XP Pro SVP2 with jdk1.5.0_01
Thanks a lot!

I may have found the problem. If you capture packets
with ethereal (google for it) while sending a
fragmented broadcast datagram you'll see these in the
IP header of every fragment:
Header checksum: 0xc4a0 (incorrect, should be
0xbf86)If ethereal is right Windows messes up IP header
checksum calculation when fragmenting broadcasts. The
fragments do get sent but they are broken and the
receiver will drop them. Non-broadcasts have correct
checksums.
Windows bug. Complain to Bill :-)Yeah, good luck, see below.
If you have non-Windows machines around you could try
Unix->Windows and Windows->Unix. The bug could be in
the Berkeley IP stack too (AFAIK Windows uses a
version of it).Nope. Windows uses an implementation by MS of the WINSOCK specification. Neither WINSOCK nor MS's implementation has anything to do with Berkeley code.
The WINSOCK spec. doesn't map BSD sockets perfectly, and MS doesn't implement the RFC's perfectly either.

EEM send UDP broadcast

Similar Messages

Maybe you are looking for