5050 Yahoo Messenger / MesosYahoo Messenger; also Apache Mesos master.
Legacy IM or cluster scheduler.
| Transport | Status | Meaning |
|---|---|---|
| TCP | Unofficial | Not assigned by IANA, but standardized, specified, or widely used on this port. |
| UDP | — | Not applicable for this transport. |
| SCTP | — | Not applicable for this transport. |
| DCCP | — | Not applicable for this transport. |
Registered (1024–49151). Assigned by IANA on request; usable without elevated privileges on most systems.
Browse all ports →
Copy-ready inbound rules for the active transports. Replace every <source> placeholder with the specific host, subnet, or CIDR that should reach this port.
sudo ufw allow proto tcp from <source> to any port 5050Allow TCP 5050 (Yahoo Messenger / Mesos). Replace <source> with the network/host that should reach it.
sudo firewall-cmd --permanent --add-rich-rule='rule family="ipv4" source address="<source>" port port="5050" protocol="tcp" accept'Allow TCP 5050 (Yahoo Messenger / Mesos) from <source>. Run 'firewall-cmd --reload' afterwards.
nft add rule inet filter input ip saddr <source> tcp dport 5050 acceptAllow TCP 5050 (Yahoo Messenger / Mesos). Assumes table 'inet filter' with an 'input' chain.
sudo iptables -A INPUT -p tcp -s <source> --dport 5050 -j ACCEPTAllow TCP 5050 (Yahoo Messenger / Mesos). Persist with iptables-save/netfilter-persistent.
az network nsg rule create -g <resource-group> --nsg-name <nsg> -n Allow-yahoomessengermesos-5050 --priority 1000 --access Allow --direction Inbound --protocol TCP --source-address-prefixes <source> --destination-port-ranges 5050Inbound rule for 5050 (Yahoo Messenger / Mesos). Set <source> to a CIDR; lower priority number = higher precedence.
aws ec2 authorize-security-group-ingress --group-id <sg-id> --ip-permissions IpProtocol=tcp,FromPort=5050,ToPort=5050,IpRanges="[{CidrIp=<source-cidr>}]"Inbound TCP 5050 (Yahoo Messenger / Mesos). Replace <source-cidr> (e.g. 10.0.0.0/16).
gcloud compute firewall-rules create allow-yahoomessengermesos-5050 --direction=INGRESS --action=ALLOW --rules=tcp:5050 --source-ranges=<source-cidr> --network=<network>Ingress rule for 5050 (Yahoo Messenger / Mesos). Scope with --source-ranges and optionally --target-tags.
netsh advfirewall firewall add rule name="Allow Yahoo Messenger / Mesos 5050/TCP" dir=in action=allow protocol=TCP localport=5050 remoteip=<source>Inbound TCP 5050 (Yahoo Messenger / Mesos). Set remoteip to a host/subnet; 'any' is discouraged.
New-NetFirewallRule -DisplayName "Allow Yahoo Messenger / Mesos 5050/TCP" -Direction Inbound -Action Allow -Protocol TCP -LocalPort 5050 -RemoteAddress <source>Inbound TCP 5050 (Yahoo Messenger / Mesos). Replace <source> with a host or subnet.
Rules are generated only for transports marked active for this port. They default to an inbound allow with an explicit source placeholder — never any. Review direction, scope, and rule precedence before applying in production.