Networking Forums

Networking Forums > Computer Networking > Linux Networking > Troubleshooting XP <-> Fedora 2 crossover cable connection.

Reply
Thread Tools Display Modes

Troubleshooting XP <-> Fedora 2 crossover cable connection.

 
 
Manas Ranade
Guest
Posts: n/a

 
      12-25-2004, 09:56 AM
Hi,

I have two machines with following eth configs:

Win XP Prof (no SP2):
IP: 192.168.0.10
Subnet mask: 255.255.255.0
No gateway
No DNS

Fedora Core2:
IP: 192.168.0.11
Subnet mask: 255.255.255.0
No gateway
No DNS
ip_forward=1

I can ping only from fedora, unable to ping from XP.

1. I havn't checked with another crossover cable since I can ping one
way. Would be a good idea to check another cable?

Pls share ur thoughts abt how I cud proceed with the troubleshooting. I
tried to search groups for other such incidents but did't come across
any. If there are/is any pls indicate.

Thanks,
Manas

 
Reply With Quote
 
 
 
 
Michael Heiming
Guest
Posts: n/a

 
      12-25-2004, 01:23 PM
In comp.os.linux.networking Manas Ranade <(E-Mail Removed)>:
> Hi,


> I have two machines with following eth configs:


> Win XP Prof (no SP2):
> IP: 192.168.0.10
> Subnet mask: 255.255.255.0
> No gateway
> No DNS


> Fedora Core2:
> IP: 192.168.0.11
> Subnet mask: 255.255.255.0
> No gateway
> No DNS
> ip_forward=1


> I can ping only from fedora, unable to ping from XP.


> 1. I havn't checked with another crossover cable since I can ping one
> way. Would be a good idea to check another cable?


If one way works, the other should be OK, since packets are
already going in both directions.

One reason might be you enabled firewalling on the fedora box,
which could disable ICMP echo requests. Try disabling the firewall
and retry.

[..]

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 153: Big to little endian conversion error
 
Reply With Quote
 
Manas Ranade
Guest
Posts: n/a

 
      12-26-2004, 02:04 AM
I did not find ipfwadm on the machine, whereis did not return anything.
Also system-config-securitylevel shows firewall disabled.
Do I need to recompile the kernel aftr setting ip_forward to 1?
Right now I've just set it in /etc/sysctl.conf and
/etc/sysconfig/network

Manas

 
Reply With Quote
 
Michael Heiming
Guest
Posts: n/a

 
      12-26-2004, 07:41 AM
In comp.os.linux.networking Manas Ranade <(E-Mail Removed)>:
> I did not find ipfwadm on the machine, whereis did not return anything.
> Also system-config-securitylevel shows firewall disabled.


There's no ipfwadm with FC2, firewall with kernel 2.4/2.6 is
called iptables, you can check for rules if any 'iptables -L'
('man iptables').

Should be per default controlled through:

/etc/init.d/iptables
Usage: /etc/init.d/iptables {start|stop|restart|condrestart|status|panic|save}


> Do I need to recompile the kernel aftr setting ip_forward to 1?


No, you don't even need to reboot to switch ip_forward on but
it's unrelated to your problem, since you just want to ping from
one host to another.

What does the following output:
cat /proc/sys/net/ipv4/icmp_echo_ignore_all

> Right now I've just set it in /etc/sysctl.conf and
> /etc/sysconfig/network


Sounds fine, but show us what you did exactly, if unsure.

--
Michael Heiming (X-PGP-Sig > GPG-Key ID: EDD27B94)
mail: echo (E-Mail Removed) | perl -pe 'y/a-z/n-za-m/'
#bofh excuse 412: Radial Telemetry Infiltration
 
Reply With Quote
 
Manas Ranade
Guest
Posts: n/a

 
      12-26-2004, 09:35 AM

iptables -L output is:

[root@man-machine manas]# /sbin/iptables -L
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

cat /proc/sys/net/ipv4/icmp_echo_ignore_all is displaying 0

/etc/sysctl.conf looks like:
# Kernel sysctl configuration file for Red Hat Linux
#
# For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and
# sysctl.conf(5) for more details.

# Controls IP packet forwarding
net.ipv4.ip_forward = 1
net.ipv4.ip_always_defrag = 1

# Controls source route verification
net.ipv4.conf.default.rp_filter = 0

# Controls the System Request debugging functionality of the kernel
kernel.sysrq = 0

# Controls whether core dumps will append the PID to the core filename.
# Useful for debugging multi-threaded applications.
kernel.core_uses_pid = 1

kernel.sem=100 32000 100 100
kernel.shmmax=2147483648
kernel.shmmni=4096
kernel.shmall=2097152
kernel.shmmin=1
net.ipv4.ip_local_port_range=1024 65000

/etc/sysconfig/network looks like:
NETWORKING=yes
FORWARD_IPV4=yes
HOSTNAME=man-machine

 
Reply With Quote
 
Manas Ranade
Guest
Posts: n/a

 
      12-26-2004, 12:07 PM
service stop iptables did the trick!
now I can ping both ways.
thanks a lot,
Manas

Manas Ranade wrote:
> iptables -L output is:
>
> [root@man-machine manas]# /sbin/iptables -L
> 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
>
> cat /proc/sys/net/ipv4/icmp_echo_ignore_all is displaying 0
>
> /etc/sysctl.conf looks like:
> # Kernel sysctl configuration file for Red Hat Linux
> #
> # For binary values, 0 is disabled, 1 is enabled. See sysctl(8) and
> # sysctl.conf(5) for more details.
>
> # Controls IP packet forwarding
> net.ipv4.ip_forward = 1
> net.ipv4.ip_always_defrag = 1
>
> # Controls source route verification
> net.ipv4.conf.default.rp_filter = 0
>
> # Controls the System Request debugging functionality of the kernel
> kernel.sysrq = 0
>
> # Controls whether core dumps will append the PID to the core

filename.
> # Useful for debugging multi-threaded applications.
> kernel.core_uses_pid = 1
>
> kernel.sem=100 32000 100 100
> kernel.shmmax=2147483648
> kernel.shmmni=4096
> kernel.shmall=2097152
> kernel.shmmin=1
> net.ipv4.ip_local_port_range=1024 65000
>
> /etc/sysconfig/network looks like:
> NETWORKING=yes
> FORWARD_IPV4=yes
> HOSTNAME=man-machine


 
Reply With Quote
 
 
 
Reply

Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Turning a crossover cable into a straight through cable Larry Roberts Windows Networking 8 02-18-2005 10:30 AM
Internet Connection Sharing works with crossover-cable but not Wireless. Network Wizard doesn't complete. Philip Herlihy Wireless Networks 0 07-01-2004 09:02 AM
Can I convert a FastCat5e network cable into a crossover cable? Sherri & Garry January Windows Networking 10 10-30-2003 04:19 AM
Can I convert a FastCat5e network cable into a crossover cable? Sherri & Garry January Home Networking 10 10-30-2003 04:19 AM
Can I convert a FastCat5e network cable into a crossover cable? Sherri & Garry January Windows Networking 8 10-30-2003 04:19 AM



1 2 3 4 5 6 7 8 9 10 11