> www.freebsd.org etc.)The IP packets with protocol of ESP results in
> my private subnet (172.16.x.x) still being in the IP source address
> field.
IPSec and NAT don't play together.
Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia
E-mail: [EMAIL PROTECTED], Tel: +
let me rephrase it. IPSec and NAT don't play together on FreeBSD. natd
does not know how to masqeurade ESP packets.
Blaz Zupan, Medinet d.o.o, Linhartova 21, 2000 Maribor, Slovenia
E-mail: [EMAIL PROTECTED], Tel: +386-2-320-6320, Fax: +386-2-320-6325
To Unsubscribe: send mail to [EMAIL PROTECT
> And before you suggest that the gif tunnels seen in all those IPSEC
> examples actually have anything to do with IPSEC tunnels, please try
> it and look again. It's completely uninvolved other than introducing
> a route as a side-effect.
I'm not sure what you mean here, but shouldn't the follo
> He was referring to using gif tunnels together with IPsec tunnel mode
> SAs (are you?) This "works" but precisely because of the side effect
> that Louis mentioned. A clean solution would user *either* IPIP tunnels
> (i.e. gif devices) and IPsec transport mode *or* IPsec tunnel mode (and
> no gi
> > Has anyone else seen this happen? Does anyone have a fix?
>
> Yes. These disappeared when I installed the latest rev. of the
> ORiNOCO driver/firmware. You'll need a Windoze machine to apply
> the update.
I'm experiencing the same problems. It started out on a new customers'
machine. We th
> new microwave oven nearby?
Don't think so. Also, putting the same card into one of those ethernet
converters (the one where you can put a WaveLAN card into the slot and you
just get ethernet out) makes it work just fine with the same firmware and in
the same environment. Sigh...
To Unsubscrib
