Dear All

Hi everyone this is my first post to this group. I have come back to Linux after a long lay off - so I could be called an old newbie I suppose.


Having looked at a couple of posts regarding my 'challenge' - I can't make a connection between my Linux box and my ADSL modem/router/firewall - This connection is via CAT6. I have included the type of information asked for in these posts.

1. My box was working fine up until recently - I moved the CAT 6 cable and to put it into final position (we are doing up the house) is this a coincidence or is there something in this (my next move is to plug linux straight into the router)
2. Windows has no problem accessing the network now using the same wall socket (my machine is duel boot).
3. I have reinstalled linux (Fedora core 4) to see if this would help and have included all the required network info:

I.P. of machine 192.168.0.2
I.P of gateway (router) 192.168.0.1
Subnet mask 255.255.255.0
DNS. 192.168.0.1 (i.e the router) - I have tried putting in the real DNS info i.e. DNS on the other side of the router no joy with this though.

this is the same IP info as on Windows.

4. Opening up the 'Network Device Control' the info in here is as follows:

I have set IP address as static with the relevant IP's above included.
In the network adaptor section it shows the IRQ to be unknown (is this significant?)

5. I ran the following commands and have included the output from these.


[root@localhost etc]# ping 192.168.0.1
PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
From 192.168.0.2 icmp_seq=1 Destination Host Unreachable
From 192.168.0.2 icmp_seq=2 Destination Host Unreachable
From 192.168.0.2 icmp_seq=3 Destination Host Unreachable



[root@localhost ~]# ifconfig eth0
eth0 Link encap:Ethernet HWaddr 00:0B:6A:CF:9D:10
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20b:6aff:fecf:9d10/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:13 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:6 dropped:0 overruns:0 carrier:6
collisions:0 txqueuelen:1000
RX bytes:1025 (1.0 KiB) TX bytes:0 (0.0 b)
Interrupt:177 Base address:0x4c00


[root@localhost ~]# ip route ls
192.168.0.0/24 dev eth0 proto kernel scope link src 192.168.0.2
169.254.0.0/16 dev eth0 scope link
default via 192.168.0.1 dev eth0


Well thats about it if you could help that would be great.


All the best


Clive Corner

Please use code tags to place this information in.

Could you post the results of the following command:

show the contents of the following files:

/etc/sysconfig/network
/etc/sysconfig/network-scripts/ifcfg-eth0

Dear Fordeck

In response to the below:

----------------------------------------------------------
Could you post the results of the following command:

route -n

show the contents of the following files:

/etc/sysconfig/network
/etc/sysconfig/network-scripts/ifcfg-eth0

---------------------------------------------------

Thanks

Clive Corner


See Below

------------------------------------------------

Contents of:

/etc/sysconfig/network

NETWORKING=yes
HOSTNAME=localhost


Contents of:

/etc/sysconfig/network-scripts/ifcfg-eth0


DEVICE=eth0
BOOTPROTO=none
BROADCAST=192.168.0.255
HWADDR=00:0b:6a:cf:9d:10
IPADDR=192.168.0.2
NETMASK=255.255.255.0
NETWORK=192.168.0.0
ONBOOT=yes
TYPE=Ethernet
GATEWAY=192.168.0.1
USERCTL=yes
PEERDNS=yes
IPV6INIT=yes

Command

[root@localhost ~]# route -n
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 eth0
169.254.0.0 0.0.0.0 255.255.0.0 U 0 0 0 eth0
0.0.0.0 192.168.0.1 0.0.0.0 UG 0 0 0 eth0



------------------------------------------------------------------------------

Clive at one point you say tht network adaptor reports IRQ unknown but on the same side you can see it under ifconfig eth0 output(highlighted).

Maybe a broken driver could be the case of problem. Your configuration looks OK to me.

Please visit this link so you will understand how to use code tags. It makes reading the results of your postings much easier. Having said that could you post the results of these two commands:

Please find this response to the previous message

N.B. There was no output from the first command

p.s I plugged my linux box straight into the router with the same results and windows works fine when plugged into the wall socket - i.e. there is nothing wrong with my CAT6 cabling.

Thanks

Clive

Clive you can see that somehow you did got those 13 RX packets at your box & the other thing noticable is that the errors you have got are at TX. Just for the testing purpose can you fix a laptop or any OS across this box of yours with the a cross cable & then try to ping this box from that box & repost the ifconfig's output ?

And stay assured as those RX packets are not being generated by your own box, as even the replies(destination unreachable - icmp type 3) get counted in localhost RX & TX packet figures.

I am still smelling it as a broken or incorrect driver or a bug's issue.

and can you please also check the output of

What is rather bizarre about this whole thing is that linux was working fine in conecting to the network and then it wasn't I'm not aware that I made any changes to the system.

I'm afraid I don't have a laptop to do the above Amit.

What about the idea of obtaining a cheap ethernet card and seeing if I can get on the network with this, I prefer not to spend the money but if it means getting past this problem it might be worth it?

Below is the output to the command netstat -s

Any further comments on this one?

Hi clive,
Sorry, i was out of my office for some work. And about the o/p of netstat -s, no i dont see anything substantial but still it gives the idea that you did get packets at RX.

But that defeats the idea of sorting out this problem. Anyhow thats gonna work as its a new hardware.

Do you have any desktop of any OS ?

Clive is this an onboard PCI ethernet or a PNP PCI ethernet card ? If its a plug n play pci, can you try it with changing pci slots ?

Hi Amit

I'm a long way from being hard core could you explain the significance of the below.



from Amit

I do have access to XP home computer - I will have to dismantle it etc

If you can explain what I need to do apart from connecting them ethernet port to ethernet port I will do it.

I am at present downloading Fedora 6. If a broken driver is the problem perhaps this will fix it.

What anout idea that it is the ethernet card that is broken in some way - if this was the case then how come windows XP works fine with it?

Anyway thanks for your interest

All the best Clive Corner

Clive you got to connect your XP-HOME with this linux box with a cross-cable & then from windows box, ping(-t) this box's ip. Though you'll only get RTO(request timed out) messages probably but during the same time, at linux box you can use any packet logger, like tcpdump, iptraf, wireshark etc or with we are going to see whether we see any activity at this ethernet interface or not.

With the above we just want to get assure that do you recieve any packets at this box or not. We are just doing this for testing purpose.

Amit

I will get to the above tomorow.

'Speak to you then'

Cheers

Clive Corner

Sorted

Installed the latest version of operating system and now my system is fine.

Thanks for your interest.

Clive Corner