Some dumps from commands about the Eth issue

Finally im able from that comp to post some text file about some commands.
Pls note that the first ifconfig was before the nic started to work in
answer to some of my ifup and ifdown. Also ive found the nics works well
it's their connection to the router that is lacking.


[root@SilicaMkV ri]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0A:5E:53F:7E
inet addr:192.168.1.41 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20a:5eff:fe53:df7e/64 Scope:Link
UP BROADCAST MULTICAST MTU:1500 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:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:10 Memory:e3000000-0

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

[root@SilicaMkV ri]# ifdown eth0
[root@SilicaMkV ri]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0A:5E:53F:7E
inet6 addr: fe80::20a:5eff:fe53:df7e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:3 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:192 (192.0 b)
Interrupt:10 Memory:e3000000-0

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

[root@SilicaMkV ri]#
[root@SilicaMkV ri]# ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0A:5E:53F:7E
inet addr:192.168.1.41 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::20a:5eff:fe53:df7e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:9538 errors:0 dropped:0 overruns:0 frame:0
TX packets:6263 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:12595868 (12.0 MiB) TX bytes:673125 (657.3 KiB)
Interrupt:10 Memory:e3000000-0

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

[root@SilicaMkV ri]# route
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 * 255.255.255.0 U 10 0 0 eth0
default 192.168.1.1 0.0.0.0 UG 10 0 0 eth0
[root@SilicaMkV ri]#

[root@SilicaMkV ri]# route -n
Kernel IP routing table
Destination Gateway Genmask Flags Metric Ref Use Iface
192.168.1.0 0.0.0.0 255.255.255.0 U 10 0 0 eth0
0.0.0.0 192.168.1.1 0.0.0.0 UG 10 0 0 eth0
[root@SilicaMkV ri]#



[root@SilicaMkV ri]# cat /etc/resolv.conf
nameserver 193.70.152.15
# nameserver 192.168.1.1

# ppp temp entry
[root@SilicaMkV ri]#

riccardo-pini@libero.it adjusted his/her tinfoil beanie to post:

> Finally im able from that comp to post some text file about some
> commands. Pls note that the first ifconfig was before the nic started
> to work in answer to some of my ifup and ifdown. Also ive found the
> nics works well it's their connection to the router that is lacking.

<<snip>>

> [root@SilicaMkV ri]# cat /etc/resolv.conf
> nameserver 193.70.152.15
> # nameserver 192.168.1.1
>
> # ppp temp entry
> [root@SilicaMkV ri]#


So it is working OK now?

What finally got it working Riccardo?

Was it the nameserver ( DNS ) entries?

if so does the router do DNS?

Is this with static address or with DHCP?

--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

Hi Mark!

For now seems to be so. Im using DHCP for now yes. The dumps i posted here
is what it gives right now. Placing in order some cables today forced me to
completely switch off the comp and the router so i worried to have to
reinstall or work again on the nics for go online but at this first boot i
got everything going on immediately. But i want to be sure before post a
message saying that everything is fine. For now it goes. And what i posted
before is how my comp is set up. About only one thing im very sure and is
the fact that under Linux the Realtek and the 3Com Gigabit always works,
coz becoming more expert i could understand how they were reacting and they
do really works well.

Ill keep you posted about future news,
Thanks to all,
Ric

riccardo-pini@libero.it adjusted his/her tinfoil beanie to post:

> Hi Mark!
>
> For now seems to be so. Im using DHCP for now yes. The dumps i posted
> here is what it gives right now. Placing in order some cables today
> forced me to completely switch off the comp and the router so i
> worried to have to reinstall or work again on the nics for go online
> but at this first boot i got everything going on immediately. But i
> want to be sure before post a message saying that everything is fine.
> For now it goes. And what i posted before is how my comp is set up.
> About only one thing im very sure and is the fact that under Linux the
> Realtek and the 3Com Gigabit always works, coz becoming more expert i
> could understand how they were reacting and they do really works well.
>
> Ill keep you posted about future news,
> Thanks to all,
> Ric

Great stuff Riccardo,

We will make a network engineer of you yet :-)

Take care and enjoy.

Any problems just holler.

--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

Hi i also took away the sit0 adding the alias net-pf-10 off line to
/etc/modrprobe.conf, forced no apic and no local apic, but at a reboot i
got the usual situation...im posting here the dump that maybe could help:

[root@SilicaMkV ri]# ifconfig
eth0 Link encap:Ethernet HWaddr 00:0A:5E:53F:7E
UP BROADCAST MULTICAST MTU:1500 Metric:1
RX packets:20 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:18314 (17.8 KiB) TX bytes:0 (0.0 b)
Interrupt:10 Memory:e3000000-0

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:82 errors:0 dropped:0 overruns:0 frame:0
TX packets:82 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:6644 (6.4 KiB) TX bytes:6644 (6.4 KiB)

[root@SilicaMkV ri]# ifdown eth0
RTNETLINK answers: Network is unreachable

