[SLUG] Suse 8 network problem

[Chris More]

Gavin !

Thank you for your most excellent detailed response to my problem,  which I 
worked through step by step.  I could still not get the darned thing to work.

Unfortunately my knowledge of networks is fairly simplistic  and it turned 
out the problem was I hadn't given the win98 machine a IP address in the same 
range as the suse machine.  It was auto allocating itself an address and as 
soon as I gave it a static address in the 169.128.1.x range everything 
started working.   I got samba working and so things are just dandy.

My only problem now is.... its taken me so long, I can't remember why I 
wanted to network them in the first place!

Oh well.... you Linux and learn.

Many thanks.

Chris


On Wednesday 25 September 2002 1:12 pm, you wrote:
> On Wed, 2002-09-25 at 09:48, Chris More wrote:
> > Can anyone help with a problem I have with my mini-itx machine when
> > running suse 8.
> >
> > I am trying to network a win98 box to a mini-itx running suse through a
> > crossover network cable, but I can't get either machine to ping each
> > other.
> >
> > I can dual boot the mini-itx into win xp and have absolutely no problems
> > when networking xp to win98.    Which means there are no hardware
> > problems.
>
> When the module is loaded, what does dmesg (or /var/log/messsages or
> /var/log/syslog) say? everything ok?
>
> Is the module actually loaded? (lsmod)
>
> Is Linux using the same IRQ as Windows does? (/proc/interrupts, first
> collumn is also the same as what ifconfig says?).
>
> What Network card is it? Is it a PCI one or something exotic?
>
> > Under suse, as far as I can see, the network card is installed ok and is
> > even receiving and sending packets (when queryed using ifconfig).
> >
> > It seems to be something to do with the suse setup because I can't even
> > ping 127.0.0.1 without manually adding eth0 to default route.
>
> I agree. If the loopback interface isn't even being configured,
> something is really wrong. I would try stop all networking
> (/etc/init.d/network stop) then configure it manually, just to be sure
> it is only a config problem.
>
> ifconfig lo up  (bring up the loopback interface)
> ifconfig lo     (make sure it worked)
> ping 127.0.0.1
>
> ifconfig eth0 192.168.0.1 up
> ifconfig eth0 (It worked?)
>
> ipchains -F (or) iptables -F  (make sure no filters are being used)
>
> echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_all
> echo 0 > /proc/sys/net/ipv4/icmp_echo_ignore_broadcasts
>
> The box should reply to pings from the other end of the crossover (only
> to it's IP address of course, and not its hostname) and vise-versa
>
> > Its been driving me nuts for about a week now... Any ideas?  Have I
> > missed something obvious?  like not being able to use a crossover cable
> > with linux?
>
> The latest linux kernels have more advanced networking features than
> Cisco boxes. So ofcourse, a simple crossover cable should not be a
> problem. From what you have mentioned, i would think a simple config
> problem is the cause.
>
> If the above worked, you need to edit the appropriate
> /etc/sysconfig/network* files. If it didn't, can you provide some more
> info? perhaps the output of running script while trying the above or
> such.
>
> Let me know,
> Regards,
> Gav

-- 
http://www.staxton.com