Linux Netfilter discussions
 help / color / mirror / Atom feed
* Wired routing problem
@ 2003-11-14 21:18 star fire
  2003-11-14 22:04 ` Antony Stone
  0 siblings, 1 reply; 2+ messages in thread
From: star fire @ 2003-11-14 21:18 UTC (permalink / raw)
  To: iptables iptables

Dear group,

I intend to use iptables in order to limit access
trafic from our head office network(HON). The config
is as follows.

Firewall/Router

eth0
----
IP       10.2.248.1
MASK     255.255.248.0
B'CAST   10.2.255.255
Network  10.2.248.0

eth1
----
IP       172.16.1.1
MASK     255.255.0.0
B'CAST   172.16.255.255
Network  172.16.0.0


Client A
--------
IP       10.2.255.254
MASK     255.255.248.0
Gateway  10.2.248.1

Client B
--------
IP       172.16.1.3
MASK     255.255.0.0
Gateway  172.16.1.1

The firewall/router is a Redhat Linux 2.4.18
The situation where there are no iptables
running(stopped the service) and packet forwarding is
enables via sysctl.conf. As long as there are two(2)
machines as client A and B they connect to each other.
But then again when there is a CISCO route taken in as
a client, client A/B it does not ping to the router
from the other side. Could someone help me on this
issue.

Thanks sna regards

__________________________________
Do you Yahoo!?
Protect your identity with Yahoo! Mail AddressGuard
http://antispam.yahoo.com/whatsnewfree


^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: Wired routing problem
  2003-11-14 21:18 Wired routing problem star fire
@ 2003-11-14 22:04 ` Antony Stone
  0 siblings, 0 replies; 2+ messages in thread
From: Antony Stone @ 2003-11-14 22:04 UTC (permalink / raw)
  To: iptables iptables

On Friday 14 November 2003 9:18 pm, star fire wrote:

> Firewall/Router
>
> eth0
> IP       10.2.248.1
>
> eth1
> IP       172.16.1.1
>
> Client A
> IP       10.2.255.254
>
> Client B
> IP       172.16.1.3
>
> The firewall/router is a Redhat Linux 2.4.18
> The situation where there are no iptables
> running(stopped the service) and packet forwarding is
> enables via sysctl.conf. As long as there are two(2)
> machines as client A and B they connect to each other.

Okay, I understand what you mean by the above configuration, and it works.

> But then again when there is a CISCO route taken in as
> a client, client A/B it does not ping to the router
> from the other side.

Please explain where the Cisco router fits into the above network setup, what 
IP addresses it has, and what the routing table is on all machines involved.

Antony.

-- 

If the human brain were so simple that we could understand it,
we'd be so simple that we couldn't.
                                                     Please reply to the list;
                                                           please don't CC me.


^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2003-11-14 22:04 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2003-11-14 21:18 Wired routing problem star fire
2003-11-14 22:04 ` Antony Stone

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox