Re: [9fans] /net/ip*

Re: [9fans] /net/ip*

[nigel]

[-- Attachment #1: Type: text/plain, Size: 42 bytes --]

Serves my right for trusting the gnet.


[-- Attachment #2: Type: message/rfc822, Size: 1679 bytes --]

From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] /net/ip*
Date: Fri, 26 Jan 2001 15:52:08 +0100
Message-ID: <00e901c087a7$b09f6c20$8692fea9@coma>

> If I were Russian, I might say "niet".

nyet, although it is written:

    HET

H = n
E = ye
T = t

i did a bit of russian and can still read cyrillic, slowly :-)

ps. i lucked out that i could render it in ascii.

Re: [9fans] /net/ip*

[nigel]

[-- Attachment #1: Type: text/plain, Size: 42 bytes --]

Serves me right for trusting the gnet.


[-- Attachment #2: Type: message/rfc822, Size: 1679 bytes --]

From: "Boyd Roberts" <boyd@planete.net>
To: <9fans@cse.psu.edu>
Subject: Re: [9fans] /net/ip*
Date: Fri, 26 Jan 2001 15:52:08 +0100
Message-ID: <00e901c087a7$b09f6c20$8692fea9@coma>

> If I were Russian, I might say "niet".

nyet, although it is written:

    HET

H = n
E = ye
T = t

i did a bit of russian and can still read cyrillic, slowly :-)

ps. i lucked out that i could render it in ascii.

Re: [9fans] /net/ip*

[Boyd Roberts]

> If I were Russian, I might say "niet".

nyet, although it is written:

    HET

H = n
E = ye
T = t

i did a bit of russian and can still read cyrillic, slowly :-)

ps. i lucked out that i could render it in ascii.

Re: [9fans] /net/ip*

[nigel]

[-- Attachment #1: Type: text/plain, Size: 42 bytes --]

If I were Russian, I might say "niet".


[-- Attachment #2: Type: message/rfc822, Size: 1569 bytes --]

From: splite@purdue.edu
To: 9fans@cse.psu.edu
Subject: Re: [9fans] /net/ip*
Date: Fri, 26 Jan 2001 09:34:28 -0500
Message-ID: <20010126093428.A4563@sigint.cs.purdue.edu>

On Thu, Jan 25, 2001 at 07:23:35PM -0500, presotto@plan9.bell-labs.com wrote:
> The way to build a nat with plan 9 is to set up 2 ip stacks, open

Not to pick a nit, but should a nut with a Gnot on the 'net build a nat?

Re: [9fans] /net/ip*

[splite]

On Thu, Jan 25, 2001 at 07:23:35PM -0500, presotto@plan9.bell-labs.com wrote:
> The way to build a nat with plan 9 is to set up 2 ip stacks, open

Not to pick a nit, but should a nut with a Gnot on the 'net build a nat?

Re: [9fans] /net/ip*

[presotto]

[-- Attachment #1: Type: text/plain, Size: 239 bytes --]

The way to build a nat with plan 9 is to set up 2 ip stacks, open
a pkt interface on each one, and start a process that does
the translation by xfering packets from one to the other:

Look at ppp to see how to use a packet interface.

[-- Attachment #2: Type: message/rfc822, Size: 1796 bytes --]

From: Latchesar Ionkov <lucho@gmx.net>
To: 9fans@cse.psu.edu
Subject: [9fans] /net/ip*
Date: Thu, 25 Jan 2001 17:40:15 -0500
Message-ID: <20010125174015.A7009@gmx.net>

Hi,

I am trying to write a simple program that does network address translation in
Plan9. I am using /net/ipmux to get the packets I need to modify, but I
don't quite understand where to write these packets after I modify them :)

So far I see two choices: /net/ipmux/<nn>/data and /net/ipifc/<nn>/data. I
tried both of them but I don't see any packet going out or I see the packet
receiving from the filter again.

Any ideas what should I do?

Thanks,
	Lucho

[9fans] /net/ip*

[Latchesar Ionkov]

Hi,

I am trying to write a simple program that does network address translation in
Plan9. I am using /net/ipmux to get the packets I need to modify, but I
don't quite understand where to write these packets after I modify them :)

So far I see two choices: /net/ipmux/<nn>/data and /net/ipifc/<nn>/data. I
tried both of them but I don't see any packet going out or I see the packet
receiving from the filter again.

Any ideas what should I do?

Thanks,
	Lucho