F
flekso
I've found this netsh script that allows me to install NAT on a WinXP
machine (undocummented feature):
netsh routing ip nat install
netsh routing ip nat add interface "external" full
netsh routing ip nat add interface "internal" private
....but now i have another problem, mainly because my internet
connection is based on dial-up PPPoE aDSL, so i have two icons in
network connections, one that represents a WAN miniport(this one i
click to connect), and the other that represents NIC that connects to
my aDSL modem.
The problem is my WAN miniport(PPPoE) gets assigned with the external
IP, and the NIC gets an automatic private address(whatever that means)
in the 169.254 range, but netsh won't accept the PPPoE as an interface(says
it not a real interface),
so i must use the one that's detected as local(at least by netlimiter)...
Any clues ? Maybe i can fool the netsh into thinking that PPPoE is a real
NIC ? Why are there two icons anyway ?
Thanks.
machine (undocummented feature):
netsh routing ip nat install
netsh routing ip nat add interface "external" full
netsh routing ip nat add interface "internal" private
....but now i have another problem, mainly because my internet
connection is based on dial-up PPPoE aDSL, so i have two icons in
network connections, one that represents a WAN miniport(this one i
click to connect), and the other that represents NIC that connects to
my aDSL modem.
The problem is my WAN miniport(PPPoE) gets assigned with the external
IP, and the NIC gets an automatic private address(whatever that means)
in the 169.254 range, but netsh won't accept the PPPoE as an interface(says
it not a real interface),
so i must use the one that's detected as local(at least by netlimiter)...
Any clues ? Maybe i can fool the netsh into thinking that PPPoE is a real
NIC ? Why are there two icons anyway ?
Thanks.