New answers tagged

0

You could try following the link in this thread to see if that will help with your phone. As for when you use the dongle, you can try logging into the gateway set by the dongle and see if you can get any access to be able to forward the ports through it. If not, then you might consider buying a router that can connect to the internet using a cellular ...


0

You can set up a Cloud VPN Between your Server hosted in your Enterprise and GCE, more information can be found in this article. Another way to do it is by setting up a NAT gateway on GCE with a static IP, however this will create a single point of failure which might be an issue in case of instance or zone maintenance.


1

Dropping the [RST,ACK] and [FIN,ACK] will not work. There are many application like ftp upload that will simply fail to ack the completion of the FTP transfer. The comments by gscott are the correct method, but one additional requirement is needed. You must make them strict by applying the policy iptables -P OUTPUT DROP iptables -P FORWARD DROP iptables -...


0

The real answer is : Publish a vpn endpoint. This can be behind building NAT (it is better in a publicly visible endpoint). From remote, you vpn to your network and then rdp over the vpn. Making RDP publicly accessible is a bad bad idea.


2

To get this setup working, is it simply a case of asking the people who own the building to forward port 1194 to the ip address they have assigned our router? Yes.* Or is it potentially more complicated than that? No.* Also, if we want to remote desktop in to one of our pcs, is it just a case of getting them to forward port 3389 to our router ...


0

Port forwarding and DMZ are related to sessions initiated on the WAN side and redirected as configured to the proper local machine. For that reason, unless you have advanced configuration or shell access to your router (which does not appear to be your case), it is not possible to define the rules needed in it. Even if you could, it would cause a conflict ...


0

I have found a working solution: sysopt noproxyarp outside2 ! object network net_192.168.31.0 subnet 192.168.31.0 255.255.255.0 ! object network net_192.168.1.0 subnet 192.168.1.0 255.255.255.0 ! object network net_192.168.2.0 subnet 192.168.2.0 255.255.255.0 ! object-group network 3G_NAT network-object object net_192.168.1.0 network-object object ...


0

Try this sudo ufw allow from 192.168.10.0/24 to 192.168.10.1 port 53 proto tcp sudo ufw allow from 192.168.10.0/24 to 192.168.10.1 port 53 proto udp This will allow TCP and UDP DNS (port 53) traffic from your local private network (which I assume is 192.168.10.0/24, or in other words, 192.168.10.1-255) and not anywhere else. Finally, check to make sure ...


2

Before answering the questions, I'd like to address some of the assumptions in it. The firewalling properties of NAT were also beneficial for security. This is often-repeated, but simply not true; see below. IPv4 NAT firewall rules are "block incoming packet remote-address:port -> local-address:port, unless sent outgoing packet local-address:port ->...


1

Changes made with firewall-cmd are only persistent when you (also) make them persistent with --permanent... man firewall-cmd --permanent The permanent option --permanent can be used to set options permanently. These changes are not effective immediately, only after service restart/reload or system reboot. Without the --permanent option, a ...


2

The time module will deliver close to what you are wanting; the below covers 2:00am to 6:00am every day (read up on this module for further information as it does also allow for targeting on a per day of the week basis): -m time --timestart 02:00 --timestop 06:00 but you would need to create many rules to achieve your "every 5 minutes" requirement. Also ...


0

NAT needs to be able to translate traffic coming from a private interface to an IP address attached to a public interface. When you configure NAT you identify one interface as Public and one as Private. This would be difficult on a Server with a single NIC. If you are running 2012 R2 and if you have the correct sort of NOC you can create virtual interface ...


3

Teredo is a protocol that tunnels IPv6 traffic via UDP on IPv4 to a Teredo server, which then routes the IPv6 traffic onward to the Internet, or back toward you. The Teredo IPv6 address you receive encodes the IPv4 address of the Teredo server and UDP port for your particular tunnel connection. If the tunnel disconnects and reconnects, these may change. ...


0

Firewall -> NAT -> Outbound There you can create a new rule for the WAN with source 10.1.1.0/24 and NAT address 'WAN address'. This should automatically be done by pfsense if you assigned a WAN and LAN interface. Also: Interfaces -> WAN Make sure if you use static addresses that you have an IPv4 upstream Gateway set. If not, click on 'add a new one' ...



Top 50 recent answers are included