Re: [CentOS] snat packet going out a bridge

2016-01-21 Thread Eliezer Croitoru
On 20/01/2016 19:55, Steve Clark wrote: So I want traffic coming in eth5 with 10.10.0.x addresses to be source natted to 192.168.100.3. But my iptables nat statement never gets hit. Chain POSTROUTING (policy ACCEPT 172 packets, 31384 bytes) pkts bytes target prot opt in out source des

Re: [CentOS] snat packet going out a bridge

2016-01-21 Thread Gordon Messmer
On 01/21/2016 03:49 AM, Steve Clark wrote: Thanks, but forwarding is turned on and my FW rules are empty. Try specifying the physical device the packets are going out, rather than the bridge, in your postrouting rule. Apparently you also need an ebtables rule to prevent the return packets

Re: [CentOS] snat packet going out a bridge

2016-01-21 Thread Steve Clark
On 01/20/2016 04:21 PM, Gordon Messmer wrote: On 01/20/2016 09:55 AM, Steve Clark wrote: Any ideas? IP forwarding needs to be enabled, and you also need rules in your FORWARD chain to allow the packets. Thanks, but forwarding is turned on and my FW rules are empty. Chain INPUT (policy ACCEP

Re: [CentOS] snat packet going out a bridge

2016-01-20 Thread Gordon Messmer
On 01/20/2016 09:55 AM, Steve Clark wrote: Any ideas? IP forwarding needs to be enabled, and you also need rules in your FORWARD chain to allow the packets. ___ CentOS mailing list CentOS@centos.org https://lists.centos.org/mailman/listinfo/centos

[CentOS] snat packet going out a bridge

2016-01-20 Thread Steve Clark
Hi List, I am running into a problem where I have 2 interfaces bridged with and ip address assigned. I have another interface in which traffic has ingress traffic that needs to go out the bridged interface. I am trying unsuccessfully to SNAT the traffic leaving the bridge interface to its ass

Re: [CentOS] SNAT Logging

2013-02-27 Thread Robert
On Wed, 27 Feb 2013 15:45:01 -0300 (BRT) Antonio da Silva Martins Junior wrote: > Hi All, > >I'm running our network with an 10/8 IPv4 subnets, with an SNAT catch all > rule on the iptables firewall to the world. > >Is there a pratical way to log each connection? Maybe an "automatic >

[CentOS] SNAT Logging

2013-02-27 Thread Antonio da Silva Martins Junior
Hi All, I'm running our network with an 10/8 IPv4 subnets, with an SNAT catch all rule on the iptables firewall to the world. Is there a pratical way to log each connection? Maybe an "automatic hotspot" wich will assign an "external" IP to each "internal" one, and log it. What are you u

Re: [CentOS] SNAT

2010-01-10 Thread Agile Aspect
On Sun, Jan 10, 2010 at 6:33 AM, David Hláčik wrote: > Hello I will briefly draw the situation > > Router with one interface eth0 , to local network 10.123.0.0/16 > > on a local network ADSL modem with IP  10.123.10.11 > > I want to use 10.123.10.11 as a connection to internet . > > Because of tha

Re: [CentOS] SNAT

2010-01-10 Thread David Hláčik
Hello, CentOS 5.4, but I believe there will be no difference. Best, David On Sun, Jan 10, 2010 at 4:07 PM, Alexander Dalloz wrote: > Am 10.01.2010 15:33, schrieb David Hláčik: > >> Hello I will briefly draw the situation > > [ ... ] > >> Please help, >> >> Thank you in advance. >> >> David >

Re: [CentOS] SNAT

2010-01-10 Thread Alexander Dalloz
Am 10.01.2010 15:33, schrieb David Hláčik: > Hello I will briefly draw the situation [ ... ] > Please help, > > Thank you in advance. > > David The router runs CentOS or Fedora? Because you are sending your mails to both mailing lists. Alexander _

Re: [CentOS] SNAT

2010-01-10 Thread David Hláčik
*** Sorry for mistake I have configured static route on ADSL modem "10.123.0.0/16 via > 10.123.10.1" which ensures traffic comming from internet will ge to > my router 10.123.10.1 is address of eth0 on my router. On Sun, Jan 10, 2010 at 3:33 PM, David Hláčik wrote: > Hello I will briefly draw t

[CentOS] SNAT

2010-01-10 Thread David Hláčik
Hello I will briefly draw the situation Router with one interface eth0 , to local network 10.123.0.0/16 on a local network ADSL modem with IP 10.123.10.11 I want to use 10.123.10.11 as a connection to internet . Because of that I have created default route "ip route add default via 10.123.10.1

Re: [CentOS] SNAT question

2009-11-28 Thread Peter Peltonen
Hi, On Thu, Nov 26, 2009 at 1:17 AM, Tait Clarridge wrote: >> >> wrote: >> >>> Hi, >> >>> >> >>> I am unable to get my LAN masqueraded using SNAT with CentOS 5.3 and >> >>> iptables. >> >>> >> >>> I have the following setup: >> >>> >> >>> eth0: connects to internet with static public IP 1.2.3.1

Re: [CentOS] SNAT question

2009-11-25 Thread Tait Clarridge
On Thu, 2009-11-26 at 00:58 +0200, Peter Peltonen wrote: > On Mon, Nov 23, 2009 at 4:31 PM, Peter Peltonen > wrote: > > Hi, > > > > On Mon, Nov 23, 2009 at 4:15 PM, Giovanni Tirloni wrote: > >> On Mon, Nov 23, 2009 at 12:10 PM, Peter Peltonen > >> wrote: > >>> Hi, > >>> > >>> I am unable to get

Re: [CentOS] SNAT question

2009-11-25 Thread Peter Peltonen
On Mon, Nov 23, 2009 at 4:31 PM, Peter Peltonen wrote: > Hi, > > On Mon, Nov 23, 2009 at 4:15 PM, Giovanni Tirloni wrote: >> On Mon, Nov 23, 2009 at 12:10 PM, Peter Peltonen >> wrote: >>> Hi, >>> >>> I am unable to get my LAN masqueraded using SNAT with CentOS 5.3 and >>> iptables. >>> >>> I ha

Re: [CentOS] SNAT question

2009-11-23 Thread Peter Peltonen
Hi, On Mon, Nov 23, 2009 at 4:15 PM, Giovanni Tirloni wrote: > On Mon, Nov 23, 2009 at 12:10 PM, Peter Peltonen > wrote: >> Hi, >> >> I am unable to get my LAN masqueraded using SNAT with CentOS 5.3 and >> iptables. >> >> I have the following setup: >> >> eth0: connects to internet with static

Re: [CentOS] SNAT question

2009-11-23 Thread Giovanni Tirloni
On Mon, Nov 23, 2009 at 12:10 PM, Peter Peltonen wrote: > Hi, > > I am unable to get my LAN masqueraded using SNAT with CentOS 5.3 and iptables. > > I have the following setup: > > eth0: connects to internet with static public IP 1.2.3.1 (obscured > here for privacy) > eth1: connects to DMZ with s

[CentOS] SNAT question

2009-11-23 Thread Peter Peltonen
Hi, I am unable to get my LAN masqueraded using SNAT with CentOS 5.3 and iptables. I have the following setup: eth0: connects to internet with static public IP 1.2.3.1 (obscured here for privacy) eth1: connects to DMZ with static public IP 1.2.3.2 (obscured here for privacy) eth2: connects to LA