Jump to content

mygoditsfullofstars

Resident
  • Posts

    71
  • Joined

  • Last visited

Everything posted by mygoditsfullofstars

  1. So you know what the overall cost would be for every person who wanted to have it on their parcel/region plus all the traffic in and out of the region that connected and listened to the stream? Unless you are LL's accountant and can see the books, you cant sit there and say they are rolling in money and can afford it, none of us are privy to LL's financial position.... Why should LL pay for it? Lets assume for arguments sake LL decided to do this, do you really think that expense wouldn't trickle down the pipe to somewhere else in the form of higher fees for land, currency transactions etc?
  2. Assuming is it a specific network carrier that's at fault, traceroutes (if enough of them are supplied), might help in identifying which one it might be (ie: comparing a bunch of traceroutes provided by people having problems against users in similar geographic locations who are not having problems). Whether anything can be done about a problematic intermediate network carrier is another matter entirely, depends on where along the path they are, if its something within Amazon or one of their upstreams its likely Amazon can get it resolved. If its a carrier beyond that boundary then all I can say is "good luck" since it would require sending an email to the NOC of that carrier (who most of the time don't respond to emails (based on my past experiences when in such a situation)). Its also possible this problem will just go away on its own if its a network carrier who is aware of the problem and is currently working to resolve it. Anyway I might be completely barking up the wrong tree with it being a specific intermediate network carrier being the issue, but is a plausible theory.
  3. UDP packet loss also wouldn't explain login issues (where some people are having to try 20 or more times before they can log in) since all of that most certainly is TCP (during the initial authentication stage).
  4. Traceroute, while handy in some scenarios shouldn't be considered a definitive guide as to the health of a network path. By default, traceroute uses ICMP. Many layer 3 devices (routers, firewalls) drop ICMP traffic (or can even de-prioritize it under certain network conditions). UDP is session-less, and UDP data not being returned could mean it is being lost literally anywhere along the network path, it doesn't necessarily indicate that the simulator or server itself is hosed and is not sending any traffic back.
  5. It has also been hit and miss for some people rather than constant - could it just be pure luck that the other machine worked when tested (ie: is it consistently able to log in and out and tp around with no issues?)
  6. It might be interesting to know whether or not if any of the affected people are using VPN's (some AV software like Norton, and I am sure there are others also includes a VPN service that runs in the background, often without the end users knowledge its even rerouting their network traffic).
  7. I am unaffected too. Using Linux here. Unsure if there is any pattern to operating system/os version. Looking at the data in this thread so far, it doesn't appear to be Country or ISP specific. It could be a problem with an intermediate network carrier somewhere along the network path into Amazon that's having issues and those who are unlucky are being routed via that carrier.. Anyway pure speculation on my part - it will be interesting to see what it actually is.
  8. If you are having the same symptoms as others in this thread, it is not Firestorm related (please read through the thread, you will find it is effecting other viewers too)
  9. Hello, that wont be the reason The dullahan binary shipped with official firestorm builds is safe, sometimes, certain antivirus software flags it as suspicious incorrectly (these are known as false positives). Cloudflare blocking can happen for a variety of reasons, but I wont go into them here, it will turn into a trainwreck of a thread if I attempt it (just like the last thread did).
  10. Its hard to stay inspired when all I face is aggression, baseless accusations etc. I am actually someone that's in a position to be helpful with a wide range of issues. I've offered an avenue for people to reach out for contact if they are facing Cloudflare issues but I just get shat on for even offering.
  11. Wow hostility much? I am not even remotely interested in your computer and was not offering to make any changes to it or suggesting that you do. I was offering to look at the Cloudflare logs on my end to see what might have caused the block, but carry on being hostile Have a nice day.
  12. If switching web browsers fixed it, then you can probably rule out your IP address as the issue. More than likely your other browser has some grudge with Javascript or certain types of Javascript. If you have the Ray ID of the block page I can confirm what it was, but do this in DM please if you want me to have a look, I don't want another round of what went on in the other thread here.
  13. Like I said, most web browsers warn users about enabling strict security settings, there are some pitfalls to doing it, and its not just our domains that users who enable strict security controls will run into issues with. To expect every network/site operator to just bow and cater to every need is ridiculous and unrealistic. There are some who even go as far as to completely disable Javascript on their machines and expect everyone to bow to their needs and not have anything that requires the use of javascript. It never ends, cant please everyone... In most cases, those who are "locked out" as you put it can work around it easily in most cases, but see if I elaborate on that, you will just use that to start another argument..
  14. I wasn't going to say anything further on this, since it is clear that there are certain people who will never see eye to eye with me on this and are just here for the argument and will just keep disagreeing because they can (what a waste of energy). Most internet web browsers have security/privacy settings which can be adjusted, and these can be set to various levels, however, there is often a warning that is displayed in many web browsers when turning the privacy settings up to strict or high that the change may cause some websites not to work etc - there is a reason the software is informing a person of this when they elect to enable stricter security settings (so that they are aware that there could be some pitfalls to making that move and to expect some problems if they proceed). I am not against anyone who wishes to use strict privacy settings in their web browser, or install plugins that attempt to enhance security, in fact I give them a pat on the back for trying to protect themselves - whats not fair however is to then attack site operators who are in turn just trying to do the same thing themselves to help protect their infrastructure against threats. Site operators have the right to try and protect their infrastructure too, just as much as end users have the right to ramp up the security on their PC to fort Knox levels if they wish. Sure I could make compromises on infrastructure security to allow everything through, but why should I?? The users who are hardening security on their computers are certainly not willing to make compromises in that area... Sometimes you cant always have your cake and eat it too. The self entitlement of some people is astounding.. Life is too short for squabbling over such things, lets just agree to disagree and move on.
  15. Not taking the bait - as I said, you are not privy to the threats that the infrastructure faces on a day to day basis. We're done here.
  16. One more thing. Cloudflare themselves also maintain their own blocklists to help protect site operators, certain network carriers or IP address ranges could also be the subject of temporary blacklisting if they have been involved in DOS attacks and the like, those usually are temporary though and clear after some time.
  17. I think this is an exaggeration. If you are trying to access the domains and are not using something like TOR or a VPN (or some shady http proxy) you should be fine (unless your system is having problems with basic javascript (more on that below)). People have a good reason for using Cloudflare to protect their infrastructure from an internet that is full of hostile threats. I don't expect you to understand this since you are not in a position where you are privy to the sorts of threats that infrastructure faces on a day to day basis, I am privy to it. If you are getting blocked, send me the "Ray ID" at the bottom of the Cloudflare page and I will look into why the session was blocked. There are a couple of reasons why *some* and I emphasize "some" people could encounter a problem (no its not the whole world, people tend to inflate/exaggerate the severity of things often (I'm also aware that many have sockpuppet accounts on these forums too)) - Cloudflare will try and block scripts and bots, it will do this by having a visitors web browser run some small javascript challenges behind the scenes - if the visitors web browser is unable to respond to basic javascript, then the session will probably not be allowed. This can be caused by a few things: Misconfigured security software interfering and preventing Cloudflares Javascript from running Browser privacy settings set too strictly. Some third party browser plugins that claim to "improve privacy" that are interfering.
  18. Yes On ubuntu (and probably debian and its clones) that library is part of the libglu1-mesa package. On Fedora it likely has another name, try something like dnf provides libGLU.so.1 It should tell you what package you need to install.
  19. This is a great example of how google can help spread FUD and information that is just plain wrong. HTTP has no relevance to routing protocols like BGP. For info on what BGP actually is https://www.techtarget.com/searchnetworking/definition/BGP-Border-Gateway-Protocol As for DNS hijacking, more FUD, no relevance to the HTTP protocol. DNS could in theory be hijacked if something were to happen to the hosts file on your PC or something were to change your PC's network configuration to use a set of rogue nameservers. I fail to see the relevance to the HTTP protocol. People have made far too big a deal out of HTTPS in recent years and created all sorts of FUD around it. My 2 cents worth.
  20. They have to legally. They wouldn't have been able to remain operating for so many years if they didnt.
  21. @Drakeo Bare metal means to run it natively on hardware. No virtualization. I am not going to argue with you anymore because I am tired of you being condescending and hostile (and making ill informed assumptions), the point being is that it was broken and trying to use EGL which is not the preferred method on Linux and that was the underlying reason for the log spammage. CEF creates its own log file (cef_log.txt) and also echos that junk out to it, which is the file that was getting massive on the systems of numerous people (so, no, the CEF spam is not just going to STDOUT). FYI -- I have a programming background in x86 assembler and C and other languages up my sleeve. Fact is, you make DUMB assumptions. Another fun fact I am a Linux (and Unix) sysadmin with over 20 years commercial experience in the field with Devops up my sleeve. So before you go calling me a windows person and me not knowing what the printf() function is ponder the above for the moment. I've not used windows in many years. I am done here.
  22. This should be now fixed in https://vcs.firestormviewer.org/phoenix-firestorm/changeset/abd5f7a8993d777fa19e1c2fcd70d2af038e3730 Looks good for me now:
×
×
  • Create New...