search for: geoblock

Hi Several questions below: a) is it possible to block IP addresses on a per mountpoint level e.g. my user with /mountpointA.ogg does not mind being hammered by connections from 93.184.216.34 [example.com] but my user with /mountpointB.ogg wants to block that IP address. b) is it possible to geoblock ranges of IP addresses and whole countries on a per mountpoint basis? c) what options do people use for geoblocking? I'm on a VPS so ipset is currently not an option. Many thanks in advance Chip Scooter -------------- next part -------------- An HTML attachment was scrubbed... URL: <http:...

Hi, I stumpled upon Icecast, but I effectively can only play few stations because somehow most of the stations that I'm interested in use the radionomy service. After some research I found out that I'm not the only one and that this company is blocking many countries worldwide: https://www.google.com/search?q=this+radio+station+is+not+available+in+your+country+site:board.radionomy.com

...> > a) is it possible to block IP addresses on a per mountpoint level e.g. my > user with /mountpointA.ogg does not mind being hammered by connections from > 93.184.216.34 [example.com] but my user with /mountpointB.ogg wants to > block that IP address. > > b) is it possible to geoblock ranges of IP addresses and whole countries > on a per mountpoint basis? > > c) what options do people use for geoblocking? I'm on a VPS so ipset is > currently not an option. > > Many thanks in advance > > Chip Scooter > > __________________________________________...

...>> e.g. my user with /mountpointA.ogg does not mind being hammered >> by connections from 93.184.216.34 [example.com >> <http://example.com>] but my user with /mountpointB.ogg wants to >> block that IP address. >> >> b) is it possible to geoblock ranges of IP addresses and whole >> countries on a per mountpoint basis? >> >> c) what options do people use for geoblocking? I'm on a VPS so >> ipset is currently not an option. >> >> Many thanks in advance >> >> Chip Scooter...

...allow everything but 2 countries (AU,NZ). There are even more conflicting ideas about how to do this, but I figured it out. Also I cannot see a difference in speed between using (maxmind) -A filter_countries -m geoip --src-cc AU,NZ -j ACCEPT and (ipdeny) -A filter_countries -m set --set au.geoblock src -j ACCEPT which is really good! Jobst -- The future isn't what it used to be (it never was). | |0| | Jobst Schmalenbach, General Manager | | |0| Barrett & Sales Essentials |0|0|0| +61 3 9533 0000, POBox 277, Caulfield South, 3162, Australia

...chafft wrote: > Why does Icecast forward both requests? Very simple: Not all auth setups > require username:password. E.g. some are only for logging and > accounting. Some auth using the IP address, which is already known in > the first request. Indeed. One of my streams has requested geoblocking, which uses exactly the mechanism you describe. -- Paul Martin <pm at nowster.me.uk>

On Mon, Jan 14, 2019 at 07:29:45AM +0000, Phil Perry (pperry at elrepo.org) wrote: > On 14/01/2019 07:09, Jobst Schmalenbach wrote: > > Hi > I use ipdeny's aggregated country lists to do the same thing: > > http://www.ipdeny.com/ipblocks/data/aggregated/ > > I just feed this data directly into ipset/iptables via a script running on > my firewall (not a C6 box).

Hi, we are using Icecast with url authentication for some days now. This generally works quite well. But our web service that provides the authentication check sometimes gets requests with the following parameters: { "action":"stream_auth", "mount":"/stream", "ip":"xxxxx", "server":"xxxx.yyyy.de",