[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: How to talk ethernet to windows




Colin Paul Adams wrote:
>>>>>> "Kevin" == Kevin Martin <kevintm ameritech net> writes:
>>>>>>             
>
>     Kevin> Colin Paul Adams wrote:
>     >> I have a fedora 9 box which is connected to my wireless network
>     >> (via network manager).
>     >> 
>     >> It also has an ethernet port, and there is a windows xp
>     >> professional box in the same room with an ethernet port too. I
>     >> have a cable to connect the two boxes together.
>     >> 
>     >> So I want to set up a lan with the linux end addressed as
>     >> 10.0.0.1 and the windows end addressed as 10.0.0.2, and a
>     >> netmask of 255.255.255.0. And for the windows box to be able to
>     >> connect to the internet by routing through to the linux box,
>     >> and thence through to the wireless network.
>     >> 
>     >> How do I configure the two boxes to do this?
>     >> 
>     Kevin> Are you asking *how* to setup the static addresses for the
>     Kevin> interfaces and then the routing, or just the routing?  If
>
> Both, really.
>
>     Kevin> it's just the routing, on the windows box (from a cmd.exe
>     Kevin> window) do a "route -p add net 0.0.0.0 mask 255.255.255.0
>     Kevin> 10.0.0.1" (that will setup the static route to route
>     Kevin> everything thru the Linux ip address and save it for future
>
> It doesn't. It responds with:
>
> Bad destination address netA
>   
Actually, I think it's "route add 0.0.0.0 mask 0.0.0.0 10.0.0.1"...take
a look at netstat -rn (to see what routes are set) and do a "route -?"
to see what the route syntax is (for example, you may not need the "mask
0.0.0.0" when setting the default route, I don't know for sure).
>     Kevin> traffic, and you'll need to setup ip forwarding in
>     Kevin> /proc/sys/net/ipv4/ip_forward.  
>
> How do I do that?
>   
echo 1 > /proc/sys/net/ipv4/ip_forward

FWIW, I don't know if that will stay on a reboot so you may need to
setup that command in /etc/rc.d/rc.local so it's replaced each time.
>     Kevin> As to setting up the static routes, in Windows the easiest way to do it is with the
>     Kevin> Networking gui,
>
> I thought that was what the above command was supposed to do. What
> else do I need to do?
>   
My apologies, I meant to say static ip address with the GUI, not static
routes.
> P.S. It is Chinese-language Windows (for my wife - I wouldn't dream of
> using windows myself), and I can't read Chinese, so I have to get her
> to translate, and she doesn't understand computer technical terms.
> So command lines would be easier for me.
>   
Well, there's a command called netsh that can apparently do this but it
requires a service called remoteaccess to be running which doesn't
appear to exist on Windows desktop O.S.'s.  That being said, it's the
GUI or nothing.
>     Kevin>  in linux you can use Network Manager (yuk)
>     Kevin> or set it up in the /etc/sysconfig/networking and
>     Kevin> /etc/sysconfig/networking-scripts area.
>
> What needs setting up?
>   


[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]