Tag Info

New answers tagged

0

If you want join 2 different LAN-s, you can do something like this: sysctl -w net.ipv4.ip_forward=1 iptables -A FORWARD -i eth0 -j ACCEPT iptables -A FORWARD -i eth1 -j ACCEPT


0

The EC2 Instance in question had no public IPv4 address ergo could not participate in The Internet. Simply assign a public IP address to the instance, and: [ec2-user@nat1 ~]$ curl -v wikipedia.org/ * Trying 208.80.154.224... * Connected to wikipedia.org (208.80.154.224) port 80 (#0)


1

I suspect your SIP port is now in the RTP range, so Asterisk doesn't realize this is a SIP connection. Either move the SIP port or move the RTP port range so they don't overlap. Please capture the CLI output of a failed call (off LAN) and a succesfull call (on LAN) and post the results here. To capture the CLI output, from the bash prompt: asterisk -r ...


1

On router A, your acess-list 10 seems to be wrong access-list 10 permit 0.0.0.0 255.255.255.0 do this config t no access-list 10 access-list 10 permit 10.1.2.0 0.0.0.255


1

Solved: I put the following commands, I missed one. iptables -t nat -A PREROUTING -s 172.19.128.248 -j DNAT --to-destination 192.168.200.202 iptables -t nat -A PREROUTING -s 192.168.200.202 -j DNAT --to-destination 172.19.128.248 iptables -t nat -A POSTROUTING -p tcp -j SNAT --to-source 172.19.128.237


0

Are you performing this configuration from within RRAS? I would like to duplicate the steps you are trying and go from there.


1

First, I think you may need to enable ip forwarding. sysctl -w net.ipv4.ip_forward=1 to get your machine to be a router. Full details on ip forwarding are here. Second, I won't swear to this but your iptables rules look wrong to me. It seems you need something more like this: iptables -A PREROUTING -t nat -i eth0 -p tcp --dport 1044 -j DNAT ...


0

I have an active internet connection from provider on festethernret1 and also have vlan1. I need to have an internet connection from festethernret1 to my vlan1. If your Internet connection is on FastEthernet 1, then your config is wrong. Your config both applies ip nat outside on FastEthernet 0, and uses FastEthernet 0 for the NAT overload configuration ...


2

This seems to be related to the Linux conntrack code being unhappy about the "long" delayed segment, aborting the connection because of unexpected data. The behavior can be mitigated by setting netfilter/nf_conntrack_tcp_be_liberal to 1. Kernel documentation: https://www.kernel.org/doc/Documentation/networking/nf_conntrack-sysctl.txt


2

A NAT interface will allow outbound traffic from your vm but not inbound. Create a bridge interface on your host then in your VirtualBox VM network settings select the Bridged Adapter from the 'Attached To' dropdown and then the bridge interface from the "Name' dropdown. Of course, if you don't really care about having separate subnets for your host and ...


1

You can whitelist anything you want writing the following at the top of the CHAIN: iptables -t mangle -A rate-limiter <rule to match whitelisted> -j RETURN Packets matching the whitelisted networks will return to POSTROUTING without modification.


0

I figured it out, the issue was with the zone based firewall. All I needed was the NAT rule, plus to modify the firewall to allow specific incoming ports. I found this article very useful and explained everything needed for zone-based port forwarding.


3

Check that your VMs have ip addresses on 10.x.x.x/24 (netmask 255.255.255.0) Set 10.x.x.11 (br0 ip address) as the default gateway of your VMs Enable ip forwarding on the physical host Enable SNAT with: iptables -t nat -A POSTROUTING -s 10.x.x.x/24 -o eth1 -j SNAT --to y.y.y.102


1

iptables -t nat -I POSTROUTING -s 10.x.x.x/24 ! -d 10.x.x.x/24 -j SNAT --to-source y.y.y.102 this must be changed to iptables -t nat -I POSTROUTING --out-interface eth1 -j SNAT --to-source y.y.y.102 According to your first rule, only packages with destination to 10.x.x.x must be processed. So, what about traffic from outside to your network? (source ...


0

There is no difference in the routing needed for ssh and http. Both are running over TCP and are playing no tricks with the underlying IP traffic. According to your question both are using the same hostname, but you did not mention whether that hostname resolves to just one or multiple IP addresses. Using the telnet command you can verify if a connection ...


1

I suspect that the answer you're looking for is an Azure site-to-site VPN. Considering your size (2 DCs, ISP with NAT), you might want to consider Office 365 for Business instead of hosting your own email, however. You also haven't said what the web server would host. If it's just your company web site, that can really be hosted anywhere. Unless there's ...


1

Ok, so following on from http://superuser.com/questions/923747/vpn-ip-forwarding-and-nat/925570#925570 I have what may be a really stupid question to ask, but if all you need is access to specific ports, like http/https have you tried SSH Tunneling? It's much easier than setting up a VPN. Ultimately you ssh from one machine to another, and then have the ...


0

The key appears to be that HTTP/S Management needs to be explicitly whitelisted, even if you have a firewall rule that permits regular traffic. So the entries required were: LAN > WAN Source: Any Destination: All X2 Management IP Service: HTTPS Management A second rule for HTTP Management allowed the non-secure site to redirect to the secure one. ...


0

As of April 2015, AWS now offers a straightforward solution to this problem: VPC Endpoints A VPC endpoint enables you to create a private connection between your VPC and another AWS service without requiring access over the Internet, through a NAT instance, a VPN connection, or AWS Direct Connect. Endpoints are virtual devices. They are horizontally ...



Top 50 recent answers are included