From: Nicolas Salvo <nicolas.salvo@gmail.com>
To: lartc@vger.kernel.org
Subject: [LARTC] Two class C subnets...
Date: Tue, 12 Jul 2005 21:34:43 +0000 [thread overview]
Message-ID: <c64c1531050712143475bab196@mail.gmail.com> (raw)
Hi!, I'm getting nuts with this so I really need your help...
I have a network in the 192.168.100.0/24 class C with the gw in
192.168.100.1, all the company works great with that scenario but now
we need to add more class C networks, now this is what I have:
2: eth0: <BROADCAST,MULTICAST,UP> mtu 1500 qdisc pfifo_fast qlen 1000
link/ether 00:08:a1:53:6d:51 brd ff:ff:ff:ff:ff:ff
inet 192.168.100.1/24 brd 192.168.100.255 scope global eth0
inet 192.168.2.1/24 brd 192.168.2.255 scope global eth0
0: from all lookup local
32763: from 192.168.100.0/24 to 192.168.2.0/24 lookup Monitors2
32764: from 192.168.2.0/24 to 192.168.100.0/24 lookup Monitors
32765: from xxx.xxx.xxx.xxx lookup ISP
32766: from all lookup main
32767: from all lookup 253
Monitors Table:
default via 192.168.100.1 dev eth0
Monitors2 Table:
default via 192.168.2.1 dev eth0
Main Table:
192.168.100.0/24 dev eth0 scope link
192.168.2.0/24 dev eth0 proto kernel scope link
xxx.xxx.xxx.xxx/24 dev eth2 scope link
127.0.0.0/8 dev lo scope link
default via xxx.xxx.xxx.xxx dev eth2
The only thing that I want is that if a packet comming from the
192.168.2.0/24 is going to some host in the 192.168.100.0/24 net, the
kerenl route those packets to 192.168.100.1 or in the other way, now,
I don't know what I'm doing wrong but that doesn't work for me, the
packets got lost somewhere, I'm a little lost with this so please can
anyone give me a hint?
Thanks
--
Nicolas A. Salvo
Capital Federal
Buenos Aires - Argentina
_______________________________________________
LARTC mailing list
LARTC@mailman.ds9a.nl
http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc
reply other threads:[~2005-07-12 21:34 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=c64c1531050712143475bab196@mail.gmail.com \
--to=nicolas.salvo@gmail.com \
--cc=lartc@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.