similar to: Redirecting port 8080 to port 80 - how to add in /etc/sysconfig/iptables file?

Hello again, unfortunately the following /etc/sysconfig/iptables file does not work: *nat :INPUT ACCEPT :OUTPUT ACCEPT :PREROUTING ACCEPT :POSTROUTING ACCEPT #-A PREROUTING -p tcp -m tcp --dport 80 -j REDIRECT --to-ports 8080 -A PREROUTING -p tcp -m tcp -d 144.76.184.154/32 --dport 80 -j REDIRECT --to-ports 8080 COMMIT *filter :INPUT DROP :OUTPUT ACCEPT :FORWARD DROP -A INPUT -m state --state

Hello Gordon and others On Tue, Jun 21, 2016 at 4:13 PM, Gordon Messmer <gordon.messmer at gmail.com> wrote: > On 06/21/2016 02:30 AM, Alexander Farber wrote: > >> -A PREROUTING -p tcp -m tcp -d 144.76.184.154/32 --dport 80 -j REDIRECT >> --to-ports 8080 >> > > > I think you have the ports backward, here. > here the problem description again: I have

On Tue, 2016-06-21 at 15:46 +0100, Always Learning wrote: > On Tue, 2016-06-21 at 16:24 +0200, Alexander Farber wrote: > > > *nat > > :INPUT ACCEPT > > :OUTPUT ACCEPT > > :PREROUTING ACCEPT > > :POSTROUTING ACCEPT > > -A PREROUTING -p tcp --dst 144.76.184.154 --dport 8080 -j REDIRECT > > --to-port 80 > >

On Mon, Jun 20, 2016 at 10:01 PM, Alexander Farber <alexander.farber at gmail.com> wrote: <cut> > > However I actually need my Jetty program to run at port 80 - so that users > behind corporate firewalls can connect too. > > The Jetty doc at > https://www.eclipse.org/jetty/documentation/current/setting-port80-access.html > suggests to run the command > > #

Hello fellow CentOS users, on a freshly installed 7.2 machine and after reading https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/7/html/System_Administrators_Guide/chap-Managing_Services_with_systemd.html I try to enable iptables with following commands: # cat /etc/centos-release CentOS Linux release 7.2.1511 (Core) # rpm -qa | grep iptables iptables-1.4.21-16.el7.x86_64

Am 2016-06-21 16:58, schrieb Always Learning: > On Tue, 2016-06-21 at 15:46 +0100, Always Learning wrote: > >> On Tue, 2016-06-21 at 16:24 +0200, Alexander Farber wrote: >> >> > *nat >> > :INPUT ACCEPT >> > :OUTPUT ACCEPT >> > :PREROUTING ACCEPT >> > :POSTROUTING ACCEPT >> > -A PREROUTING -p tcp --dst 144.76.184.154 --dport

On 06/21/2016 02:30 AM, Alexander Farber wrote: > -A PREROUTING -p tcp -m tcp -d 144.76.184.154/32 --dport 80 -j REDIRECT > --to-ports 8080 I think you have the ports backward, here.

On Tue, 2016-06-21 at 16:24 +0200, Alexander Farber wrote: > *nat > :INPUT ACCEPT > :OUTPUT ACCEPT > :PREROUTING ACCEPT > :POSTROUTING ACCEPT > -A PREROUTING -p tcp --dst 144.76.184.154 --dport 8080 -j REDIRECT > --to-port 80 http://www.karlrupp.net/en/computer/nat_tutorial # IMPORTANT: Activate IP-forwarding in the kernel! # Disabled by default! $> echo

Hello, I'm a user (and big fan) of CentOS 5.6 and in my /etc/sysconfig/iptables there are few blocking rules for some annoying visitors of my website (I run a card game there since many years and some people are "special"): *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT ACCEPT [294:35064] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i lo -j ACCEPT -A

