curaga


Group: Members
Posts: 2163
Joined: Feb. 2007 |
 |
Posted: Nov. 05 2007,15:55 |
 |
Hey, why would you want another ip through the wlan for the other comp?
I think there are two easy solutions: - Add the ip, with either the old wlan0:0 & wlan0:1 thingy, or with ip's label command - Bridge the eth0 to the wlan, so they appear to be on the same local network, with the other comp having it's own ip
-------------- There's no such thing as life. Those mean little jocks invented it ;) - Windows is not a virus. A virus does something!
|