Jump to content

Bananimal

Members
  • Content Count

    12
  • Joined

  • Last visited

Community Reputation

3 Neutral

About Bananimal

  • Rank
    Member

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

  1. Thanks so much for the detailed response. I spent all day Sunday past trying to figure this one out. Your explanation is superb and is sure to help others.
  2. Alright. Doing some research on what ports ISPs may block. Coming up with a few things. Of interest for this particular ISP is this is port 67 - UDP. I stand corrected and humbled to a degree. Blocked Internet Ports List Find out which ports are blocked by Xfinity and Comcast services, and why. Ports on the internet are like virtual passageways where data can travel. All information on the internet passes through ports to get to and from computers and servers. When a certain port is known to cause vulnerability to the security and privacy of your information, Xfinity blocks it to protect you. Find the Reasons for Blocking Listed Below Port Transport Protocol Direction Downstream/ Upstream to CPE Reason for Block IP Version 0 TCP N/A Downstream Port 0 is a reserved port, which means it should not be used by applications. Network abuse has prompted the need to block this port. IPv4/IPv6 25 TCP SMTP Both Port 25 is unsecured, and Botnet spammers can use it to send spam. This does not affect Xfinity Connect usage. We recommend learning more about configuring your email settings to Comcast email to use port 587. IPv4/IPv6 67 UDP BOOTP, DHCP Downstream UDP Port 67, which is used to obtain dynamic Internet Protocol (IP) address information from our dynamic host configuration protocol (DHCP) server, is vulnerable to malicious hacks. IPv4 135-139 TCP/UDP NetBios Both NetBios services allow file sharing over networks. When improperly configured, ports 135-139 can expose critical system files or give full file system access (run, delete, copy) to any malicious intruder connected to the network. IPv4/IPv6 161 UDP SNMP Both SNMP is vulnerable to reflected amplification distributed denial of service (DDoS) attacks. IPv4/IPv6 445 TCP MS-DS, SMB Both Port 445 is vulnerable to attacks, exploits and malware such as the Sasser and Nimda worms. IPv4/IPv6 520 UDP RIP Both Port 520 is vulnerable to malicious route updates, which provides several attack possibilities. IPv4 547 UDP DHCPv6 Downstream UDP Port 547, which is used to obtain dynamic Internet Protocol (IP) address information from our dynamic host configuration protocol (DHCP) server, is vulnerable to malicious hacks. IPv6 1080 TCP SOCKS Downstream Port 1080 is vulnerable to, among others, viruses, worms and DoS attacks. IPv4/IPv6 1900 UDP SSDP Both Port 1900 is vulnerable to DoS attacks. IPv4/IPv6 Hmmmm. I'm looking like a dufus about right now I presume. Worth checking with your ISP. Many block some ports but it is usually incoming traffic to prevent you from hosting servers and business services on a residential service. Outgoing traffic is usually allowed for all ports. In the event they do block se, and it is usually things like SMTP and VPN's. I did hear of, but no confirmation, one ISP planning to block all traffic other than o, going , thinking they could prevent allot of malware from using uncommon ports 25, 53, 80, 443.
  3. Not bull. I know better. Block your port 80 and get back to me. Your internet would be partially functional at best only leaving SSL open on 443. You'll also be lucky if you can get back into your router interface on your private LAN once you turn off port 80 as typically local or Intranet runs on HTTP mostly. There's generally no reason to encrypt internal communications. Depending on the router, you may not be able to turn off port 80 for this reason. With all due respect, sounds like to me that you're just rattling off networking buzzwords to sound like you know what you apparently don't. HTTP is still very much prevalent on the net and your internal network. Not everything rides on 443. I also don't believe you know how NAT works. NAT is used primarily on-prem to obfuscate internal IP address as outbound TCP packets leave your perimeter. In this case, your home network. It blocks nothing. It's a translation that takes place. Network Address Translation or NAT. That's to say, if there is any NAT going on, it's your router or firewall doing it. There is no benefit that I am aware of for an ISP to NAT your TCP transmissions. What do they care? The security of your private network is not their concern. Being "behind a NAT" as you say, means nothing. You cannot be behind a NAT. NAT is a configuration setting, not a firewall. Furthermore, if NAT is turned on, you most certainly will be able to send and receive TCP packets in a transparent fashion. You as a user would never know the difference. NAT in a Nutshell TCP packet moves outbound from your NIC to your router. If NAT is enabled in your router's config, each packet gets wrapped with new header info that includes a new IP address that is entirely different than what was originally included in the packet header from your NIC. All packets from all of your devices on your private network (behind your router) are assigned the same IP on the public side outbound. Obfuscation. All NAT'ed packets leave your router with the same, single IP, and are consumed by the destination devices/hosts in the cloud. These devices/hosts don't give two Willies what the IP address is in the header. The destination device/host sends return packets back to the NAT'ed IP address, which is your router. You router unwraps the IP header from the packet and knows which internal IPs on your network to route the packets to. This keeps devices, hackers, and other bad actors from targeting internal IP addresses on your private network. For this reason, disabling NAT and broadcasting your internal IP schema to the world is a risky endeavor. I have a feeling next you'll be telling me that a Class C IP is routeable over SSL. HTTP = port 80 HTTPS = port 443 TCP = protocol The majority of HTTP traffic uses HTTPS? Not correct. HTTPS and HTTP traffic use TCP as do other ports e.g., IL-2. Don't take offense to this, but if you're foolish enough to disable NAT on your router thinking it will possibly solve your network connection issues in IL-2, you're opening yourself up to man-in-the-middle attacks. Bad actors would be able to target specific IPs on the private side of your router because you're exposing your internal IP schema to hackers should they intercept your communications, which is very much a reality these days. Specifically over HTTP or other transmissions in the clear like SMTP and FTP.. Now the reason I chimed in here is that most of the posts in this thread are significantly off the mark. My suggestion is to enable NAT immediately for security reasons, forward port 28000 TCP and UDP separately in your router config. Then forward port 28100 using the "Both" option for both TCP and UDP if your router has the "both" option. If that doesn't work, try setting TCP and UDP for port 28100 separately like you did for port 28000. NAT is not your problem. Here's a screen of my router config:
  4. ISPs don't block ports. They will block attempted port scanning. The ports are local to your router. Also, if port 80 (HTTP) was blocked, you'd not be able to surf the Internet.
  5. Ehhhhh. through my trial and error, I have seen it named "Lead entity" before. Problem was, aircraft 2 assumed that entity for whatever reason. When I link the wingman, they automatically assume a "Plane entity" name. You can't delete or modify it either. If you break the link, then it returns to a blank field. So check this out. Here's my grouped flight tree. And the bottom image shows what the groups look like in the session lobby. It makes zero sense to me. I suspect because the "Lead" entity is missing. And I mis-spoke earlier, if I do not group the aircraft, all four are grouped correctly in the lobby with the exception that the lead aircraft is in slot four. The second image below is what happens when I group the objects and name them Sochie Airfield.
  6. See images below. I tested this and it puts the lead aircraft in slot 4.
  7. Thanks Sketch, You're findings are interesting. I am able to duplicate what you have outlined here, but for the life of me, I cannot seem to get the lead aircraft to assume a Lead Entity name in the advanced properties for the lead aircraft. Even though the linked aircraft properly show the Flight Lead target ID correctly when linked to it and I can see the attached wingman in the Change formation dialog of the Lead aircraft. As far as the manual, That may be where I got it from. I truly don't recall. I'll see if I get hunt down an up to date copy.
  8. Well, I thought I had it figured out. As now, the flight is split into two groups. 6.5 hours and still can't get a few planes on the map in one group.
  9. I figured it out. I was wanting to load USAAF P-39s and set the country to neutral. No go. Have to select Russian or German. I have to wonder why neutral is even in the list. That got the aircraft to show up in the mission lobby. However, now the issue is that they are two separate aircraft and not grouped even though I target linked them and then grouped them. What really makes no sense is the advanced properties shows the wingman, plane #1 in the formation as a Flight Lead Entity in the name field. And then plane #0 in the formation, which is the lead, shows nothing in the name field where it should be a Flight Lead Entity. Makes no sense. I even unlinked everything and created a target link from the lead plane to the wingman plane and it calls the wingman plane the lead entity. I'm simply wanting to put all aircraft types throughout the map for a coop free flight mission where we can just hop into the mission and pick what we want to fly while learning these aircraft. I have everything 1C has for sale. I'd like to use it instead of using someone else's mission with adversaries. Sometimes, our group just wants to hop in the sim and do pattern work, formation work, and comms work without the distraction of being shot down. Any help would be greatly appreciated. See mission below. Free Flight Mission.zip Figured it out. I have to use the callsign stork for all aircraft and number them 0-3. I also wanted to say that I wasn't directing my frustration toward you guys that took it upon yourselves to document the editor further. 1C added the coop feature to the ME, they need to update they manual with more specific information related to it. Thanks for your efforts. It's greatly appreciated.
  10. I am pulling my hair out here as well. I've done all of the above and when I load the coop mission, I get no aircraft groups to select in the lobby. The mission I have setup is simple. Two P-39s at Sochi Airfield. The first is named Flight Lead and the second is Wingman One. I then target linked both aircraft and then grouped them together naming the group P-39L1 (Sochi Airfield). Could the parenthesis in the group name be causing this issue? I guess I'll try that. BTW, I've read the manuals, I've scoured the forums, this is the first post where someone mentioned not using integers when naming the aircraft entity. Would be good to include these types of Gotchas in the manuals. Otherwise, folks like me follow the instructions and get nowhere for 4 hours. It's frustrating, and I'd be willing to bet that's why there aren't a lot of mission builders in this community.
×
×
  • Create New...