Subject: Re: How to fix packet destination address before RFC1122 dropping takes place?
To: Paulo Matias <syscoder@gmail.com>
From: Quentin Garnier <cube@cubidou.net>
List: tech-net
Date: 07/06/2007 22:49:02
--b1ERR0FXR0PvNIRE
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Fri, Jul 06, 2007 at 05:18:25PM -0300, Paulo Matias wrote:
> >
> >I just think it would be difficult to convince anyone that such
> >a change is suitable for all.
>=20
> Sure. It's the reason I asked if there was a solution that could be
> done without changing the code.
>=20
> So I think the best solution will be to develop a little program for
> capturing the packets via bpf, modifying them, and sending them to a
> TUN interface.
>=20
> Unfortunately, changing the kernel code is not a good choice in my
> case, because I'm developing a set of scripts for helping users of
> these mobile phones under BSD and Linux, and I must make it the
> simplest possible to the end-user.
>=20
> Thanks, now I know the solution I thought about (using bpf) was not a
> hack, but the way out for doing it under BSD solid TCP/IP stack.

You might have a way through hacking on pppd;  possibly using a plug-in.
I'm not 100% sure, but it's an idea.

--=20
Quentin Garnier - cube@cubidou.net - cube@NetBSD.org
"You could have made it, spitting out benchmarks
Owe it to yourself not to fail"
Amplifico, Spitting Out Benchmarks, Hometakes Vol. 2, 2005.

--b1ERR0FXR0PvNIRE
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.6 (NetBSD)

iQEVAwUBRo6qvdgoQloHrPnoAQJ02QgAoBYoxMPtycmU2t0xPNTpFpo+ZVjlUIhR
1lXQZdH6ZAyL1LFO6ccTcgH6YlL8Y+m3mWSept8WjQC8y2CZizqZhAaTi5mtD0cJ
P9KBNe813YdbXde35qZ4N6HESsRT5BrEu/xF1KIQkZh2vK7B80ct16qqwEDz4e/A
Jw4ShK8//k3BSjEp+1O4wCImBKH1HIJmtLDhmQeskTFBNLqzV784e39bYGzTJ0h5
g9sDVvI77BNpURW64tjFeK4jXn8BIk83pvsB7toQBQDz2l/LgSUD0V1Iw3dVopJ+
2Wqb4fDmZR5MKJwkFkQzube599e4NrzVJVus90fCDONj01NYnJjFBg==
=/uu6
-----END PGP SIGNATURE-----

--b1ERR0FXR0PvNIRE--