So anyone any idea what could cause the network from failing to connect? Even though I changed nothing.
Sep 16 17:07:22 osmc-Basil connmand[226]: eth0 {add} address 192.168.1.116/16 label eth0 family 2
Sep 16 17:07:22 osmc-Basil connmand[226]: eth0 {add} route 192.168.0.0 gw 0.0.0.0 scope 253 <LINK>
Sep 16 17:07:22 osmc-Basil connmand[226]: eth0 {add} route 192.168.1.1 gw 0.0.0.0 scope 253 <LINK>
Sep 16 17:07:22 osmc-Basil connmand[226]: eth0 {add} route 79.133.43.124 gw 192.168.1.1 scope 0 <UNIVERSE>
Sep 16 17:07:22 osmc-Basil connmand[226]: eth0 {add} route 45.32.28.232 gw 192.168.1.1 scope 0 <UNIVERSE>
Sep 16 17:07:22 osmc-Basil connmand[226]: eth0 {add} route 0.0.0.0 gw 192.168.1.1 scope 0 <UNIVERSE>
Sep 16 17:07:22 osmc-Basil connmand[226]: eth0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
Sep 16 17:19:16 osmc-Basil connmand[226]: eth0 {del} route 178.17.170.67 gw 192.168.1.1 scope 0 <UNIVERSE>
Sep 16 17:19:16 osmc-Basil connmand[226]: Skipping disconnect of carrier, network is connecting.
Sep 16 17:19:16 osmc-Basil connmand[226]: Adding host route failed (Network is down)
Sep 16 17:19:16 osmc-Basil connmand[226]: Adding host route failed (Network is unreachable)
Sep 16 17:19:16 osmc-Basil connmand[226]: Adding host route failed (Network is down)
Sep 16 17:19:16 osmc-Basil connmand[226]: Adding host route failed (Network is unreachable)
Sep 16 17:19:16 osmc-Basil connmand[226]: Adding host route failed (Network is down)
Some of these subnets look strange. Can you explain your network setup in more detail? What are the network settings of a working computer (i.e. what does ipconfig on Windows show?)
the routes could be DNSes it connects to, i messed around with a few different kinds, some are Anycast so that’s pretty random.
My normal ipconfig on a working comp shows
IPv4-adrress. . . . . . . . . . . . : 192.168.1.113 (preference)
Subnetmask. . . . . . . . . . . : 255.255.255.0
Standardgateway. . . . . . . . . : 192.168.1.1
Everything I have is set to static IP’s so it’s always just 192.168.1.xxx for the IPv4, subnet 255.255.255.0 and gateway 192.168.1.1.
That’s just my default settings really.
I can’t really explain why it seems to gw 0.0.0.0 though, it’s set to 255.255.255.0.
As for my network setup, Pi, dumb switch, dd-wrt router bridged with router/modem model in bridge mode.
Have it like that for years now.
Small sidenote, there might be an entry in there that makes you go wtf, thats when I DHCPed for a second to give it a try, I got the weirdest numbers ever, no even remotely in my subnet so I moved back to static.
192.168.1.116/16 is what you have on the Pi. That is not 255.255.255.0. So either you have wrongly configured the Pi or the DHCP server?
Pi is configured through OSMC tool, I just checked it again, Subnet is set to 255.255.255.0
Well that is than strange about the output of your logfile.
Provide the output of ifconfig
Through kodi command line you mean? let me check.
eth0 Link encap: Ethernet Hw Addr (my mac not useful)
inet addr: 192.168.1.116 Bcast: 192.168.1.255 Mask: 255.255.255.0
UP BROADCAST RUNNING MULTICAST DYNAMIC MTU 1500 Metric 1
RX packets 0 errors 126 dropped 63 overruns 0 framework 126
TX packets 740 errors 0 dropped 0 ovverruns 0 carrier 0
collisions 0 txqueuelen 1000
RX bytes 0 TX bytes 72955
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 65546 Metric 1
RX packets 1226 errors 0 dropped 0 overruns 0 frame 0
TX packets 1226 errors 0 dropped 0 overruns 0 carrier 0
Collisions 0 txqueuelen 1
RX bytes 108780 TX bytes 108780
Had to type this blind because both connections are on 1 screen but don’t think i missed anything.
Ok, this is really strange as it contradicts your logfile. Suggest to run
grab-logs -C -A cat /boot/uploadlog.txt | grep "address 192."
to verify. You should get a line with address 192.168.1.116/24 and not address 192.168.1.116/16.
This indicates a serious low level ethernet issue. Suggest you try different cable and switch port.
The RX TX was right after a reboot so its alright, is usually much higher.
Running the log now.
I am talking about the RX error rate!
This is how a healthy interface looks like! 0 Errors
eth0 Link encap:Ethernet HWaddr b8:27:eb:d4:52:31
inet addr:192.168.1.22 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::ba27:efff:fed4:5339/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:13002355 errors:0 dropped:77 overruns:0 frame:0
TX packets:8638324 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:4206175064 (3.9 GiB) TX bytes:3799617113 (3.5 GiB)
Thats what it looked like if i plug my computer (the one i’m using now) with the same cable I use as the pi into the switch at the same port. It’s not the switch, its not the cable.
As for the cat log I dont have a | on my keyboard, or I can’t seem to find it, any idea?
Well if you insist on that point than it must be a Pi issue?
Well depends on the keyboard layout so suggest to google based on your layout.
Haha and of course the only keyboard I have that wasn’t bluetooth is one thats absolutely brandless lol i’ll just search the log manually
192.168.1.116/24 in this log, no idea why it said 16 in the other.Ipconfig state 3 ipconfig method 1
eth 0 {add} address 192.168.1.116/24 label eth0 family 2
eth 0 {add} route 192.168.1.9 gw 0.0.0.0 scope 253
eth0 {add} route 192.168.1.1 gw 0.0.0.0 scope 253
eth {add} route 178.17.170.67 gw 192.168.1.1 scope 0
eth0 {add} route 37.235.49.61 gw 192.168.1.1 scope 0
eth0 {add} route 0.0.0,0 gw 192.168.1.1 scope 0
eth0 {del} route FE80:: gw :: scope 0
To avoid confusion revert your corrections in your post otherwise people will not understand the context.
Anyhow I am out of ideas other than something is really wrong with the network setup especially is you one time end up with /16 and next time /24
That might have been because of the DHCP i tried to use which gave me really wacky numbers.
I also switched switch ports. Didn’t help.
Also what I don’t understand is why my connection suddenly crapped out, it worked perfectly fine, didn’t change anything through SSH, didn’t touch the network at all. I came here for, see topic, and then suddenly this happened out of no where.
And if I try to DHCP I get the following IP, which if you look up, is in reverse range
169.254.139.130 - IP address is in a reserved range.
See this for example 169.254.139.130 - No unique location - Link-local - IP address geolocation
This means you don’t get an IP address from the DHCP server and therefore an APIPA address assigned.
Once again either you broke your Pi or have another fundamental network problem.
Fundamental network error would mean that this comp, my gaming consoles, phones and tablets wouldn’t work properly on it either right?
All of those do.
I’m going to reinstall OSMC just to try and see what happens.
Well that would also be a possibility that you had something installed messing up the network.