Tag Info

New answers tagged

0

Ok, i see a space into the URL, just before the IP addresses. Please remove those spaces from those *proxy env variables, and if that doesn't work, please try to unset it. To set it correctly: export http_proxy=http://7.1.1.12:3128/ To unset it: unset http_proxy Edit: Just repeat it for all *proxy variables


0

In your case, the apt-get command is finding those http_proxy entries and attempting to connect to the internet through them. In this case, it is an IP address belonging to the Department of Defense, and the :3128 is indicating Squid. Either you do work for the DoD - in which case you should not be posting this information on a public forum, this should ...


0

ufw is considered as a simple frontend for iptables. It does not support all the functionalities provided by iptables and filetering based on matching state of connection is not supported yet. ufw was basically initiated so that any user can understand or edit the basic firewall rules without having to go through the complexities of iptables. You can check ...


0

Did you run the script with privileges? Operation not permitted is usually a need for more privileges. It is a Kernel error so you either need to be root or have kernel permissions to do this. (I forget the name of the kernel permission that would be required) sudo /etc/block-china.sh or su -c 'sh /etc/block-china.sh'


1

iptables -L by default will try to resolve IP addresses to hostnames. I have a small iptables ruleset on this one system here, but it does take a while to get through even that small list because of the rules. By using iptables -L -n, it displays everything numerically and skips IP resolution and port service common name display. It should also display ...


1

Sorry for the late reply and thanks for the help, but I have found my issue. Apparently my server was under DoS attack, luckily only a few ip's. Somehow this only affected machines inside the home network and not directly the server it self, because I was able to access it from outside my home network. I've blocked them using ufw firewall and it seems I'm ...


0

Through bodhi.zazen`s comment I found the solution. Setting iptables -A OUTPUT -m state --state NEW -p udp --dport 53 -j ACCEPT iptables -A OUTPUT -m state --state NEW -p tcp --dport 53 -j ACCEPT and allowing Input from a previous established connection with eiter iptables -A INPUT -m state --state ESTABLISHED,RELATED -j ACCEPT or iptables -A INPUT ...


1

It is worth noting the the accepted answer only applies for other network hosts connecting to the machine running iptables. It does not redirect the port for clients running on the iptables machine trying to connect to port 25570 (for example). These entries will forward the port for connections coming from the network or from the local host running the ...


0

As asked by Doug Smythies adarsh@adarsh-VPCEB14EN:~$ sudo ping google.com PING google.com (173.194.36.1) 56(84) bytes of data. 64 bytes from google.com (173.194.36.1): icmp_seq=1 ttl=56 time=514 ms 64 bytes from google.com (173.194.36.1): icmp_seq=2 ttl=56 time=499 ms 64 bytes from google.com (173.194.36.1): icmp_seq=3 ttl=56 time=587 ms ^C --- google.com ...


0

Update: Recreated the file share_my_internet.sh and the commands are working. But now execution of the command (./share_my_internet.sh) does not enable internet sharing and moreover, host machine also loses internet access. Help would be appreciated.


2

AFAIK, NTP works on UDP. So you can try something like, sudo iptables -A OUTPUT -p udp --dport 123 --sport 1024:65535 -j ACCEPT sudo iptables -A INPUT -p udp --sport 123 --dport 1024:65535 -j ACCEPT


0

Allright, after a few tries I have finally achieved the goal. The key to the success were two rules below: -A PREROUTING ! -s 10.42.0.1/32 ! -d 10.42.0.1/32 -p tcp -m tcp --dport 53 -j DNAT --to-destination 10.42.0.1:53 -A PREROUTING ! -s 10.42.0.1/32 ! -d 10.42.0.1/32 -p udp -m udp --dport 53 -j DNAT --to-destination 10.42.0.1:53 I hope that this will ...


1

I've finally found a way to fix the issue I had.I found this article about iptables It helped me a lot to fix the issue. The only thing I did is run the command sudo iptables -F Doing that has allowed me to push again on remote repositories and thus using ssh. But I had to save that. For this I run this other command to make all the changements due to ...


3

Okay so if you use iptables from the command line you they don't get restored on reload or reboot. You can ever set your firewall rules with ufw instructions here or if you really need to use iptables you need to save your rules to file and have them restored back before your network comes up, you should also disable ufw as bodhi.zazen suggested so: sudo ...



Top 50 recent answers are included