It depends. If the service relates in any way to IRC, probably not. However, if you are developing an open source application that needs to listen on a TCP/UDP port, we may allow it. If your service falls into this category, send an email to us describing your project in full detail before starting any listener. If we feel that the service you want to run meets with our security requirements, we will notify you by email.

p02: Add information on IBM enhancements to security server to permit large number of DCE principals to be created. See similar questions...

First have you considered the advantages of using all protocol sequences? RPCs work the same either way. DCE's implementation provides the same security and reliability over all communication protocols. In most cases the performance is about the same as well. For some applications and some platforms, there may be reasons to prefer one protocol over another. For instance, if your platform has a poor implementation of UDP, that could be a reason to prefer TCP, or vice-versa. See similar questions...

Initially, netstat may be useful to determine which ports are in use: $ netstat -a |grep .service|port Then, you can use the freely available utility lsof to determine which process is using a give port, for instance when you get the error Address already in use. $ lsof -i protocol:service|port E.g.: $ lsof -i UDP:1812 See the lsof man page for full details. See similar questions...

Most Schemes come with built-in functions for accessing sockets. Some allow the definition of custom port types, thus enabling the use of standard Scheme port functions on sockets and many other objects. See similar questions...

By entering FastOutUdpSport, FastOutUdpDport, FastOutTcpSport and FastOutTcpDport plus a corresponding source port number (Sport) or destination port number (Dport) into the [cts] section of the CFOS.INI file, you can prioritize UDP or TCP packets with TX CTS. Please note that each entry can have multiple values, separated by spaces or commas, like for instance: See similar questions...

UDP is good for sending messages from one system to another when the order isn't important and you don't need all of the messages to get to the other machine. This is why I've only used UDP once to write the example code for the faq. Usually TCP is a better solution. It saves you having to write code to ensure that messages make it to the desired destination, or to ensure the message ordering. See similar questions...

VaxVoice SDKs use UDP protocol for voice streaming. Because, UDP protocol is a preferred protocol to send voice data over the IP based Network. See similar questions...

TCP (Transmission Control Protocol) and UDP (User Datagram Protocol) are both protocols that use IP. Whereas IP allows two computers to talk to each other across the Internet, TCP and UDP allow individual applications (also known as "services") on those computers to talk to each other. In the same way that a telephone number or physical mail box might be associated with more than one person, a computer might have multiple applications (e.g. See similar questions...

port 507) to push web site updates from an internal developement web server to production web servers on a secured firewall segment Firewall configuration: Administrative services like exec, login and shell should be replaced with secure alternatives (such as SSH). Utilities like syslog should be encapsulated in a VPN if you need to move the data over the Internet. Firewall configuration: Unix print services. See similar questions...

There are a number of reasons. The first is that script-kiddies aren't too bright. If they only scripts available use port 7, then that is all they can use. Secondly, the service has to respond to broadcast requests. Therefore, you cannot use TCP (which will only respond to directed queries). Many other UDP services only respond to directed queries. Finally, when fraggle was first developed, many firewalls allowed Echos to pass through (because they were used for performance monitoring). See similar questions...

But defining a new port may not help you to traverse NAT. If you leave the default configuration, requests and response will *probably* traverse most NAT. See similar questions...

Each application running over TCP or UDP distinguishes itself from other applications using the service by reserving and using a 16-bit port number. Destination and source port numbers are placed in the UDP and TCP headers by the originator of the packet before it is given to IP, and the destination port number allows the packet to be delivered to the intended recipient at the destination system. See similar questions...

A3) There are at least four different kinds of games as far as networking is concerned: Turn-based games, Real Time Strategy games, Role Playing Games, and Action Games. Briefly, if you're turn-based, you should go with TCP because it's simpler, unless you need peer-to-peer NAT punch-through. For RTS games, you're usually best off using TCP, although UDP can make sense in extreme cases. See similar questions...

A5) UDP uses slightly smaller headers per packet than TCP, which may give you marginally better throughput on narrow channels (such as modems). UDP will also deliver any received packet as it is received, without waiting to re-order packets, so if latency is more important than correctness of the underlying channel, then UDP will introduce less jitter in your game, and gameplay will be smoother. See similar questions...

To scan all possible ports would involve scanning over 130,000 ports. While that would be thorough, there are a number of problems associated with doing this: Scanning can take a long time. To scan all 64K TCP ports would take our scanner several hours. We do offer a full 64K TCP port scan as part of our advanced audit. UDP ports cannot be scanned reliably. The problem with UDP ports is that they don't respond when the port is open. See similar questions...

Actually, nothing! While everyday experience and Hollywood movies make people think of sounds when they see the words "radio telescope," radio astronomers do not actually listen to noises. First, sound and radio waves are different phenomena. Sound consists of pressure variations in matter, such as air or water. Sound will not travel through a vacuum. Radio waves, like visible light, infrared, ultraviolet, X-rays and gamma rays, are electromagnetic waves that do travel through a vacuum. See similar questions...

Better is relative. Technically UDP is faster as it incorporates less overhead such as the back and forth signaling (the ACK and NAK's etc) to establish and maintain the connection. The only downside to UDP, sometimes jokingly called the Unreliable Data Protocol, is the remote possibility of a lost packet. With the emergence of VOIP (which uses UDP) and the subsequent improvements in Internet infrastructure, the probability of UDP packet delivery has improved dramatically. See similar questions...

Yes. The PicoWeb server is not limited to use only by Web browsers. The supplied PicoWeb firmware also supports custom programming using UDP and TCP. With the latest release of the PicoWeb firmware (v2.xx), application code can initiate short outbound TCP/IP sessions with remote host computers by using special firmware routines. Normally, the PicoWeb is restricted to servicing inbound TCP/IP sessions only. UDP-based communication is also possible using the PicoWeb firmware. Yes. See similar questions...