Dismiss Notice
It can take 24-48 hours for the hosting/Teamspeak applications to be reviewed. Opening a thread before 48 hours, asking about the application timeline will result in your account and application being deleted permanently.

Mod_Security Setup Tips?

Discussion in 'Free VPS Hosting' started by IEpicDestroyer, Sep 23, 2017.

  1. Bryan

    Bryan Administrator

    Messages:
    5,886
    Likes Received:
    945

    It was. Was pinging in and out on IPv6. Let me try again and see what I can come up with.
     
  2. Bryan

    Bryan Administrator

    Messages:
    5,886
    Likes Received:
    945
    Pinging in without any issues at all.

    Code:
     ping6 2605:6f80:0:800::4142:c929
    PING 2605:6f80:0:800::4142:c929(2605:6f80:0:800::4142:c929) 56 data bytes
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=46 ttl=54 time=42.4 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=47 ttl=54 time=42.4 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=48 ttl=54 time=42.5 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=49 ttl=54 time=42.4 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=50 ttl=54 time=42.5 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=51 ttl=54 time=42.3 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=52 ttl=54 time=42.8 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=53 ttl=54 time=42.6 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=54 ttl=54 time=42.4 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=55 ttl=54 time=42.4 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=56 ttl=54 time=42.5 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=57 ttl=54 time=42.5 ms
    

    Not sure why it's not pinging out, but I'll see what I can do.
     
  3. Bryan

    Bryan Administrator

    Messages:
    5,886
    Likes Received:
    945
    Pinging out as well. Nothing on the server or your VPS was changed.

    Code:
    ping6 ipv6.google.com
    PING ipv6.google.com(sea15s02-in-x0e.1e100.net) 56 data bytes
    64 bytes from sea15s02-in-x0e.1e100.net: icmp_seq=4 ttl=50 time=34.1 ms
    64 bytes from sea15s02-in-x0e.1e100.net: icmp_seq=5 ttl=50 time=34.1 ms
    64 bytes from sea15s02-in-x0e.1e100.net: icmp_seq=6 ttl=50 time=34.1 ms
    
     
  4. IEpicDestroyer

    IEpicDestroyer Premium VPS Client

    Messages:
    98
    Likes Received:
    18
    That's umm... funny. Cloudflare isn't making any connections over IPv6, kept the existing record so it'll just randomly select IPv4 or v6 to use. Let me try pinging it from my PC to see.
     
  5. Bryan

    Bryan Administrator

    Messages:
    5,886
    Likes Received:
    945
    I have had it pinging in and out for almost 40 minutes. It's still going as we speak.

    epic1.png epic2.png
     
  6. IEpicDestroyer

    IEpicDestroyer Premium VPS Client

    Messages:
    98
    Likes Received:
    18
    That's very very funny. Because this is what happened on my computer, I didn't change anything on the server lately, all I remember doing past week was uploading some new files on the web server and creating a new virtual host for a subdomain.

    Pinging 2605:6f80:0:800::4142:c929 with 32 bytes of data:
    Request timed out.
    Request timed out.
    Request timed out.
    Request timed out.

    Ping statistics for 2605:6f80:0:800::4142:c929:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

    Tracing route to 2605:6f80:0:800::4142:c929 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms reacted
    2 5 ms 7 ms 7 ms reacted
    3 8 ms 8 ms 8 ms sttlwawbgr80.bb.telus.com [2001:568:1::50a]
    4 8 ms * 8 ms node-1w7jr9fenjgbk2vrqtjijbcxq.ipv6.telus.net [2001:568:1::13e]
    5 11 ms 30 ms 11 ms 100ge14-1.core1.pdx1.he.net [2001:470:0:3c2::2]
    6 27 ms 35 ms 27 ms 100ge10-1.core1.slc1.he.net [2001:470:0:214::2]
    7 43 ms 36 ms 36 ms 10ge1-1.core1.las1.he.net [2001:470:0:27d::1]
    8 50 ms 45 ms 42 ms 2001:470:1:4b7::2
    9 36 ms 50 ms 47 ms 2604:2280:fffe:1::2
    10 36 ms 36 ms 36 ms 2605:6f80:0:800::2
    11 * * * Request timed out.

    It times out all the way until 30 hits. There's some glitch with the server not being able connect to the internet.

    Oh, got a question: is the IPv6 provided by a tunnel or is it native access? Noticed something with one of the hops.
     
  7. Bryan

    Bryan Administrator

    Messages:
    5,886
    Likes Received:
    945
    The server is not having any issues connecting to the internet that I can see.

    From Los Angeles:

    Code:
    PING 2605:6f80:0:800::4142:c929(2605:6f80:0:800::4142:c929) 56 data bytes
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=1 ttl=57 time=7.73 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=2 ttl=57 time=7.76 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=3 ttl=57 time=7.83 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=4 ttl=57 time=7.71 ms
    
    --- 2605:6f80:0:800::4142:c929 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3038ms
    rtt min/avg/max/mdev = 7.713/7.761/7.834/0.117 ms
    
    
    
    
    traceroute to 2605:6f80:0:800::4142:c929 (2605:6f80:0:800::4142:c929), 30 hops max, 80 byte packets
     1  2607:fcd0:100:1a00::2 (2607:fcd0:100:1a00::2)  0.036 ms  0.011 ms  0.011 ms
     2  2607:fcd0::602c:b421 (2607:fcd0::602c:b421)  0.236 ms  0.262 ms  0.239 ms
     3  2001:504:13::1a (2001:504:13::1a)  2.131 ms  2.168 ms  2.202 ms
     4  10ge3-1.core1.las1.he.net (2001:470:0:27e::2)  13.338 ms  7.796 ms  7.874 ms
     5  * 2001:470:1:4b7::2 (2001:470:1:4b7::2)  7.799 ms 2001:470:1:405::2 (2001:470:1:405::2)  7.834 ms
     6  2604:2280:fffe:1::2 (2604:2280:fffe:1::2)  10.445 ms  8.222 ms 2604:2280:fffe:2::2 (2604:2280:fffe:2::2)  7.869 ms
     7  2605:6f80:0:800::2 (2605:6f80:0:800::2)  7.649 ms  7.767 ms  7.676 ms
     8  2605:6f80:0:800::4142:c929 (2605:6f80:0:800::4142:c929)  7.607 ms  7.724 ms  7.581 ms

    From Dallas:

    Code:
    PING 2605:6f80:0:800::4142:c929(2605:6f80:0:800::4142:c929) 56 data bytes
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=1 ttl=53 time=35.1 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=2 ttl=53 time=35.2 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=3 ttl=53 time=35.2 ms
    64 bytes from 2605:6f80:0:800::4142:c929: icmp_seq=4 ttl=53 time=35.2 ms
    
    --- 2605:6f80:0:800::4142:c929 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 3038ms
    rtt min/avg/max/mdev = 35.166/35.228/35.266/0.138 ms
    
    
    
    traceroute to 2605:6f80:0:800::4142:c929 (2605:6f80:0:800::4142:c929), 30 hops max, 80 byte packets
     1  2604:880:1:1::2 (2604:880:1:1::2)  0.032 ms  0.013 ms  0.011 ms
     2  2604:880:12::41 (2604:880:12::41)  6.692 ms  6.684 ms  6.677 ms
     3  2604:880:20::1 (2604:880:20::1)  1.543 ms  1.587 ms  1.573 ms
     4  2604:880:10::1 (2604:880:10::1)  0.505 ms  0.494 ms  0.487 ms
     5  10gigabitethernet3-1.core1.dal1.he.net (2001:504:0:5::6939:1)  9.149 ms  9.261 ms  9.316 ms
     6  100ge4-2.core1.phx2.he.net (2001:470:0:360::2)  19.284 ms  23.713 ms  23.700 ms
     7  100ge11-2.core1.lax2.he.net (2001:470:0:362::1)  27.936 ms  37.199 ms  37.255 ms
     8  10ge3-1.core1.las1.he.net (2001:470:0:27e::2)  40.550 ms  35.395 ms  35.475 ms
     9  2001:470:1:405::2 (2001:470:1:405::2)  39.572 ms 2001:470:1:4b7::2 (2001:470:1:4b7::2)  35.319 ms  35.313 ms
    10  2604:2280:fffe:2::2 (2604:2280:fffe:2::2)  35.503 ms 2604:2280:fffe:1::2 (2604:2280:fffe:1::2)  35.270 ms 2604:2280:fffe:2::2 (2604:2280:fffe:2::2)  35.366 ms
    11  2605:6f80:0:800::2 (2605:6f80:0:800::2)  35.242 ms  35.322 ms  35.294 ms
    12  2605:6f80:0:800::4142:c929 (2605:6f80:0:800::4142:c929)  35.287 ms  35.271 ms  35.362 ms
     
  8. IEpicDestroyer

    IEpicDestroyer Premium VPS Client

    Messages:
    98
    Likes Received:
    18
    Funny, funny, funny, I completely don't understand how it works, but just tested it again and it's now responding to any site. Able to connect on PC, random looking glasses, and was able to connect to Cloudflare. Funny, it's been cutting in and out for me. Thanks for your help and sorry for troubling you. But I got one last question, is the IPv6 address provided from HE's tunnel broker? That would explain why it keeps using HE instead of connecting to the d/c from SIX for me.
     
  9. Bryan

    Bryan Administrator

    Messages:
    5,886
    Likes Received:
    945
    It could definitely be that the IPv6 side of the network is having intermittent issues. I'll keep watching it and see what happens.

    The IPv6 is not through the tunnel broker, but I believe it is still through Hurricane Electric. It's an actual block through Fiberhub (datacenter). I know the datacenter has direct peering with SIX, but I don't know if it's on the IPv6 side of the house. It definitely does through IPv4. They actually have a datacenter in the Westin Building in Seattle and another in Tukwila. But ours is located in Las Vegas.
     
  10. IEpicDestroyer

    IEpicDestroyer Premium VPS Client

    Messages:
    98
    Likes Received:
    18
    Hmm.. you might want to double check with the datacenter. I have native IPv6 access from my internet provider and this is the trace route:

    Tracing route to 2605:6f80:0:800::4142:c929 over a maximum of 30 hops

    1 <1 ms <1 ms <1 ms reacted
    2 5 ms 10 ms 5 ms reacted
    3 9 ms 11 ms 8 ms sttlwawbgr80.bb.telus.com [2001:568:1::50a]
    4 8 ms * 10 ms node-1w7jr9fenjgbk2vrqtjijbcxq.ipv6.telus.net [2001:568:1::13e]
    5 11 ms 11 ms 11 ms 100ge14-1.core1.pdx1.he.net [2001:470:0:3c2::2]
    6 35 ms 27 ms 27 ms 100ge10-1.core1.slc1.he.net [2001:470:0:214::2]
    7 46 ms 36 ms 36 ms 10ge1-1.core1.las1.he.net [2001:470:0:27d::1]
    8 36 ms 37 ms 36 ms 2001:470:1:4b7::2
    9 37 ms 36 ms 38 ms 2604:2280:fffe:1::2
    10 37 ms 36 ms 36 ms 2605:6f80:0:800::2
    11 36 ms 36 ms 36 ms 2605:6f80:0:800::4142:c929

    Was looking up the IPs without hostnames to see who it belongs to and for the eighth hop, it showed in the organization "Hurricane Electric IPv6 tunnel broker".
    It could be a network issue today, usually I get my connection with the peered port at SIX, today it fell back to HE to connect to the server.
     
  11. Bryan

    Bryan Administrator

    Messages:
    5,886
    Likes Received:
    945
    It's definitely through Hurricane Electric to my knowledge, but not through the tunnel broker service. We have a /32, which the tunnel broker doesn't offer. All they have is /48. But HE might just label their v6 WHOIS with the tunnel broker name. I honestly don't know.
     
  12. IEpicDestroyer

    IEpicDestroyer Premium VPS Client

    Messages:
    98
    Likes Received:
    18
    Hmm.. oh well. Thanks for your help!
     

Share This Page