jnraptor
jnraptor
Comments
-
Inception Hosting @ Frankfurt Mon 06 Sep 2021 01:24:01 PM BSTBasic System Information:---------------------------------Processor : Intel(R) Xeon(R) E-2278G CPU @ 3.40GHzCPU cores : 2 @ 3407.982 MHzAES-NI : ✔ EnabledVM-x/AMD-V : ❌ DisabledRAM : 1.9 GiBSwap : 512.0 MiBDisk : 47.2 GiBfio Disk Speed Tests (Mixed R/W…
-
Frankfurt Thanks for getting my IP delisted so quickly too! Mon 06 Sep 2021 01:24:01 PM BSTBasic System Information:---------------------------------Processor : Intel(R) Xeon(R) E-2278G CPU @ 3.40GHzCPU cores : 2 @ 3407.982 MHzAES-NI : ✔ EnabledVM-x/AMD-V : ❌ DisabledRAM : 1.9 GiBSwap : 512.0 MiBDisk : 47.2 GiBfio Disk…
-
You mean AdGuard home right? The below works if you are only using AdGuard home to serve your VPS and WireGuard clients. Under Settings | DNS settings, scroll down to the Access Control fields at the bottom. Under allowed clients, enter in ip ranges to whitelist. For example, I have whitelisted my VPS and wireguard clients…
-
f307a65641f024a994991640e8af5cc3 Thanks :)
-
Ordered "BF2020 Los Angeles 2c/2g/30gb". 10Gbit network! :astonished: =) # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## Yet-Another-Bench-Script ## v2020-11-20 ## https://github.com/masonr/yet-another-bench-script ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## #Fri 27 Nov 2020 02:54:50 AM CETBasic System…
-
Ryzen 3600 dedi with GorillaServers: AMD Ryzen 5 3600 3.4Ghz 6 Core 12 Thread with 4.2GHz boost 32GB DDR4 256GB NVMe 4TB HDD 1Gbps Port / 30TB outbound (unmetered inbound) # ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## ## Yet-Another-Bench-Script ## v2020-09-21 ## https://github.com/masonr/yet-another-bench-script ##…
-
I am on the server in Germany, but am not using the email features, so I cannot speak to it. However, here is the screenshot from DA, and it does show a mailing list icon:
-
@MaxKVM did not specify on the support ticket what networking changes were applied, but they did mention that it was a change they tried previously but did not get applied correctly. My suspicion is disabling ebtables as they have mentioned previously.
-
Thanks to @MaxKVM for being patient with me and following this thread too. They had me reboot the VPS after verifying the networking changes on their end and it is working now! My VPS is able to ping the upstream router's fe80 address now and thus able to respond back with NAs, and IPv6 starts working on wireguard clients…
-
I was able to get public IPv6s from a /112 block to work on @Abdullah's WebHorizon though. * Allocate IPv6 address(es) to the OVZ node on the control panel. This will automatically modify the node's /etc/network/interfaces file. * Compile and install boringtun or wireguard-go, as the nodes run on a 3.10 kernel, which does…
-
@MaxKVM noted that they disabled ebtables. Do you know what about security features are required to be disabled? I tried doing a permanent neighbor entry for the upstream router's fe80 address. sudo ip ne add fe80::xxxx:xxxx:xxxx:fdc0 lladdr xx:xx:xx:xx:fd:c0 dev eth0 router My VPS no longer sends out the NS entry below…
-
Thanks, signing up for the NAT256 account.
-
@Abdullah You mentioned in another thread that you solved the problem with giving out public IPv6 addresses to VPN clients? Does that apply to this NAT VPS?
-
Yes, my suspicion is that this is the root case, hence my original question. I was not able to get an answer to this from MaxKVM or Hivelocity. That works if I can ping fe80::1 gateway from eth0 and if upstream router is configured to listen to that. Unfortunately, that does not work. jon@max1 ~: ping -I eth0 fe80::1ping:…
-
The NS/NA loop that you mention looks very similar to the issue I have. Anyway, this is the second host I am using NDP to try and get around the on-link IPv6. IPv6 completely stopped working on the first host after a few days of testing, so I cancelled it. However, I have successfully tested without NDP on other services…
-
On the client side, there is already a route created when wireguard starts the connection. jon@ubuntu-vm ~: ip -6 route show table 51820default dev wg0 metric 1024 pref medium I will try proxying the wg0 IPv6 address too though - UPDATE: that does not help. Clients can already access the VPS wg0 interface through the…
-
Sadly, not many hosts provide routed IPv6, and that is why I have to use proxy_ndp.
-
Yes, the wg interface has no MAC address: 21: wg0: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1420 qdisc noqueue state UNKNOWN group default qlen 1000 link/none inet 10.9.0.1/24 scope global wg0 valid_lft forever preferred_lft forever inet6 2402:zzzz:zzzz:yyyy::200:1/112 scope global valid_lft forever preferred_lft forever I do…
-
* Output from ip6tables confirms that packets are being forwarded on the wg interface. This would also be confirmed since it starts working after pinging the gateway, and it also works when I switch to NATed IPv6. sudo ip6tables -L -v -nChain FORWARD (policy DROP 179 packets, 19062 bytes) pkts bytes target prot opt in out…
-
Setting accept_ra to 2 does not help. My VPS instance is not able to route to the upstream router's link local address IPV6 address (fe80::xxxx:xxxx:xxxx:fdc0), so it is unable to reply to the NS messages coming from that IPv6 address. jon@max1 /etc/network: ip ne show dev eth0107.xxx.xxx.xxx lladdr xx:xx:xx:xx:fd:c0…
-
* Yes, I have forwarding setup on wg* on both iptables and ip6tables. -A FORWARD -i wg+ -j ACCEPT-A FORWARD -o wg+ -j ACCEPT IPv4 and IPv6 forwarding is enabled in sysctl: net.ipv4.conf.all.forwarding = 1net.ipv6.conf.all.forwarding = 1 * RA is usually used to provide link local ipv6 gateway addresses right (among other…