Re: Can Ebtables help with this?

Hi,

(1) 192.168.250.181 ----------  192.168.18.1  (2)
192.168.250.191  --------- 192.168.250.254 (3)

Certainly, if (2) is a Linux box, we can do many things of it.

The IP on (2) is not reversed. It is stated indeed correctly. It is
impossible to ping the other segment of the network. BUT, I have to make it
possible, no NAT can be done on (2)

In short:-
(A) I need to ping 192.168.250.191 from 192.168.250.181 (making it pingable)
(B) I am not allowed to do NAT on (2)
(C) I need to find a way doing it :)

Really hope that this clear things up a little bit more :) Thank you all.

Thank you,
Calvin Kaiwen



----- Original Message -----
From: "tony mancill" <tony-/[email protected]>
To: "pevee" <[email protected]>
Cc: <[email protected]>
Sent: Friday, November 08, 2002 12:49 PM
Subject: Re: [Ebtables-devel] Can Ebtables help with this?


> I'll bite, just because now I'm wondering what's intended by the question.
> If I grok the diagram correctly, you have a client system, (1), attached
> to a segment where there is a dual-attached router or machine (2), that is
> then attached to the segment where the default gateway is.  (I'm not sure
> yet why the gateway is in the picture, but maybe it figures into problem
> statement somehow.)
>
> If I had to guess, I'd say that you want to assign a public IP to (1) so
> that it's accessible from the outside, but it's behind router (2), of the
> 192.168.18.1/24 interface.  (Are the IP addresses the left and right of
> (2) perhaps reversed?)  And furthermore, you aren't allowed to touch (2)?
> The easiest thing to do would be to drop a box on that "external" segment,
> give it the public IP of (1), and then use redir or transproxy or DNAT
> rules or whatever you want to get the traffic over to the "real" (1) box,
> which will have an internal address.
>
> Is it only that you can't do NAT on system (2)?  What options do you have
> for (2)?  If it's a Linux box, there are lots of ways to solve (my guess
> at) your problem.
>
> Cheers,
> tony
>
> On Wed, 6 Nov 2002, Bart De Schuymer wrote:
>
> > On Wednesday 06 November 2002 10:31, pevee wrote:
> > > Hi,
> > >
> > > I have a test case as followed:-
> > >
> > > (1) 192.168.250.131  ---------------------  192.168.18.1 (2)
192.168.250.57
> > > ---------------  (gateway)
> > >
> > > (a) user (1) will be using a public IP
> > > (b) I am not allowed to do NAT (masquerading) on (2)
> > > (c) Can ebtables help me to enable user (1) to ping to (2)
192.168.250.57?
> > >
> > > If not, is there any other way? IP Aliases? Port Translation?
> >
> > It's probably just me but I don't have a clue what your question is.
> >
> > --
> > cheers,
> > Bart
>
>
>
> -------------------------------------------------------
> This sf.net email is sponsored by: See the NEW Palm
> Tungsten T handheld. Power & Color in a compact size!
> http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en
> _______________________________________________
> Ebtables-devel mailing list
> [email protected]
> https://lists.sourceforge.net/lists/listinfo/ebtables-devel
>



-------------------------------------------------------
This sf.net email is sponsored by: See the NEW Palm 
Tungsten T handheld. Power & Color in a compact size!
http://ads.sourceforge.net/cgi-bin/redirect.pl?palm0001en