Old compac armada M700: setting the network connection ??? I have a problem.

[cre84j]

It's a network connection problem
On a very old laptop which is running Tinycore
A Pentium III
192 Mb ram, no HDD but a thumb drive only
TC boots up fine very fast slic and easy but after reading up on this through these forums and other documentation i have had no progress on sorting this out so am turning to you here at this forum for some input.

I have tried all sorts of things with setting up a network so i can get the machine on line and download one app to start with so i can put this system to work and find out how to operate Tiny Core and get the full experience maybe get it set up to do what i have in mind to use it for.

I have it connected to my netbook which is connected to the internet. there doesn't seem to be much chance of doing it any other way. I am using a peer to peer connection (xover cable). I pinged from one to the other lots of times from both machines.

I have the netbook's IP as 192.168.1.1 and it is also the Gateway because it has the internet connection and so figured that would be the route for the machine i have tinycore on to go out through.
I take the name servers from the 'resolv.conf' file on the netbook (it's running ubuntu) and put that in the Network setup on the TC machine (the old armada M700)
the TC machine (the old has the IP address of 192.168.1.2


this is how it looks on the tinycore machine (old compac notebook)

Code: [Select]

etho
192.168.1.2 = IP
255.255.255.0 = network mask
192.168.1.255 = broadcast address
192.168.1.1 = gateway
4.2.2.1
4.2.2.2 = name servers

and this is how it looks on the netbook running ubuntu

Code: [Select]

192.168.1.1 = IP
255.255.255.0 = network mask
192.168.1.255 = broadcast address
192.168.1.1 = gateway
4.2.2.1
4.2.2.2 = name servers

well it seems very straightforward but am not getting the ping to work although the netbook instantly responds when i plug the cable into it and also the light is showing at the socket on the compaq. the cable seems OK.

If you can help or have a suggestion that would be apreciated as i have been trying  to get this happening for some time now. thanks in advance to anyone who can help me.

[tinypoodle]

'etho' is wrong, I'd guess that should be 'eth0'

[cre84j]

Yes sorry that is a typo

I have

Code: [Select]

eth0 it's set there by default anyway so didn't have to change that

[curaga]

Please post the output of "ifconfig -a" on the TC laptop. Also check whether there's a firewall stopping you on the Ubuntu comp.

[cre84j]

decided to post the ifconfic -a reply here now but will need to do some research on the firewall before i can tell you anything. Is it something to do with the ports i should be researching concerning the firewall?

this is the result from the ifconfig -a

Code: [Select]

dummy          Link encap:Ethernet HWaddr 92:BB:3C:FE:DD:1C
                      BROADCAST NOARP  MTU:1500  Metric:1
                      RX packets:0 errors:0 dropped:0 overruns:0 frame:0
                      TX packets:0 errors:0 dropped:0 overruns:0 carrierr:0
                      collisions:0 txqueuelen:0
                      RX bytes:0 (0.0 B)   TX bytes:0 (0.0 B)

eth0              Link encap:Ethernet HWaddr 00:B0:55:14:DD:77
                     inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
                     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 carrierr:0
                     collisions:0 txqueuelen:1000
                     RX bytes:0 (0.0 B)   TX bytes:0 (0.0 B)

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:12 errors:0 dropped:0 overruns:0 frame:0
                     TX packets:12 errors:0 dropped:0 overruns:0 carrierr:0
                     collisions:0 txqueuelen:0
                     RX bytes:600 (600.0 B)   TX bytes:600 (600.0 B)

I typed this out but checked it for typo's and am fairly sure it is as was on screen. Well i checkd and double checked it and am sure it is true to what is on screen on the TC machine.

I'll look into the firewall now but look out for anything you post back here in the meantime, thanks for the prompt reply I really appreciate it.

[curaga]

It that's correct, the ethernet port is down. No wonder then why no traffic

sudo ifconfig eth0 up

[cre84j]

been looking into the probability of the firewall on the ubuntu machine causing this
well by what i read ubuntu has a firewall by default closing all ports unless they are opened from the inside so am looking into that because i read that there is more than one way of dealling with it, The following is what is in the terminal after I did sudo ifconfig eth0 up on the TC machine:

Code: [Select]

tc@box:~$ sudo ifconfig eth0 up
ifconfig: SIOCSIFFLAGS: No such file or directory
tc@bax:$ ping 192.168.1.1
PING 192.168.1.1 (192.168.1.1): 56 data bytes
ping: sendto: Network is unreachable
tc@box:~$
well am thinking that it's the firewall on the ubuntu side that is causing this
something about an ubuntu application called 'ufw' and it's rules and also changing #nat table rules by uncommenting some things. this is from the man pages:

Code: [Select]

First, packet forwarding needs to be enabled in ufw. Two configuration files will need to be adjusted, in /etc/default/ufw change the DEFAULT_FORWARD_POLICY to “ACCEPT”:

DEFAULT_FORWARD_POLICY="ACCEPT"

Then edit /etc/ufw/sysctl.conf and uncomment:

net.ipv4.ip_forward=1

It is about something called IP or subnet source masquerading again this is from the man pages.

Code: [Select]

ufw Masquerading

IP Masquerading can be achieved using custom ufw rules. This is possible because the current back-end for ufw is iptables-restore with the rules files located in /etc/ufw/*.rules. These files are a great place to add legacy iptables rules used without ufw, and rules that are more network gateway or bridge related.
which looks like a really good setup as a firewall so i want to keep that going and work with it and need to do some reading and see what i can change to make this work properly.

[tinypoodle]

Code: [Select]

tc@box:~$ sudo ifconfig eth0 up
ifconfig: SIOCSIFFLAGS: No such file or directory


Without knowing how to interprete this, it is certainly not related to any other box you attempt to connect to.

[cre84j]

I'm going on experience maybe i shouldn't
but find that sometimes if a condition is not met
then the script is forked through to saying
something like a standardized string like

Code: [Select]

else "No such file or directory"so that is why I double checked and went on this:

Code: [Select]

PING 192.168.1.1 (192.168.1.1): 56 data bytes
ping: sendto: Network is unreachable
tc@box:~$Maybe i am wrong to do this
but thought that tiny core would have
the right set up by default to be on a network
maybe i am wrong to do that but went on this
default message and what it say's

Code: [Select]

ping: sendto: Network is unreachablemaybe it is unreachable because the TC side is down
which again doesn't make sense to me though could
probably ping self to see, which will try.

[cre84j]

I just pinged the TC machine and it was as i thought

Code: [Select]

tc@box:~$ ping 192.168.1.2
PING 192.168.1.2 (192.168.1.1): 56 data bytes
64 bytes from 192.168.1.2: seq=0 ttl=64 time=115 ms
64 bytes from 192.168.1.2: seq=1 ttl=64 time=119 ms
64 bytes from 192.168.1.2: seq=2 ttl=64 time=123 ms
64 bytes from 192.168.1.2: seq=3 ttl=64 time=127 ms
64 bytes from 192.168.1.2: seq=4 ttl=64 time=114 ms
64 bytes from 192.168.1.2: seq=5 ttl=64 time=121 ms
etc.......well am taking from this that the IP address on the TC end of the connection is up
thanks for you comment tinypoodle it's forced me to make that check
and prove that this TC machine is online just not able to reach the network
for some reason. Well it must be a firewall on the other end the
ubuntu machine has not got the appropriate port open for some reason
and it must be by default as i have not put a firewall on it myself.

[maro]

cre84j: I'm not sure that your NIC is been properly recognised by TC. So what is the result of ifconfig eth0 and dmesg | grep -i eth after your attempt with 'sudo ifconfig eth0 up'?

If the command would have worked the BROADCAST MULTICAST MTU:1500 Metric:1 line from the 'ifconfig eth0' output should have changed to UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 and some of the counters in the following lines might show a non-zero value.

If you have problems with interpreting the (full) 'dmesg' output it might help us to know you what NIC you've got. Since you won't be able to load the 'pci-utils.tcz' extension I'd suggest you run grep -E 'DRIVER|PCI_ID' /sys/bus/pci/devices/*/uevent (and post the result back here). This could help us to steer you to more specific troubleshooting.


EDIT: Scrap this: I've only now seen the posting about the apparently successful 'ping' test. Mind you no host has to respond to a 'ping', so that does not need to mean too much.

[maro]

Hmm, those are pretty high response times for a local 'ping' test (> 100 msec). I'd expect something more like 0.2-0.3 msec for two hosts on the same LAN (and 0.04 msec to oneself).

I wonder how the route output looks like.

[cre84j]

Why is this message saying no such file or directory?

Code: [Select]

tc@box:~$ sudo ifconfig eth0 up
ifconfig: SIOCSIFFLAGS: No such file or directorywhy does it not say "no such device"?
is there a file that needs to be created here in the TC machine
on the /tce extension drive.

I can't do anything at boot time in the boot codes using F2 or F3
there is some sort of key binding problem which is in the Bios i guess.
a lot of the keys register a number instead of the alphabet letter
like if i use the 'M' key it will put out the number '3' or the 'L' is '0' or something like that.

I can use another machine to set up some things in the /tce extension but need to get
the connection problem fixed at some time so wanted to work on it first off.

Well one thing at a time
does anybody know why it says "no such file or directory" what is needed to resolve that?

[cre84j]

this if from the 'ifconfig eth0'

Code: [Select]

eth0              Link encap:Ethernet HWaddr 00:B0:55:14:DD:77
                     inet addr:192.168.1.2 Bcast:192.168.1.255 Mask:255.255.255.0
                     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 carrierr:0
                     collisions:0 txqueuelen:1000
                     RX bytes:0 (0.0 B)   TX bytes:0 (0.0 B)
and this is from dmeg | grep -i eth

Code: [Select]

[code]tc@box:~$ dmesg | grep -i eth
e100: eth0: e100_probe: addr 0x41280000, irq 11, MAC addr 00:B0:55:14:DD:77
e100: eth0: e100_request_firmware:failed to load firmware: Failed to load firmware "e100/d101s_ucode.bin":-2
e100: eth0: e100_request_firmware:failed to load firmware: Failed to load firmware "e100/d101s_ucode.bin":-2
e100: eth0: e100_request_firmware:failed to load firmware: Failed to load firmware "e100/d101s_ucode.bin":-2
e100: eth0: e100_request_firmware:failed to load firmware: Failed to load firmware "e100/d101s_ucode.bin":-2
e100: eth0: e100_request_firmware:failed to load firmware: Failed to load firmware "e100/d101s_ucode.bin":-2
tc@box:~$
'maro' your right about that thanks, now what next 

oh 'maro' in answer to your other question I was pinging self and thought it is a way of knowing if the ethernet was up or not
also am typing these responses out so not totally accurate like the MAC address as was not certain it was a wise thing
to do to publish these adresses on the internet.
[/code]

[tinypoodle]

Install the firmware*.tcz extension.
Highly likely the error message refers to the missing firmware.