General TC > General TC Talk

Building Another Logger

<< < (6/8) > >>

MTCAT:
Hi Rich,

Forgot to add, I did reboot but I still see the same two-line output for eth0 from


--- Code: ---route -n

--- End code ---

Thanks,

David

MTCAT:
Hi Rich,

Here is the output of


--- Code: ---route -n

--- End code ---

from Lubuntu, in which the network connection is okay, can surf the web in Firefox. Seems to be the same as TC except Lubuntu doesn't show the "loopback" entry and the other two lines in TC are in the opposite order as seen in Lubuntu.

Thanks,

David

Rich:
Hi MTCAT

--- Quote from: MTCAT on February 03, 2026, 11:43:18 AM --- ... Is it normal or correct to have two entries for eth0? Now I don't know where this old entry of 172.16.1.0 is coming from. ...
--- End quote ---
It seems it is. I just checked several of my machines, and they all display:

--- Code: ---tc@E310:~$ route -n
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
0.0.0.0         192.168.1.1     0.0.0.0         UG    0      0        0 eth0
127.0.0.1       0.0.0.0         255.255.255.255 UH    0      0        0 lo
192.168.1.0     0.0.0.0         255.255.255.0   U     0      0        0 eth0
tc@E310:~$
--- End code ---
This was for TC10 x86. TC14 x86_64 and TC16 x86_64 were identical.

Your route result appears to be in a different order. I don't know if that's
significant. What happens if you do this:

--- Code: ---sudo ifconfig eth0 down
sudo /opt/eth0.sh
route -n
--- End code ---
See if Apps can now connect.

If not, try changing eth0.sh to this:

--- Code: ---#!/bin/sh
pkill udhcpc
ifconfig eth0 172.16.1.98 netmask 255.255.255.0 broadcast 172.16.1.255 up
route add default gw 172.16.1.254
echo nameserver 8.8.8.8 > /etc/resolv.conf
echo nameserver 172.16.1.254 >> /etc/resolv.conf
--- End code ---

Instead of attaching images, redirect output from commands
into a file like this:

--- Code: ---route -n > route.txt
--- End code ---
Then you can copy/paste from a file into a post between code tags.

Attached images occupy much more space on the server than text.
Even when displayed inline, text can't be searched for when in an image.

MTCAT:
Hi Rich,

Thanks for the help, I'll cut down on the images.

Without any modifications to eth0.sh, I did

--- Code: ---sudo ifconfig eth0 down
sudo /opt/eth0.sh
route -n > route.txt

--- End code ---

After doing this I could ping Google but still could not connect to TinyCore repo.

Then I shut down eth0


--- Code: ---sudo ifconfig eth0 down

--- End code ---

And modified eth0.sh as you instructed, followed by


--- Code: ---sudo /opt/eth0.sh
route -n > routev2.txt

--- End code ---

Once again, I could ping Google but could still not connect to TinyCore repo.

Thanks,

David

MTCAT:
Sorry, forgot to attach the text files to previous post, attached them here and can see below (hopefully).

Here's route.txt;


--- Code: ---Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
127.0.0.1       0.0.0.0         255.255.255.255 UH    0      0        0 lo
172.16.1.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         172.16.1.254    0.0.0.0         UG    0      0        0 eth0

--- End code ---

And here's routev2.txt;


--- Code: ---Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
127.0.0.1       0.0.0.0         255.255.255.255 UH    0      0        0 lo
172.16.1.0      0.0.0.0         255.255.255.0   U     0      0        0 eth0
0.0.0.0         172.16.1.254    0.0.0.0         UG    0      0        0 eth0

--- End code ---

Navigation

[0] Message Index

[#] Next page

[*] Previous page