Recommended Posts

i believe hosting websites are a no-no in the tos agreement with my isp provider, but can they tell if i do so? i have a small website i want to host on an old pc using apache. i've got it hosted for free on brinkster, but no ftp sucks and the space is too limiting (30MB). uhm, i said small, cuz it's mainly a personal site to host albums of pictures and such.

also, when considering a host you've got to know what's how much bandwidth you'll get. if i get this started, what is the limit on my bandwidth then? i mean, how much data can be served per month? is there a way to figure this out?

thanks for any help.

Link to comment
https://www.neowin.net/forum/topic/25850-hosting-website-not-allowed/
Share on other sites

Don't regularly run intrusive portscans on people to see what services are running, as that is both unethical and illegal to some degree.

However, what they do more often than not is 'sniff' traffic running to their customers to look for any traffic directed at port 80, or 21 (if running web servers and FTP services are not allowed on said ISP), then crusually wait for a responce from said port. If both of these carry, using a tool such as capturenet, they automatically log the transaction and alerts are normally feried by e-mail to the system administrator. Most routers employed by ISPs can carry out this as a matter of configuration, and as a result traffic to such ports never makes it through the router in the first place. (AOL for instance blocks any traffic to the 139 port of their customers to prevent people taking advantage of any possible IPC$ vulnerabilities). ISP's such as this normally don't care if people run webservers or FTP's based on the fact that no packets will ever reach those services to even make use of them.

The way round it for FTP is indeed through the use of differant port number, meaning that the packets will be neither flagged nor tagged. Especially if the person has their client set up to recieve packets from the FTP service on port 25. That way, it appears to the ISP and their sniffers as if the person running the FTP site on a high port and sending information to the client, is in fact legitimately connecting to an FTP service on an external source.

With http connections the problem is of course created by the fact that browsers by default will always attempt to connect to port 80, meaning that if you changed the port, you would have to tell people about that change, before they could look at your site so they could reconfigure their browsers.

I'd personally just stick the site up and see what happens, and how many hits it gets, and see if the ISP admin e-mailed me and told me to shut it down, which is the normal course of action for them to take. They rarely sever connections for such ridiculously unimportant offenses.

The other way of doing it, is pay a pitifully small amount a month to have your site hosted by a company, with 100 MB of web-space.

Scrown Owl

  Quote
Originally posted by mimeryme

ah, thanks Awesys, now just got to figure out what to change in my apache settings to let me do that.

Lookup the "Listen" Directive. You can add the a Listen 88 or Listen 8080 line if you like.

As for possible bandwidth, do the math. Just muliply what you can get per second times 60*60*24*30 and that's how much you can do per month.

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • KDE Plasma 6.5 will notify you if your printer's ink is low by David Uzondu This week, the KDE team continued work on the upcoming Plasma 6.5.0 as well as Plasma 6.4's fourth bug fix release, 6.4.4. As usual, both Plasma versions saw several UI tweaks, bug fixes, and performance improvements. The most notable changes are discussed in this article. Let's start with Plasma 6.5. The desktop environment is getting a useful feature that tells you when your printer is low on ink. This works by having the system check the Common Unix Printing System, or CUPS, for marker levels after a print job is created or completed. CUPS stores attributes like marker-levels in its printers.conf file, and once a level is determined to be low, it triggers a marker-supply-low-warning that Plasma will now use to inform you. UI improvements scheduled for 6.5 include disabling key repeat for certain global shortcuts, like toggling Overview, to prevent rapid screen flashing that could be a seizure risk. There is a better "Someone started sharing this screen" notification that now appears only after a connection is fully established. You will also find standard KDE styling with the "Confirm deleting network connection" dialog, and more consistent spacing in the Global Menu widget. As for bug fixes in 6.5, a layout bug that caused visual overflow in the printer setup page has been corrected. An issue that stopped you from using the virtual keyboard in the Application Dashboard search field is fixed, and XDG portal-using apps can now request screencasts of new virtual outputs. Finally, the clipboard configuration window's size and position information has been moved from the state config file to the settings file. Moving on to 6.4.4, the hitboxes for desktop items now correctly match their visual styling. This means no more accidentally selecting an invisible box around a file. And when you mark a notification as low priority, it will now correctly appear in your history if it arrived during Do Not Disturb mode, so it does not just vanish. If you're experiencing a Kwin crash on login, particularly in a QEMU virtual machine, 6.4.4 has a fix for that on the way. Other bug fixes 6.4.4 brings include: A fix for the Global Menu widget's single-button mode for X11 users. The search field in the Wayland version of the Global Menu widget works again. An annoying bug in the Global Shortcuts XDG portal that made apps think they had no shortcuts has been resolved. Plasma Browser Integration's built-in Share feature has been repaired. Plasma 6.4.4 will drop on the 5th of next month. You can find more details on the official KDE Blog.
    • I just remember wondering how she was ever a bridge officer at all with all of her insufferable insecurities. I am sure she's a wonderful person in real life, but the character was poorly written. They even had to dedicate a whole episode to her being forced into taking the responsibility of leading cadets out of a problem of some sort as if to show how she is "growing" into her function. Never bridge officer material and I just rolled my eyes at her scenes and eventually stopped watching the show altogether, but also because of all the lead character's cry/whisper/talking that frustrated me.
    • Didnt know it was coded/decoded so my bad.
  • Recent Achievements

    • Week One Done
      Homayoun Hotak earned a badge
      Week One Done
    • Dedicated
      Profit earned a badge
      Dedicated
    • One Month Later
      hhgygy earned a badge
      One Month Later
    • Week One Done
      hhgygy earned a badge
      Week One Done
    • One Year In
      NIKI77 earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      641
    2. 2
      ATLien_0
      241
    3. 3
      Xenon
      168
    4. 4
      neufuse
      149
    5. 5
      +FloatingFatMan
      123
  • Tell a friend

    Love Neowin? Tell a friend!