is greatly
appreciated.
Regards
Jennifer Botten
ETECH
-Original Message-
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of Tom H
Sent: 24 July 2011 02:57 PM
To: CentOS mailing list
Subject: Re: [CentOS] VLAN's
On Sat, Jul 23, 2011 at 3:26 PM, John R
On Sat, July 23, 2011 15:02, John R Pierce wrote:
On 07/23/11 10:22 AM, Kristopher Kane wrote:
this sort of thing really belongs on an iproute2/netfilter mail
list, however, as its not at all centos specific.
So John, exactly what is CentOS specific? Should I only read the
emails with
On Sat, Jul 23, 2011 at 3:26 PM, John R Pierce pie...@hogranch.com wrote:
On 07/23/11 12:09 PM, Tom H wrote:
Even after this explanation I don't understand your objection to
helping someone with a firewall and routing issue on a CentOS box. You
might have a point if the executables didn't
On Friday, July 22, 2011 10:55 PM, Jennifer Botten wrote:
Hi Julio,
-A FORWARD -i eth2.2 -s 192.168.1.0/24 -d 10.30.4.28 -p udp -j ACCEPT
-A FORWARD -i eth2.2 -s 192.168.1.0/24 -d 192.168.0.0/24 -p tcp -j ACCEPT
-A FORWARD -i eth1 -s 192.168.0.0/24 -d 192.168.1.0/24 -p tcp -j ACCEPT
-A
this sort of thing really belongs on an iproute2/netfilter mail list,
however, as its not at all centos specific.
So John, exactly what is CentOS specific? Should I only read the emails
with release speculation?
-Kris
___
CentOS mailing list
On 07/23/11 10:22 AM, Kristopher Kane wrote:
this sort of thing really belongs on an iproute2/netfilter mail list,
however, as its not at all centos specific.
So John, exactly what is CentOS specific? Should I only read the
emails with release speculation?
things related to the
On Sat, Jul 23, 2011 at 3:02 PM, John R Pierce pie...@hogranch.com wrote:
On 07/23/11 10:22 AM, Kristopher Kane wrote:
this sort of thing really belongs on an iproute2/netfilter mail list,
however, as its not at all centos specific.
So John, exactly what is CentOS specific? Should I only
On 07/23/11 12:09 PM, Tom H wrote:
Even after this explanation I don't understand your objection to
helping someone with a firewall and routing issue on a CentOS box. You
might have a point if the executables didn't come from packages in the
canonical CentOS repo.
I'm writing my doctoral
On Sat, 2011-07-23 at 12:26 -0700, John R Pierce wrote:
On 07/23/11 12:09 PM, Tom H wrote:
Even after this explanation I don't understand your objection to
helping someone with a firewall and routing issue on a CentOS box. You
might have a point if the executables didn't come from
Hi,
I have a firewall running IPTABLES. I have tried to route sip traffic from
my WAN(eth3) interface to a VLAN(eth2.2) interface, however the data will
not route to the VLAN it keeps routing to the default interface(eth2). Does
anyone have an idea as to what I need to look for?
Regards
Hi Jennifer,
Could you copy the iptables rules?
Julio
On 7/22/2011 8:49 AM, Jennifer Botten wrote:
Hi,
I have a firewall running IPTABLES. I have
tried to route
On 7/22/2011 8:49 AM, Jennifer Botten wrote:
Hi,
I have a firewall running IPTABLES. I have tried to route sip traffic
from my WAN(eth3) interface to a VLAN(eth2.2) interface, however the
data will not route to the VLAN it keeps routing to the default
interface(eth2). Does anyone have an
-A POSTROUTING -m helper --helper sip -m state --state ESTABLISHED,RELATED
Thanks
Jennifer
From: centos-boun...@centos.org [mailto:centos-boun...@centos.org] On Behalf
Of cbul...@gmail.com
Sent: 22 July 2011 04:37 PM
To: centos@centos.org
Subject: Re: [CentOS] VLAN's
Hi Jennifer
On 07/22/11 6:49 AM, Jennifer Botten wrote:
Hi,
I have a firewall running IPTABLES. I have tried to route sip traffic
from my WAN(eth3) interface to a VLAN(eth2.2) interface, however the
data will not route to the VLAN it keeps routing to the default
interface(eth2). Does anyone have an
On 7/22/2011 1:17 PM, John R Pierce wrote:
I have a firewall running IPTABLES. I have tried to route sip traffic
from my WAN(eth3) interface to a VLAN(eth2.2) interface, however the
data will not route to the VLAN it keeps routing to the default
interface(eth2). Does anyone have an idea as to
On 07/22/11 11:29 AM, Les Mikesell wrote:
You need this because you want to route based on the source address, not
the destination. That might be what the OP wants too, but it's not
clear from the question and doesn't have anything to do with the
interfaces being vlans.
well, I suspect he
16 matches
Mail list logo