Nothing new except this last one i never saw. Also when i do the ruote
command i get the list i posted here yesterday but it takes time for find
the gateway address. This of course when i cannot connect to the router.

At this time after have received the RTNETLINK message i set up again the
nic with mcc rebooted and the nic went up.

Any idea?

P.S.: Maybe Mark i will study something for get a certification! ))

I forgot to say that if i do ifup eth0 seems to be useless (no "RUNNING"
indication as answer to ifconfig command) and if i then do ifdown eth0 i
get the error message.

Thanks,
Ric

riccardo-pini@libero.it adjusted his/her tinfoil beanie to post:

> Hi i also took away the sit0 adding the alias net-pf-10 off line to
> /etc/modrprobe.conf, forced no apic and no local apic, but at a reboot
> i got the usual situation...im posting here the dump that maybe could
> help:
>
> [root@SilicaMkV ri]# ifconfig
> eth0 Link encap:Ethernet HWaddr 00:0A:5E:53F:7E
> UP BROADCAST MULTICAST MTU:1500 Metric:1
> RX packets:20 errors:0 dropped:0 overruns:0 frame:0
> TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
> collisions:0 txqueuelen:1000
> RX bytes:18314 (17.8 KiB) TX bytes:0 (0.0 b)
> Interrupt:10 Memory:e3000000-0
>

> Any idea?
>

Well for a start the nic is not getting a IP, either from DHCP or
static.

--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

Yep i know. So speaking about when it's not up, i can assign either dhcp or
static to the nic, i can ping it, perhaps i cannot read the "running" work
when i ifconfig and check all the ethx. If i try to ifdown it i receive
that "RTNETLINK answers: Network is unreachable" message. And once i a
while when i boot linux is able to really bring up the nic and connect it
to the gateway. Actually seems the gateway that is unable to properly
handle the nic. Is there any command or check i'd do for understand what's
happening and be able to resolve it?

Ric

riccardo-pini@libero.it adjusted his/her tinfoil beanie to post:

> Yep i know. So speaking about when it's not up, i can assign either
> dhcp or static to the nic, i can ping it, perhaps i cannot read the
> "running" work when i ifconfig and check all the ethx. If i try to
> ifdown it i receive that "RTNETLINK answers: Network is unreachable"
> message. And once i a while when i boot linux is able to really bring
> up the nic and connect it to the gateway. Actually seems the gateway
> that is unable to properly handle the nic. Is there any command or
> check i'd do for understand what's happening and be able to resolve
> it?
>
> Ric


I have been bordering on the fact that it is the modem/router for a
while, I use dozens of the 8193 network cards here and have never had
problems also the fact that /both/ your different chipset nics show the
same problem points to something external to your machine.

One thought on the router side is to check that you are not allocating
an IP on your machine that might be in its DHCP pool ( if you can
change that in your router ) normally you can specify the range of the
dynamically allocated IP`s maybe your router does not like you putting
a static address that is inside the pool?????

And we all know that you have checked/replaced the cable?????

And you are only connecting one nic to the router at the same time????

Another thought, have you tried booting with the parameter of:

pci=routeirq

HTH

--
Mark
Twixt hill and high water
N. Wales, UK
Novell Support Forums SysOp

Ciao Mark,

> I have been bordering on the fact that it is the modem/router for a
> while, I use dozens of the 8193 network cards here and have never had
> problems also the fact that /both/ your different chipset nics show the
> same problem points to something external to your machine.

im thinking about the same, infact im working on the router now. Two nics,
same behviour, 3 distros, and two diff cables (one came along with the
router and another normal one i bought), cannot mistake.


> One thought on the router side is to check that you are not allocating
> an IP on your machine that might be in its DHCP pool ( if you can
> change that in your router ) normally you can specify the range of the
> dynamically allocated IP`s maybe your router does not like you putting
> a static address that is inside the pool?????

Would be strange. Using DHCP on router and under linux the connection led
goes on but it's unable to fix an Ip to the nic (it shows "determining ip
address" but the procedure never ends), instead if i decide for static ip
for both i obtain that for a reboot i can find everything goin up, but for
one reboot. Anyway, normal behaviour would require that i can bring up/down
the nic as much as i want and see the router finding them (led on), and use
it, right? This never happened. I wonder if the "Winbleah" Easy
configurator procedure wrote something inside the router's firmware. But i
think that i jumped over this when under linux ive updated the firmware and
did several hard reset on it.


> And we all know that you have checked/replaced the cable?????

Will (again) check them.


> And you are only connecting one nic to the router at the same time????

Yes of course. Worked with only the Realtek without have phisically in the
3com and viceversa with Realtek disabled and the 3com in.


> pci=routeirq

This i already tried time ago and didnt work. (Which hits another point
against the router).

This is the link to the router in-rom web based interface. Do you see
something particular i should do/not do?

http://www.usr.com/support/9105/9105-ug/index.htm

Thanks,
Ric