are you using a proxy, or are you using nat?

for the moment I'm using .... nothing
you see ...

anything that will do the job
but can please somebody now precent a clear solution
to the problem ?
The linux machine needs to do eventually:
internet sharing
file sharing
web server (apache tomcat)
postgresql server

But first comes first, the internet sharing.
and still, if anybody is able to come online on msn to help me out,
please, this is day 5 I'm sitting here searching for a solution
what is needed to get one ?

there is a how to for ip masquerading here

http://www.ibiblio.org/pub/Linux/doc...ade-HOWTO.html

as for eth1, and the windows machine, i'd use static addresses for both of those. set the windows static to 192.168.0.3, netmask 255.255.255.0, to set the static address for eth1 in linux, open /ets/sysconfig/network-scripts/ifcfg-eth1 as root w/any editor, it should look something like this

DEVICE=eth1
BOOTPROTO=none
ONBOOT=yes
NETWORK=192.168.0.1
NETMASK=255.255.255.0
IPADDR=192.168.0.1
USERCTL=no

once that's done, bring the interface down then back up

ifconfig eth1 down
ifconfig eth1 up

now try to pinging from both directions. if this works all you have to get sorted is the connection sharing via ip masquerading.


for the file sharing you'll need to look into samba

http://us1.samba.org/samba/

but as you stated that'll be after sorting the first issues.
good luck.

ok, I gave windoze a static ip,
I get a timeout when I ping, but I must admit,
it's better then a "Destination host unreachable"

did you give eth1 a static ip? did you try pinging that ip?

yup
at least I thought so ...

[root@d5772aaf net]# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:05:5D:84:250
inet6 addr: fe80::205:5dff:fe84:25d0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1034 errors:0 dropped:0 overruns:0 frame:0
TX packets:81 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:248640 (242.8 Kb) TX bytes:4830 (4.7 Kb)
Interrupt:5 Base address:0xe400

it has no address, did you bring the interface down and then up? did you edit the file i posted earlier?

I saw the problem,
I just rebooted to be sure,
eth1 is back up and running

[root@d5772aaf pelgrim]# ifconfig eth1
eth1 Link encap:Ethernet HWaddr 00:05:5D:84:250
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::205:5dff:fe84:25d0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:10 errors:0 dropped:0 overruns:0 frame:0
TX packets:10 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:1129 (1.1 Kb) TX bytes:588 (588.0 b)
Interrupt:5 Base address:0xe400

can you please come online on msn
pelgrimforever@hotmail.com
this would be a lot more effeciënt and productive
PLEASE
I'm getting crazy about this whole linux mess ...

i'm reluctant to do that as access to someone elses machine is most suredly dangerous. i will however stay in this thread as long as it takes to get you going. be patient, think about how long it took you to learn the in and outs of windows, it didn't happen overnite, or in a week. now apply that mind set to linux. that should put a little perspective on it for you. that said, can you ping the internal network addresses from either box? try it and post back.

I can even ping with the windoze when linux is shut down ...
it gives a time out on 192.168.0.1

on the linux side,
ping 192.168.0.2 (the windoze ip adress)
just give no result at all, I guess the timeout is by default infinite ...

msn (it's called Kopete in mandrake KDE)
Internet - instant messaging
isn't exactly accessing someones machine, merely talking ...
I just want an iffecient way of talking.
What windoze concerns, I never learned it,
the wizards do the trick and I coudln't care less what happens in there,
as long as I can use it to program, same for linux.
Just like a car needs to ride, I couldn't care less about the engine ...

could you post the actual results of the ping command from both machines? i can use kopete, w/the icq protocol, i've never registered w/msn, didn't like the rules. i don't feel that taking the thread to a user to user level would benefit the forum as a whole. keeping the thread info here could benefit someone down the road.

ofcourse,
but now we get a message every 5 min,
the other way a message every 5 seconds ...

the ping results you got:
from windoze to linux
Requst time out

from linux to windoze
abosolutely nothing anymore, the thing waits endlessly without giving any message,
no command prompt, nothing ...

it's almost 1.30 in the morning here,
ever online during the day ?

it's only 7:20 p.m here, it is the day here, sorry. from the linux machine, issue

iptables -F

that should ensure that all firewall rules are flushed. this is just to be sure that it's not firewall related. with both machines up and running, try again from linux

ifconfig -a

route -n

then from windows

ipconfig /all

and

route print

post all the results.

there we go again :+)

eth0 Link encap:Ethernet HWaddr 00:50:BA:EA:6D:1C
inet addr:213.119.42.175 Bcast:213.119.42.255 Mask:255.255.255.0
inet6 addr: fe80::250:baff:feea:6d1c/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:710 errors:0 dropped:0 overruns:0 frame:0
TX packets:784 errors:0 dropped:0 overruns:0 carrier:0
collisions:45 txqueuelen:1000
RX bytes:224008 (218.7 Kb) TX bytes:103387 (100.9 Kb)
Interrupt:11 Base address:0xd400

eth1 Link encap:Ethernet HWaddr 00:05:5D:84:250
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::205:5dff:fe84:25d0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:9 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:546 (546.0 b)
Interrupt:5 Base address:0xe400

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:62 errors:0 dropped:0 overruns:0 frame:0
TX packets:62 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:3914 (3.8 Kb) TX bytes:3914 (3.8 Kb)

sit0 Link encap:IPv6-in-IPv4
NOARP MTU:1480 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)

Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.0.0 0.0.0.0 255.255.255.0 U 0 0 0 eth1
213.119.42.0 0.0.0.0 255.255.255.0 U 0 0 0 eth0
127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0 lo
0.0.0.0 213.119.42.1 0.0.0.0 UG 0 0 0 eth0


nothing changed really on the windows side,
so I refer to my earlier post for that

route print

Destination netmask gateway interface metric
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.0.0 255.255.255.0 192.168.0.2 192.168.0.2 20
192.168.0.2 255.255.255.255 127.0.0.1 127.0.0.1 30
192.168.0.255 255.255.255.255 192.168.0.2 192.168.0.2 30
224.0.0.0 224.0.0.0 192.168.0.2 192.168.0.2 30
255.255.255.255 255.255.255.255 192.168.0.2 192.168.0.2 30

Persistent routes
none

Headache: YES :+)