Tag Info

New answers tagged

0

If you're running Windows, check the output of your route print command. You will see an entry for: 0.0.0.0 0.0.0.0 [Gateway IP] [Interface IP] [Metric] It sounds like your traffic is probably going through your VPN tunnel when that is active. Since your VPN client is offloaded to an external device (VPN router), you will have no software options for ...


0

I managed to get this to work by connecting 2 routers (client and server) with openVPN, where the tap0 interface is bridged to ethernet on both sides. Seems that not propagating 255.255.255.255 over the VPN interface may be an issue on Windows clients only, perhaps due to the lack of bridging.


0

If you cannot route to localhost, perhaps you can route to another local server and do the spoof there. Perhaps you can give that server and your machine an extra network address in a /30, with the spoof-server the original IP, and your machine the other IP in that range.


1

You can add a route to access the server's public IP directly through its local IP. On Windows, the command is like route add [public IP] mask 255.255.255.255 [the server's local IP] To add a persistent route, add -p parameter to above command. Then each time when you visit the public IP, the computer will go thru the server's local IP as gateway. ...


0

What you really need to do is setup separate DNS zones for internal and external consumption where the external view is a subset of the internal view and only contains names that refer to A records in public IP address space that is reachable from the public Internet (a firewall is assumed), and the internal view has everything and is reachable by all ...


0

This can be achieved using a custom routing table and policy (I recently did something very similar myself) Firstly create a custom routing table for your VPN echo "10 vpn" >> /etc/iproute2/rt_tables Tell iproute2 to use this routing table for traffic to and from your 192.168.2.0 network ip rule add from 192.168.2.0/24 table vpn ip rule add to ...


3

It sounds like you're probably using NAT for your own internal private subnet. Couple that with firewall capabilities of DD-WRT and only opening ports inbound that you approve (implicit deny), and you should be safe. Note that any plain-text traffic traversing that link is not safe. It could be subject to snooping by the landlord on his upstream ...


0

IPv6 Prefix 2001:1:a481:300::/56 if you have 56 prefix it would be nicer to include zeroes completed prefix looks like this: 2001:0001:a481:0300:0000:0000:0000:0000/56 now we can see the prefix 2001:0001:a481:0300:0000:0000:0000:0000/56 In IPv6 the smallest subnet size (prefix) is 64; so you have 8 more bits to create subnets (2 zeros ...



Top 50 recent answers are included