Home network

[krneki]

Hello!
I have two computers at home. First works as a router and server (OS is Fedora Core 3 without graphics) and the second one is main computer (OS is Windows XP SP2) so connection looks like this: modem -> linux -> windows. Internet and home network were working fine for three months until yesterday when suddenly modem died and also my home network (I wasn't at home). I changed modem with new one and internet is working fine now on Fedora 3 but I can't figure out what is wrong with home network because internet on WinXP is simply not working. However, I can still ping from WinXP to Linux and from Linux to WinXP. I can also connect with putty to Linux router but internet on WinXP box is still not working (there are 0 received packages).
I don't have Samba on linux, I only configured network by one tutorial (which I can't find anymore).
Do you have any ideas what should I do now? I didn't change any network settings last month.

Thank you very much,
regards krneki

[Brian1]

Can the WinXP box ping and external web site IP like Google. http://216.239.39.99/ . If it can then I would say and issue with the dns settings ethier in the FC3 box or Winxp box. Not sure of your setup whether you define DNS IP or get it automatically. If you can not ping the external IP like google then I would say ip masquerading is not enabled.

Brian1

[jcliburn]

From FC3 machine, post the results of the command "/sbin/ifconfig -a". Also make sure /proc/sys/ipv4/ip_forward is set to "1". If it isn't, your FC3 box won't forward packets to or from your XP box.

[krneki]

It's even worse now. I can now ping from Linux PC to WinXP PC but I can't ping from WinXP to Linux. I receive message: Request timed out.
However, ip_forward is already set to 1 and I don't have firewall.

[jcliburn]

Again, post the results of the command "/sbin/ifconfig -a" as run from the FC3 machine. We can't help unless we know how your network is configured.

[wneumann]

Sounds as if your Xp box is expecting to find your linux box or router at some fixed ip address that has changed because of the router change. With any luck, all you have to do is change your settings on the Xp box.

For instance older netgear routers used 192.168.0.1 while Linksys and newer netgear are usually 192.168.1.1.

But when you originaly set stuff up you probably wrote some iptables rules for masquerading, and there is a slight chance you have some hard-coded ip addresses in there. You could check that too.

[krneki]

There was a mess in eth0 with IP's. IP for internet was 192.168.0.2 but it was still working properly. However I changed that IP to my static IP and I can ping from Windows PC to Linux PC again (internet is still not working).

Anyway, here are some informations:

route -e:

Kernel IP routing table
Destination Gateway Genmask Flags MSS Window irtt Iface
BSN-access.dsl. * 255.255.255.255 UH 0 0 0 ppp0
192.168.0.0 * 255.255.255.0 U 0 0 0 eth1
193.77.90.0 * 255.255.255.0 U 0 0 0 eth0
default BSN-access.dsl. 0.0.0.0 UG 0 0 0 ppp0

ifconfig (linux):

eth0 Link encap:Ethernet HWaddr 000F:E8:13:55
inet addr:193.77.90.205 Bcast:193.77.90.255 Mask:255.255.255.0
inet6 addr: fe80::2c0:dfff:fee8:1355/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:6000 errors:0 dropped:0 overruns:0 frame:0
TX packets:6662 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:740924 (723.5 KiB) TX bytes:867567 (847.2 KiB)
Interrupt:9 Base address:0xdd80

eth1 Link encap:Ethernet HWaddr 000F:03:18:3E
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2c0:dfff:fe03:183e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2000 errors:0 dropped:0 overruns:0 frame:0
TX packets:98 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:162084 (158.2 KiB) TX bytes:10333 (10.0 KiB)
Interrupt:10 Base address:0xda00

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:18 errors:0 dropped:0 overruns:0 frame:0
TX packets:18 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1629 (1.5 KiB) TX bytes:1629 (1.5 KiB)

ppp0 Link encap:Point-to-Point Protocol
inet addr:193.77.90.205 P-t-P:213.250.19.90 Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1492 Metric:1
RX packets:4391 errors:0 dropped:0 overruns:0 frame:0
TX packets:5382 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:3
RX bytes:458859 (448.1 KiB) TX bytes:590301 (576.4 KiB)

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)

ipconfig (windows):

Windows IP Configuration

Host Name . . . . . . . . . . . . : domen
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC
Physical Address. . . . . . . . . : 00-04-61-4A-23-B6
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 193.189.160.11
193.189.160.12

iptables -L (linux):

Chain INPUT (policy ACCEPT)
target prot opt source destination

Chain FORWARD (policy ACCEPT)
target prot opt source destination

Chain OUTPUT (policy ACCEPT)
target prot opt source destination

[jcliburn]

Okay, looks good. Now you need to set up IP forwarding and NAT on the Fedora machine. See pparks1 post here: http://forums.fedoraforum.org/forum/...d.php?t=116672 .