Hello, how do you block incoming AND outgoing traffic to a site? I have 2 drop lines for a site in my /etc/sysconfig/iptables: *filter :INPUT DROP [0:0] :FORWARD DROP [0:0] :OUTPUT ACCEPT [294:35064] -A INPUT -m state --state RELATED,ESTABLISHED -j ACCEPT -A INPUT -i lo -j ACCEPT -A INPUT -s xx.xx.xx.0/24 -j DROP -A INPUT -d xx.xx.xx.0/24 -j DROP -A INPUT -p icmp -m icmp --icmp-type any -j

Hello, I hope my question is not off-topic here. On CentOS 7.2.1511 I have installed: haproxy-1.5.14-3.el7.x86_64 httpd-2.4.6-40.el7.centos.1.x86_64 The /etc/haproxy/haproxy.cfg binds HAProxy to ports 80 and 443 and accepts HTTPS to slova.de: defaults mode http option http-server-close option forwardfor except 127.0.0.0/8 option

Hi, I have Solr FTR working with dovecot, and need to do the commit and optimize recommended here: https://wiki.dovecot.org/Plugins/FTS/Solr Should this run as root, or as each mail user. The documentation above implies, but doesn't state, that it is root. The docs here are similar: http://grimore.org/networking/dovecot/full_text_search But the docs here say it has to be done for each

PuppetDB is operating fine, but I can''t figure out how to disable it from listening globally on TCP 1099 or 58722 How do I disable them from listening globally without having to resort to iptables? $ lsof -i -n -P | grep java | grep LISTEN java 30115 puppetdb 22u IPv6 119118 0t0 TCP *:1099 (LISTEN) java 30115 puppetdb 23u IPv6 117236 0t0 TCP *:58772

Hello Everyone, I have a small base of users (30), but a lot of emails. I have an error again when I am indexing a virtual folder with a large number of folders. I appreciate this is a special case, but I am using dovecot and solr as it is, according to the documentation, the favourite way. One user is using a large number of archives sub folders, by years, months and subfolders, since 5 years.

Hi Muzzafer, I get the error as specified below when i try to added it in as a field:- I dont think text_general is a valid field? HTTP ERROR 500 Problem accessing /solr/. Reason: {msg=SolrCore 'collection1' is not available due to init failure: Could not load conf for core collection1: Unknown fieldType 'text_general' specified on field text. Schema file is

This happens to Puppet 2.7.1 (both master and client). I have a file resource that I set to ensure => absent, Puppet removed it correctly with info line that it has a duplicate entry in the filebucket. I then changed the ensure => present, the agent run gave me following error: /usr/bin/puppet:19 err: /Stage[main]/Emb/File[/opt/jetty-distribution-7.4.2.v20110526.tar.gz]/ensure: change from

Puppet 3.3.1 // CentOS release 6.4 (Final) rpm -qa | grep puppet puppetlabs-release-6-7.noarch puppet-3.1.1-1.el6.noarch puppetdb-1.3.0-1.el6.noarch puppet-server-3.1.1-1.el6.noarch puppetdb-terminus-1.3.0-1.el6.noarch Installed from yum packages: Running Transaction Installing : puppetdb-1.3.0-1.el6.noarch

Hi, I have a proxy/firewall, I want to dnat requests for 193.205.140.106 on port 443 towards 10.2.15.23 and requests for 193.205.140.106 on ports 4330 and 3389 towards 10.2.15.25, these rules must apply from internet, loc and fw (some client use a proxy on fw to reach these servers) I have tried with the following rules: DNAT net dmz:10.2.15.23 tcp 443 -

https://bugzilla.netfilter.org/bugzilla/show_bug.cgi?id=429 ------- Additional Comments From laforge@netfilter.org 2006-01-25 11:00 MET ------- Please specifically tell us about the exact kernel version, any patches that you might have applied, and the iptables version that you're using. -- Configure bugmail: https://bugzilla.netfilter.org/bugzilla/userprefs.cgi?tab=email ------- You

I''ve just tried this (we assume /opt/jetty-6.1.26 already exists): file { "/opt/jetty-6.1.26": owner => "jetty", group => "users", recurse => true, } ... but it''s taking an *age*. What''s the Right Way? Cheers, Robert. -- You received this message because you are subscribed to the Google Groups