> The bandwidth for our free instances is 2 TB of free bandwidth.
>
> Mike Wolfman
> ww.vultr.com
> enior Linux Systems Administrator
π±
> The bandwidth for our free instances is 2 TB of free bandwidth.
>
> Mike Wolfman
> ww.vultr.com
> enior Linux Systems Administrator
π±
> Hi Team,
>
> Just noticed that you offer FREE (as in $0) VM(s) on the vc2-1c-0.5gb-free
> plan. however I also note that this has 0 Bandwidth.
>
> I'm a bit confused by this. What would be the point of having a free VM if it has no Bandwidth? How is network bandwidth charged in this case?
>
> cheers
> james
> Hi Team,
>
> Just noticed that you offer FREE (as in $0) VM(s) on the vc2-1c-0.5gb-free
> plan. however I also note that this has 0 Bandwidth.
>
> I'm a bit confused by this. What would be the point of having a free VM if it has no Bandwidth? How is network bandwidth charged in this case?
>
> cheers
> james
twtxt.net (_flagship pod_) will no longer be π€£ I've always want to see Yarn.social grow, but grow in ways that keep to its truest sense of "decentralised". That's one of the reasons I built yarnd not to scale too much π€£ My own pod has around ~18-20 active users per month (_give or take_) and that's honestly enough π
~
twtxt.net (_flagship pod_) will no longer be π€£ I've always want to see Yarn.social grow, but grow in ways that keep to its truest sense of "decentralised". That's one of the reasons I built yarnd not to scale too much π€£ My own pod has around ~18-20 active users per month (_give or take_) and that's honestly enough π
~
yarnd? π€ Vultr is offering 1 vCPU, 500MB Memory and 10GB Storage for FREE! That's right $0.00 π€£ 
yarnd? π€ Vultr is offering 1 vCPU, 500MB Memory and 10GB Storage for FREE! That's right $0.00 π€£
# Ignore Content-Type restrictions for Git
SecRule REQUEST_HEADERS:Host "@streq git.mills.io" "id:101,phase:1,t:none,nolog,ctl:ruleRemoveById=920420"
# Ignore Content-Type restrictions for Git
SecRule REQUEST_HEADERS:Host "@streq git.mills.io" "id:101,phase:1,t:none,nolog,ctl:ruleRemoveById=920420"
@lookupASN
@lookupASN
proxy-1:~# cat build.caddy.sh
#!/bin/sh
xcaddy build \\
\t--with github.com/caddy-dns/cloudflare \\
\t--with github.com/caddyserver/cache-handler \\
\t--with git.mills.io/prologic/caddy-ratelimit \\
\t--with git.mills.io/prologic/caddy-waf
proxy-1:~#
proxy-1:~# cat build.caddy.sh
#!/bin/sh
xcaddy build \
--with github.com/caddy-dns/cloudflare \
--with github.com/caddyserver/cache-handler \
--with git.mills.io/prologic/caddy-ratelimit \
--with git.mills.io/prologic/caddy-waf
proxy-1:~#
proxy-1:~# cat build.caddy.sh
#!/bin/sh
xcaddy build \
--with github.com/caddy-dns/cloudflare \
--with github.com/caddyserver/cache-handler \
--with git.mills.io/prologic/caddy-ratelimit \
--with git.mills.io/prologic/caddy-waf
proxy-1:~#
proxy-1:~# grep -c 'Bad ASN' /var/log/caddy/caddy.log
2441
proxy-1:~# grep -c 'Bad ASN' /var/log/caddy/caddy.log
2441
proxy-1:~# cat /etc/caddy/waf/bad_asns.txt
# CHINANET-BACKBONE No.31,Jin-rong Street, CN
# Why: DDoS
4134
# CHINA169-BACKBONE CHINA UNICOM China169 Backbone, CN
# Why: DDoS
4837
# CHINAMOBILE-CN China Mobile Communications Group Co., Ltd., CN
# Why: DDoS
9808
# FACEBOOK, US
# Why: Bad Bots
32934
proxy-1:~#
proxy-1:~# cat /etc/caddy/waf/bad_asns.txt
# CHINANET-BACKBONE No.31,Jin-rong Street, CN
# Why: DDoS
4134
# CHINA169-BACKBONE CHINA UNICOM China169 Backbone, CN
# Why: DDoS
4837
# CHINAMOBILE-CN China Mobile Communications Group Co., Ltd., CN
# Why: DDoS
9808
# FACEBOOK, US
# Why: Bad Bots
32934
proxy-1:~#
> An autonomous system (AS) is a collection of connected Internet Protocol (IP) routing prefixes under the control of one or more network operators on behalf of a single administrative entity or domain, that presents a common and clearly defined routing policy to the Internet.[1] Each AS is assigned an autonomous system number (ASN), for use in Border Gateway Protocol (BGP) routing. Autonomous System Numbers are assigned to Local Internet Registries (LIRs) and end-user organizations by their respective Regional Internet Registries (RIRs), which in turn receive blocks of ASNs for reassignment from the Internet Assigned Numbers Authority (IANA). The IANA also maintains a registry of ASNs which are reserved for private use (and should therefore not be announced to the global Internet).
> An autonomous system (AS) is a collection of connected Internet Protocol (IP) routing prefixes under the control of one or more network operators on behalf of a single administrative entity or domain, that presents a common and clearly defined routing policy to the Internet.[1] Each AS is assigned an autonomous system number (ASN), for use in Border Gateway Protocol (BGP) routing. Autonomous System Numbers are assigned to Local Internet Registries (LIRs) and end-user organizations by their respective Regional Internet Registries (RIRs), which in turn receive blocks of ASNs for reassignment from the Internet Assigned Numbers Authority (IANA). The IANA also maintains a registry of ASNs which are reserved for private use (and should therefore not be announced to the global Internet).
> An autonomous system (AS) is a collection of connected Internet Protocol (IP) routing prefixes under the control of one or more network operators on behalf of a single administrative entity or domain, that presents a common and clearly defined routing policy to the Internet.\n Each AS is assigned an autonomous system number (ASN), for use in Border Gateway Protocol (BGP) routing. Autonomous System Numbers are assigned to Local Internet Registries (LIRs) and end-user organizations by their respective Regional Internet Registries (RIRs), which in turn receive blocks of ASNs for reassignment from the Internet Assigned Numbers Authority (IANA). The IANA also maintains a registry of ASNs which are reserved for private use (and should therefore not be announced to the global Internet).
429 Too many requests response π Thank you Google! π 
429 Too many requests response π Thank you Google! π
yarnd supports video too π€£
yarnd supports video too π€£