New answers tagged ip-address
Webmin's integrated miniserv doesn't AFAIK have a feature like this. It seems to be a job for a proper reverse proxy with name-based virtual host support. This isn't hard to configure and is well described in Webmin documentation. A good choice for a proxy is ie. Apache httpd.
093/8 is not always the same as 93/8. A leading Zero in an IP address can be a valid, though uncommon, way of noting that an address is expressed in octal (base-8). wikipedia: dot-decimal notation IETF: Text representation of IP Addresses
The address block 184.108.40.206/8 is allocated to RIPE NCC. From this block, RIPE NCC has allocated a couple of smaller blocks to Edgecast, namely 220.127.116.11/24 through 18.104.22.168/24 and 22.214.171.124/22. Once allocated, Edgecast is free to use these blocks wherever they see fit.
The -i makes 'last' show the remote hostname in dots and numbers IP address format instead of trying to display the hostname. I am not sure what the '.d' suffix is, nor can I find out anything on google. I can only guess it is trying to do a reverse lookup and is giving you part of a hostname and truncating it, although i thought you must specify -d to do ...
59.224.XX.178.d is not an IP-address but a hostname, or rather part of it. Last tries to do a reverse lookup and stores both the resulting hostname and ip-address for the remote host. By default the hostname gets displayed and long ones get truncated to display nice columns. Try last -a to display the hostname on the last column without truncation. or ...
Yes, create a reservation for the mac on your DHCP server.
This is a bad idea. Ok, that being said, as long as Client D will never, ever need to get to anythng on Client C or it's subnet this might work. Client A should have it's default gateway set on the NIC in the 192.168.111.0 subnet, and the NIC on the 192.168.0.0 subnet MUST NOT HAVE a default gateway set. Or your packets will be very confused as to where ...
A longshot, but netstat -aon should yield a list of established connections which you can filter by your VPN server port or PID. Copypaste the connected IPs into a tool like PingInfoView and run ping to see if any connection is dropping packets. When you identify "problematic" IPs, you can run tracert (or, even better, WinMTR) on them.
Without knowing all the specifics of the tomato router, perhaps something like this might work? iptables -t nat -A PREROUTING --dst 192.168.2.41 -p tcp --dport 7126 -j DNAT --to-destination 192.168.2.48:80 iptables -A FORWARD -d 192.168.2.48 -p tcp --destination-port 80 -j ACCEPT iptables -A FORWARD -s 192.168.2.48 -p tcp --source-port 80 -j ACCEPT
Top 50 recent answers are included