RE: UDP message not recevied at port 8100 with Scientific Linux 6.3
Hi, The Version of the OS that I use is 6.3 The version of the libtirpc package that I have is libtirpc-0.2.1-5.el6.x86_64 The firewall setting that I have is empty [ checked with iptables –L command is as below] Chain INPUT (policy ACCEPT) target prot opt source destination Chain FORWARD (policy ACCEPT) target prot opt source destination Chain OUTPUT (policy ACCEPT) target prot opt source destination Is there anything else that has to be looked in ? Thanks, Arul From: Paul Robert Marino [mailto:prmari...@gmail.com] Sent: Monday, August 19, 2013 2:32 AM To: Edison, Arul (GE Healthcare); Scientific Linux; S, Akshata (GE Healthcare); Rao, Keshava N (GE Healthcare) Subject: Re: UDP message not recevied at port 8100 with Scientific Linux 6.3 -- Sent from my HP Pre3 On Aug 16, 2013 14:36, Konstantin Olchanski olcha...@triumf.camailto:olcha...@triumf.ca wrote: On Fri, Aug 16, 2013 at 11:24:36AM -0700, Konstantin Olchanski wrote: On Fri, Aug 16, 2013 at 02:01:20PM +, Edison, Arul (GE Healthcare) wrote: Hi all, The application that I run on Scientific Linux 6.3 is to receive the UDP message at port 8100. However I found that port 8100 is used by xprint-server Is there a way to disable the xprint-server ? You can use lsof to find out who is consuming UDP packets sent to port 8100. FYI in most cases netstat is a lot easier to get this info example netstat -lunp And add a -t if you want to see TCP as well. (Also check that your packets are not rejected by your own firewall, iptables -L -v). Also SL 6.3 shipped with a defective libtirpc which discards UDP broadcast packets. The bug makes NIS not work. May bite you, too. SL 6.2 or 6.1 was okey, I think, SL 6.4 not sure. I have posted this bug on this mailing list and on RH bugzilla, it is fixed in errata packages. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
RE: UDP message not recevied at port 8100 with Scientific Linux 6.3
Hi Konstantin Olchanski, Can you provide some more info on how to disable / configure portmap? Below is the rpcbind rpm that is in the system rpcbind-0.2.0-9.el6.x86_64 Thanks, Arul -Original Message- From: Konstantin Olchanski [mailto:olcha...@triumf.ca] Sent: Friday, August 16, 2013 11:55 PM To: Edison, Arul (GE Healthcare) Cc: Scientific Linux; S, Akshata (GE Healthcare); Rao, Keshava N (GE Healthcare) Subject: Re: UDP message not recevied at port 8100 with Scientific Linux 6.3 On Fri, Aug 16, 2013 at 02:01:20PM +, Edison, Arul (GE Healthcare) wrote: Hi all, The application that I run on Scientific Linux 6.3 is to receive the UDP message at port 8100. However I found that port 8100 is used by xprint-server Is there a way to disable the xprint-server? You can use lsof to find out who is consuming UDP packets sent to port 8100. Note that UDP port collisions is a problem because portmap (rpcbind) assigns UDP ports to various daemons kind of randomly and it will eventually collide with any UDP port you decide to chose. One way to avoid this is by using portmap yourself in your application. (Also check that your packets are not rejected by your own firewall, iptables -L -v). -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: UDP message not recevied at port 8100 with Scientific Linux 6.3
-- Sent from my HP Pre3On Aug 16, 2013 14:36, Konstantin Olchanski olcha...@triumf.ca wrote: On Fri, Aug 16, 2013 at 11:24:36AM -0700, Konstantin Olchanski wrote: On Fri, Aug 16, 2013 at 02:01:20PM +, Edison, Arul (GE Healthcare) wrote: Hi all, The application that I run on Scientific Linux 6.3 is to receive the UDP message at port 8100. However I found that port 8100 is used by xprint-server Is there a way to disable the xprint-server? You can use "lsof" to find out who is consuming UDP packets sent to port 8100. FYI in most cases netstat is a lot easier to get this info examplenetstat -lunpAnd add a -t if you want to see TCP as well. (Also check that your packets are not rejected by your own firewall, "iptables -L -v"). Also SL 6.3 shipped with a defective libtirpc which discards UDP broadcast packets. The bug makes NIS not work. May bite you, too. SL 6.2 or 6.1 was okey, I think, SL 6.4 not sure. I have posted this bug on this mailing list and on RH bugzilla, it is fixed in errata packages. -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
Re: UDP message not recevied at port 8100 with Scientific Linux 6.3
Check: netstat -tulpn | grep 8100 if another process is blocking the port and iptables -L -v -n to check if the local firewall may block the request. Regards Thomas 2013/8/16 Edison, Arul (GE Healthcare) aruljeyananth.jamesedi...@ge.com Hi all, The application that I run on Scientific Linux 6.3 is to receive the UDP message at port 8100. However I found that port 8100 is used by xprint-server Is there a way to disable the xprint-server? I checked and xprint-serveris not a service . also it is not a application running on my PC ** ** If I invoke the command *cat /etc/services | grep 8100 , below is the out displayed. It means port 8100 is used by *xprint-server. xprint-server 8100/tcp# Xprint Server xprint-server 8100/udp# Xprint Server ** ** ** ** Regards, Arul ** ** -- Linux ... enjoy the ride!
Re: UDP message not recevied at port 8100 with Scientific Linux 6.3
On Fri, Aug 16, 2013 at 02:01:20PM +, Edison, Arul (GE Healthcare) wrote: Hi all, The application that I run on Scientific Linux 6.3 is to receive the UDP message at port 8100. However I found that port 8100 is used by xprint-server Is there a way to disable the xprint-server? You can use lsof to find out who is consuming UDP packets sent to port 8100. Note that UDP port collisions is a problem because portmap (rpcbind) assigns UDP ports to various daemons kind of randomly and it will eventually collide with any UDP port you decide to chose. One way to avoid this is by using portmap yourself in your application. (Also check that your packets are not rejected by your own firewall, iptables -L -v). -- Konstantin Olchanski Data Acquisition Systems: The Bytes Must Flow! Email: olchansk-at-triumf-dot-ca Snail mail: 4004 Wesbrook Mall, TRIUMF, Vancouver, B.C., V6T 2A3, Canada
