MandrivaThis Forum is for the discussion of Mandriva (Mandrake) Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606
Rep:
Good to know you are still around. Will still try to help if I can.
Cannot do DIY though. Computer never need fixing, and learning them is immediate.
It is all well known. You have all my support
Grout is great, grub is better
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606
Rep:
hello? Anybody there? ny progress with this home lan?
I spent 20 min trying to connect two linux (PC to PC) machines.
I failed miserably. It will be a while before I have a chance to try again.
I used a patch cable. So I will stand a better chance with crossover
I will keep you posted. When this work I will be better able to help.
Emmanueluk: It certainly must be possible to make a network with a crossover cable and 2 dedicated NIC's in Linux. It seems to be very easy in Windows and there is LinNeighborhood (spelling?) to let Linux and Windows coexist in an ethernet lan. It's all there if you can figure it out!
The trouble I guess is everybody's boxes are different and there are so many different flavours of Linux.
I have bought a Mercury 10/100Mbps Fast Ethernet Switch (£15) which I hoped would make things go 'click'...
And they have... I can see the green lights on in the switch showing the cable modem and the 2 NIC's are 'connected' via the switch - but the red lights are still on in the NIC's. So they are connected in a hardware sense but cannot communicate. (?)
I think it is now down to the firewall rules but cannot figure it out. Even if I remove the firewalls (on each box) the boxes don't connect. And I see from reading on the web that you actually need the firewalls but set up to allow the connection.
bobbelfield: I have also been going over the IP addresses etc that you told me but it is just not going 'click'.
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606
Rep:
I have a DI-604 router at home. It went click.
But this is more than a switch, it runs dhcp so each nic is given an IP
by the router.
Thanks for the link. I will read that document again.
The nic to nic direct is another challenge.
Back to your problem
Assuming you have allowed everything in each firewall,
and that the security setting is not disabling ping response
(cannot remember where this is)
what does route -n returns?
does ping say "host unreachable?"
PS: I remember
cat /proc/sys/net/ipv4/ip_forward
if 0 then enable with
echo 1 > /proc/sys/Net/ipv4/ip_forward
Last edited by Emmanuel_uk; 03-14-2006 at 11:39 AM.
Distribution: Mandriva mostly, vector 5.1, tried many.Suse gone from HD because bad Novell/Zinblows agreement
Posts: 1,606
Rep:
It looks like a gateway / route story.
Your first machine eth0 has the IP address given by your ISP, This is ok.
I think you need to say on first machine
ifconfig eth1 192.168.1.1 up (as root)
to make eth1 available. (not I would normally tell you 192.168.0.1)
Then connect eth1 to the switch/router.
And then you might still be missing the right getway / route instruction
eth0 on second machine is 192.168.1.2
Bobblefiedl gave you instructions for 192.168.0.2
PS: This also need checking. In your case you want 0
/proc/sys/net/ipv4/icmp_echo_ignore_all
Last edited by Emmanuel_uk; 03-15-2006 at 01:50 PM.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.
