Tag Info

Hot answers tagged

6

You're doing two things there. Enabling IP forwarding. The OS X equivalent might be: sysctl -w net.inet.ip.forwarding=1 ...but since I don't know exactly what you're trying to do, this might be technically correct but unhelpful. Adding a largely unnecessary firewall rule. If you haven't changed the default policy for your FORWARD chain (iptables -P ...


5

It is possible you don't have the ipv6 kernel module loaded on the system you're referring to. If you execute sysctl -a|grep ipv6 you will get a list of all available sysctl's referring specifically to ipv6. If that list is empty, that would lead me to believe ipv6 is not loaded. If you do see the net.ipv6.conf.all.forwarding entry in that sysctl grep, ...


4

The root cause of this problem were some implicit default routes that were not visible in the tables displayed by /sbin/route but were visible in tables displayed by /sbin/ip route and /sbin/ip rule. Then these tables were displayed it became apparent that a rule of this kind: default table route_eth0 via 10.11.11.1 dev eth0 was overriding this rule: ...


4

The SSH protocol has no way for clients to tell the server to bind to a certain address when doing a dynamic port forwarding, so no, you can't tell your SSH client to do it. You can't tell the OpenSSH server to do it either. It will blindly use getaddrinfo to connect to your remote host. The only way to fix is to configure your server so it does what you ...


3

What about your iptables rules? They look rather empty. I use the following rules, I am not sure if it would solve your exact problem though: # Allow TUN interface connections to OpenVPN server iptables -A INPUT -i tun+ -j ACCEPT # Allow TUN interface connections to be forwarded through other interfaces iptables -A FORWARD -i tun+ -j ACCEPT iptables -A ...


3

Your rule is correct. The problem you're having is because you're on a shared hosting plan at Godaddy.com. Putting the IP in here returns: Found 696 domains hosted on the same web server as 184.168.27.44 Since you're not the only site hosted on that IP, when a browser comes to the IP directly, the server doesn't know which site to return, so shows this ...


2

You can do it with something like this: Add a route on your gateway (or your desktop) route add -host 10.1.0.1 gw 172.16.9.8 Add a rule like this on the OtherBox iptables -t nat -A POSTROUTING -i eth0 -s 172.16.9.65 -d 10.1.0.1 -p tcp --dport 80 -j MASQUERADE


2

I think what you need is an HTTP proxy to do the rewriting of the request headers. IPTables doesn't parse the HTTP header and replace the domains in them. You should look at something like Nginx, or Squid for doing that, just something that understands and rewrites the HTTP request headers into the domain that you want. IPTables does not know any higher ...


2

You cannot do it with iptables even if you use the -d option as the domain names are loaded during iptables startup. The right way to do what you want to do is to use a proxy server like Squid.


2

Yes, in your configuration, assuming your network is routed properly, it should forward correctly. If you can ping FW from LN but not Internet from LN, you need to check your firewall rules on FW and routing rules on LN and FW. Verify that either LN has a public IP address, or your firewall is properly forwarding connections back to LN from the internet and ...


2

You need to enable IP forwarding somewhere: sudo sysctl -w net.ipv4.ip_forward=1 One of the place where it could be enabled is in /etc/sysctl.conf.d : echo "net.ipv4.ip_forward = 1" | sudo tee /etc/sysctl.conf.d/routing.conf Additionnaly, your iptables rules: -A POSTROUTING -s 10.0.2.0/24 -o eth0 -j MASQUERADE Will only enable NAT for hosts in ...


2

Short answer to your revised question is that there are two ways to do it; both require you remove the second NAT step (which destroys the info you're looking for). Your options after doing that are: 1) Make Server A the next hop for Server B for the traffic in question, which is why it works for your router as mentioned. This could be accomplished, in ...


2

Linux IP forwarding is basically routing. It doesn't by itself proxy, or really alter the traffic at layer 3 and above at all. That said, if you want to have something that masks the location of traffic, you could consider setting up NAT using iptables to masquerade (or source NAT) the traffic so that the source IP is that of the linux server. This works ...


2

You haven't fully explained the problem you're trying to solve, just how you think you can solve it, then asked for other options... So this answer may be somewhat vague, but I'll give it anyway. Firstly, for the love of all things holy, AVOID NAT. Please. A unicorn cries everytime a new NAT is created. Solution 1 If your servers have public IP's, just ...


2

I believe that's exactly what it would affect (assuming your DHCP client machine was running Linux, and your DHCP client supported that option[1]). Remember, DHCP stands for Dynamic Host Configuration Protocol. While it is most commonly used for just supplying the most basic network information (IP Address, default route, DNS servers), it was designed to ...


1

Your configuration seems pretty flawed. Maybe you should look into the general use of DNS. First of all you use URL Redirect on registryrocket a lot. I'm not sure that is what you want. You want to make an alias of for your heroku app. That is done with a cname. Then registryrocket cannot redirect the traffic of "rudolflabs.net" if it is not the nameserve ...


1

You will need to create a port forward in the router to your ubuntu server - otherwise it just wont work unless you sit on the same LAN as the server.


1

To perform a live migration and keep the virtual machine's IP address, both hosts must be on the same subnet.


1

How do you expect traffic to get routed to/from this server when it's on the wrong subnet? It sounds like you need to establish 802.1q trunks from your switchgear to all of your cluster nodes. This way, you can have all of your subnets available on all the nodes.


1

You are using a bridge, not routing. Don't configure the IP addresses on your host machine if you want to use them in the guests. You should not have br0:0 and the rest of them.


1

Bridge forwards ethernet packets, not just IP: forwarding delay: http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge#Forwarding_delay ethernet filtering: http://www.linuxfoundation.org/collaborate/workgroups/networking/bridge#No_traffic_gets_trough_.28except_ARP_and_STP.29


1

I think the better you can do is open 2 ports on router and redirect them; one for host_a like you has done, and other, for example 1235, to host_b. So you can use ssh -p 1234 user@X.X.X.X for host_a and ssh -p 1235 user@X.X.X.X for host_b


1

You could configure SSH on client B to use a different port. Doing that would allow you to have two different forward rules. Another option is connecting to host_B from Host_A's session. note You will want to make sure that you're using STATIC IP's for these machines. If you use DHCP, you're going to be SOL when your routers reassigns IP's. ssh from ...


1

You don't need to enable IP Forwarding on the varnish server for it to work. Varnish will not forward the client connection but, as a proxy, create a new connection on the user's behalf. If you can telnet apache2 80 or curl -x apache2:80 http://yoursite.com/yourpage from the varnish server then your network setup is ok. For the latter example ...


1

Unfortunately no, it will have a similar effect as bridging two connections. Windows selects the both interfaces based on the default gateway setting. The connection which it forwards (Bridges) on should not have a default gateway. It will then route that connection of to the first available connection which holds a default gateway. If you wish for more ...


1

Using Shorewall, you're looking for a DNAT rule (the online documentation is superb, go there). You'll end up with something like DNAT net loc:192.168.1.3:1234 tcp 5678 in your rules file, where 192.168.1.3 is the IP address of your database server. You may have to enable the routeback option if your incoming connection and your web server's ...


1

Reason: 85.214.144.212 don't know route to 192.168.178.0/24 network. 1. Add route to 192.168.178.0/24 network on 85.214.144.212-box. 2. Use NAT on Ubuntu_8.04.


1

You are doing it wrong. Using a VPN here gives you no additional security or benefit. Get rid of it. Simpler is always better. If you're trying to enforce the rule that users have to be "logged in" to get out of your network, use a proxy. For example, Squid & Squidguard.


1

If you have a bridged connection, you do not need to forward traffic. All you need to do is configure the virtual network adapter with a valid IP address on the same subnet as the host, or let it request one via DHCP. If you really want the host to be responsible for forwarding traffic from the guest machine and you want to configure this forwarding ...



Only top voted, non community-wiki answers of a minimum length are eligible