Tag Info

New answers tagged

2

You can set up port forwarding on the physical machine, so that some physical machine's port in physical network is forwarded to the VM SSH port. For example if the physical machine is 10.10.10.1 and VM network 192.168.0.0/24, then port forwards can be like this: 10.10.10.1 port 225 forwarded to 192.168.0.1 port 22 10.10.10.1 port 226 forwarded to ...


0

"I checked "What Is My IP" of my personal PC and it poped up a number, so that means my personal PC has a public IP address" First of all, your PC does not have a public IP address but it has a private IP address (192.168.0.x /24) assigned from your router. Your modem has public IP address assigned from your ISP. To check your allocated public IP address, ...


0

In the end I decided to go a different route (no pun intended). I actually have multiple physical NICs installed and was using them for other things. I since have learned something new about clustering. I have always in the past dedicated a NIC for the sole purpose of the cluster heartbeat. We my heartbeat always had a single point of failure. That ...


2

That is usually one of the points of deploying CDN. Hiding the actual data source, so it is not as easy to be (D)DoSed.


3

You're NATting to the wrong IP. Don't NAT to your host's management IP, NAT to your guest's IP.


0

Your first setup has a serious flaw: if your switch does not support VLAN tagging, you are effectively mixing your public and private LAN segments. This is not a good thing. If your switch supports VLANS, you can use bonding + VLAN to use a common physical path (the bonded interface) to transmit two different logical VLAN - with the switch ensuring that no ...


2

You need to add the Routing and Remote Access role to the server and set it up for IP routing. RRAS will handle the routing from Nic2 to the Nic1 network, but the other servers will need to know the route back to Nic2. On the other servers you will need route add 10.71.2.0 mask 255.255.255.0 10.71.1.3 This will let the other servers know to route return ...


0

Finally I solved my specific case with running nginx as reverse proxy, available from localhost only, using proxy_bind directive. From my scripts I should make queries to something like http://localhost/nginx-proxy-ip-N/https://api.example.com/?q=123


0

The use of multiple ips on a single network card can usually only work when they are a clustered resource with the failover cluster manager. In each nic you add a single network ip address with or without a gateway in the operating system. You can add a cluster resource of type ip address to setup a access point for the resource. I use this for things like a ...


0

I also experienced some issues connecting to my Raspberry Pi while connected to open hot spot (in my case it was Optimum WiFi) (SSH into my Raspberry Pi 2@Optimum WiFi - Raspberry Pi Stack Exchange). So, I'd like to share my way of getting into my Raspberry Pi 2 using this ssh reverse tunnel: pi@raspberrypi ~ $ crontab -l | tail -1 @hourly ssh -S ...


0

Nikita, you actually have a couple of options. I have setup RPs this way on dedicated power but with only a mifi card on a board. The simplest solution is to contact your ISP and request a public or static NAT IP address. Most wireless providers will do this but they may charge you for it. Verizon has a $500 charge per account but then you can setup as ...


2

The command you need is as follows: route add 196.232.5.228 mask 255.255.255.255 192.168.x.x 192.168.100.146 Where 192.168.x.x is the default gateway on your network. This command is adding a route specifically for 196.232.5.228 (because of the 32 bit mask), and is routing it to 192.168.x.x (your gateway) via interface 192.168.100.146. As you didn't specify ...


1

If I understand you correctly you should just add multiple A-records for the given domain the clients are accessing. The DNS server will provide a random IP each time a client asks for it. It is also called round-robin DNS. Example: www IN A 127.0.0.1 www IN A 127.0.0.2 www IN A 127.0.0.3 www IN A 127.0.0.4


-1

In AIX you can use IP Alias to solve this. Let say you current IP address is 10.5.1.98 and your new IP address is 90.4.12.67 then you can define the 10.5.1.98 as an alias on top of 90.4.12.67. This way any server referencing the IP address 10.5.1.98 would be forwarded to 90.4.12.67 automatically. Whatever flavor of UNIX you are using or Linux for that ...


0

I Would go for 3 x cyberdata voip intercoms. certified by over 35 IP Telephone systems. You could purchase, say a Asterisk hosted solution. These are not much money at all. From the hosted platforms GUI you could set and form hunt groups. This would be an integrated office and remote office solution. That is controlled through the intercom. You can buy these ...


2

Thee was a very similar q on UL: http://unix.stackexchange.com/questions/86056/why-does-linux-require-moving-ip-from-eth-interface-to-bridge-interface The analiogy is that ETH resembles an uplink L1 cable.


2

Your subnet mask is undoubtedly 255.255.255.0, so that address is not on your network. If your subnet mask is 255.255.0.0, your machine wouldn't be sending traffic to it through your gateway.


0

That most likely means you are trying to add a routing table entry to a network which the router identifies as a local one. In this case it's a network configured on FastEthernet 0/0.


1

You need to enable mod_log_auth https://code.google.com/p/prosody-modules/wiki/mod_log_auth Then you need to add the following on your config file: log_auth_ips = "all" This will log the IP of all incoming connections (failed or not).


1

After several painful days of debugging and routing and routing tables and a fuming head, I gave up and reconfigured all IPSec clients under my direct control to use the .92 IP and everything works as expected now. I'm still at a loss for why I couldn't sourceroute or SNAT the packets...time for some serious testing in my testing environment (I suspect some ...


1

Presumably you are using PPPoE, which explains why eth1 is connected to the modem. When the PPP session is established, pppd will invoke the various scripts in the ip.up.d as you mentioned. The ifconfig commands that you show are an entirely reasonable way to set up an IP alias. The most logical reason why multiple IP addresses are used is for when ...


5

The error messages and the referenced RFC2181 5.4.1 pretty much already tells what's wrong: you are having conflicting NS records in your zone and in the parent zone as "glue" records. "Glue" above includes any record in a zone file that is not properly part of that zone, including nameserver records of delegated sub- zones (NS records), ...


1

So here's the answer after taking Matt's suggestion and going the trial and error route. The command I used had the following pattern ip route add via dev The final command actually was # ip route add 10.0.1.31 via 10.0.1.1 dev eth1 # ip route add 10.0.2.31 via 10.0.2.1 dev eth2 After adding these I had no issues pinging between the IP's on the ...


0

You can only have one default gateway, that's why it's called default. You can create static routes for the other NICs for particular networks reachable on that NICs VLAN.



Top 50 recent answers are included