Re: NAT implementation in an IM driver
From: Valeriu Ilie (vali_il[nospam)
Date: 06/16/04
- Next message: Maxim S. Shatskih: "Re: NAT implementation in an IM driver"
- Previous message: Walter Oney: "Re: Smart Card USB Reader Driver Example"
- In reply to: Maxim S. Shatskih: "Re: NAT implementation in an IM driver"
- Next in thread: Maxim S. Shatskih: "Re: NAT implementation in an IM driver"
- Reply: Maxim S. Shatskih: "Re: NAT implementation in an IM driver"
- Messages sorted by: [ date ] [ thread ]
Date: Wed, 16 Jun 2004 10:27:50 -0400
> Forwarding the packet to another adapter will be done by the usual routing
code
> in the IP stack. The NAT must only translate the IP addresses and ports in
the
> header, and then deliver the packet to the IP stack.
OK. That's why I asked if the above protocols have to be involved in the
process of getting the destination MAC address. The IP routing from TCP/IP
protocol is taking care of sending ARPs if necessary according to the
routing table and building the new Ethernet header. But now comes the
difficult question. If for example you have 2 public interfaces (say 2
Internet providers) Windows will route the packet only on one interface, no
matter if the source IP is from one interface or another. Is it then right
to change the source MAC when you see the packet outgoing (assuming TCP/IP
is doing the routing)?
Valeriu
- Next message: Maxim S. Shatskih: "Re: NAT implementation in an IM driver"
- Previous message: Walter Oney: "Re: Smart Card USB Reader Driver Example"
- In reply to: Maxim S. Shatskih: "Re: NAT implementation in an IM driver"
- Next in thread: Maxim S. Shatskih: "Re: NAT implementation in an IM driver"
- Reply: Maxim S. Shatskih: "Re: NAT implementation in an IM driver"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
