[OpenIndiana-discuss] OI Hipster becomes unreachable over network after a certain length of uptime
Judah Richardson
judahrichardson at gmail.com
Sun Apr 10 20:10:35 UTC 2022
On Sun, Apr 10, 2022 at 3:07 PM Stephan Althaus <
Stephan.Althaus at duedinghausen.eu> wrote:
> On 4/10/22 19:56, Judah Richardson wrote:
> > Update: I still get the same 0.0.0.0 messages on reboot:
> >
> > $ dmesg | grep 0.0.0.0
> > Apr 10 12:36:58 DellOptiPlex390MT in.routed[562]: [ID 749644
> daemon.notice]
> > rge0 has a bad address 0.0.0.0
> > Apr 10 12:37:03 DellOptiPlex390MT in.routed[562]: [ID 464608
> daemon.error]
> > route 0.0.0.0/24 --> 0.0.0.0 nexthop is not directly connected
> >
> > But as before, the machine acquires the proper IP address once the DE
> > starts. We'll see if connectivity fails again ... usually takes 5 to 14
> > days to happen.
> >
> > On Sun, Apr 10, 2022 at 12:47 PM Judah Richardson <
> judahrichardson at gmail.com>
> > wrote:
> >
> >> I do notice 0.0.0.0 error messages in the onscreen messages displayed at
> >> boot, but when the DE launches the status bar popup shows a proper IP
> >> address acquisition.
> >>
> >> Does your machine have a static IP address?
> >>
> >> FWIW I remembered a Reddit thread
> >> <
> https://www.reddit.com/r/illumos/comments/fndxp7/openindiana_hipster_machine_responds_to_ip/
> >
> >> about a similar (related?) OI issue
> >> <https://github.com/jdrch/Hardware/issues/93> I was having. Someone
> >> replied
> >> <
> https://www.reddit.com/r/illumos/comments/fndxp7/openindiana_hipster_machine_responds_to_ip/fl9bdoc/
> >
> >> with a solution
> >> <https://dlc.openindiana.org/docs/20090715/SYSADV3/html/eyhuv.html>
> that
> >> I'd totally forgotten to try because I'd been able to work around the
> >> original issue. I implemented the suggested fix just now and did #
> reboot.
> >> Fingers crossed.
> >>
> >> On Sun, Apr 10, 2022 at 7:57 AM Stephan Althaus <
> >> Stephan.Althaus at duedinghausen.eu> wrote:
> >>
> >>> On 4/10/22 09:38, Stephan Althaus wrote:
> >>>> On 4/10/22 04:13, Judah Richardson wrote:
> >>>>> Finally got around to looking into this ongoing issue.
> >>>>>
> >>>>> On Thu, Dec 23, 2021 at 2:28 PM Judah Richardson
> >>>>> <judahrichardson at gmail.com>
> >>>>> wrote:
> >>>>>
> >>>>>> On Thu, Dec 23, 2021 at 11:36 AM stes at PANDORA.BE <stes at telenet.be>
> >>>>>> wrote:
> >>>>>>
> >>>>>>> Do you still have access to a console when the system is
> >>> 'unreachable'
> >>>>>>> over the network ?
> >>>>>>>
> >>>>>> Yes, I do.
> >>>>>>
> >>>>>>> If you still have a text console on the system which became
> >>>>>>> unreachable,
> >>>>>>> perhaps you could check before rebooting whether you can see any
> >>>>>>> errors on
> >>>>>>> the NIC.
> >>>>>>>
> >>>>>>> For example using:
> >>>>>>>
> >>>>>>> # dladm show-link -s rge0
> >>>>>>>
> >>>>>>> When I run the above command on system with a e1000g0 interface, it
> >>>>>>> prints IERRORS / OERRORS in the show-link -s e1000g0 output, so
> >>>>>>> hopefully
> >>>>>>> it also prints those statistics for rge0.
> >>>>>>>
> >>>>>> Doesn't show any errors on this end.
> >>>>>>> Also maybe there are error messages in the /var/adm/messages
> >>>>>>> related to
> >>>>>>> rge0.
> >>>>>>>
> >>>>>> No errors there either.
> >>>>> Seems to be a problem within the OS itself, perhaps in relation to
> that
> >>>>> particular NIC.
> >>>>>
> >>>>>
> >>>>>> These are good ideas, thanks. I'll try them next time it happens and
> >>>>>> then
> >>>>>> report back.
> >>>>>>
> >>>>>>> Regards,
> >>>>>>> David Stes
> >>>>>>>
> >>>>>>> ----- Op 22 dec 2021 om 8:56 schreef Judah Richardson
> >>>>>>> judahrichardson at gmail.com:
> >>>>>>>
> >>>>>>>> On Tue, Dec 21, 2021 at 2:06 AM Joshua M. Clulow <josh at sysmgr.org
> >
> >>>>>>> wrote:
> >>>>>>>>> On Mon, 20 Dec 2021 at 22:26, Judah Richardson
> >>>>>>>>> <judahrichardson at gmail.com> wrote:
> >>>>>>>>>> On Tue, Dec 21, 2021 at 12:23 AM Joshua M. Clulow via
> >>>>>>>>> openindiana-discuss <openindiana-discuss at openindiana.org> wrote:
> >>>>>>>>>>>> Any logs or anything like that in particular I should take a
> >>> look
> >>>>>>> at?
> >>>>>>>>>>> What driver is in use?
> >>>>>>>>>> How do I determine this?
> >>>>>>>>> What do you see in "ipadm show-addr"
> >>>>>>>> $ sudo ipadm show-addr
> >>>>>>>> Password:
> >>>>>>>> ADDROBJ TYPE STATE ADDR
> >>>>>>>> lo0/v4 static ok 127.0.0.1/8
> >>>>>>>> rge0/_b dhcp ok 192.168.0.71/24
> >>>>>>>> lo0/v6 static ok ::1/128
> >>>>>>>> rge0/_a addrconf ok fe80::7a45:c4ff:fe14:10a4/10
> >>>>>>>>
> >>>>>>>> and "dladm show-ether"?
> >>>>>>>>
> >>>>>>>> ~$ sudo dladm show-ether
> >>>>>>>> LINK PTYPE STATE AUTO SPEED-DUPLEX
> >>>>>>>> PAUSE
> >>>>>>>> rge0 current up no 1G-f
> >>>>>>> none
> >>>>>>>> By
> >>>>>>>>> default, NICs are named with the driver you're using; e.g.,
> >>>>>>>>> "bge0" is
> >>>>>>>>> an instance of the "bge" driver.
> >>>>>>>>>
> >>>>>>>>>>> What model of NIC is it?
> >>>>>>>>>> It's an onboard Realtek NIC.
> >>>>>>>>> If you "pkg install diagnostic/pci" you should be able to:
> >>>>>>>>>
> >>>>>>>>> /usr/lib/pci/pcieadm show-devs -o
> >>>>>>>>> bdf,vid,did,driver,vendor,device
> >>>>>>>>>
> >>>>>>>> $ sudo /usr/lib/pci/pcieadm show-devs -o
> >>>>>>> bdf,vid,did,driver,vendor,device
> >>>>>>>> BDF VID DID DRIVER VENDOR DEVICE
> >>>>>>>> 0/0/0 8086 100 -- Intel Corporation
> 2nd
> >>>>>>>> Generation Core Processor Family DRAM Controller
> >>>>>>>> 0/2/0 8086 102 i9150 Intel Corporation
> 2nd
> >>>>>>>> Generation Core Processor Family Integrated Graphics Controller
> >>>>>>>> 0/16/0 8086 1c3a -- Intel Corporation 6
> >>>>>>>> Series/C200 Series Chipset Family MEI Controller #1
> >>>>>>>> 0/1a/0 8086 1c2d ehci0 Intel Corporation 6
> >>>>>>>> Series/C200 Series Chipset Family USB Enhanced Host Controller #2
> >>>>>>>> 0/1b/0 8086 1c20 audiohd0 Intel Corporation 6
> >>>>>>>> Series/C200 Series Chipset Family High Definition Audio Controller
> >>>>>>>> 0/1c/0 8086 1c10 -- Intel Corporation 6
> >>>>>>>> Series/C200 Series Chipset Family PCI Express Root Port 1
> >>>>>>>> 0/1c/2 8086 1c14 pcieb1 Intel Corporation 6
> >>>>>>>> Series/C200 Series Chipset Family PCI Express Root Port 3
> >>>>>>>> 0/1c/4 8086 1c18 pcieb2 Intel Corporation 6
> >>>>>>>> Series/C200 Series Chipset Family PCI Express Root Port 5
> >>>>>>>> 3/0/0 10ec 8168 rge0 Realtek Semiconductor Co., Ltd.
> >>>>>>>> RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller
> >>>>>>>> 0/1d/0 8086 1c26 ehci1 Intel Corporation 6
> >>>>>>>> Series/C200 Series Chipset Family USB Enhanced Host Controller #1
> >>>>>>>> 0/1f/0 8086 1c5c isa0 Intel Corporation
> H61
> >>>>>>>> Express Chipset LPC Controller
> >>>>>>>> 0/1f/2 8086 1c00 pci-ide0 Intel Corporation 6
> >>>>>>>> Series/C200 Series Chipset Family Desktop SATA Controller (IDE
> mode,
> >>>>>>> ports
> >>>>>>>> 0-3)
> >>>>>>>> 0/1f/3 8086 1c22 -- Intel Corporation 6
> >>>>>>>> Series/C200 Series Chipset Family SMBus Controller
> >>>>>>>> 0/1f/5 8086 1c08 pci-ide1 Intel Corporation 6
> >>>>>>>> Series/C200 Series Chipset Family Desktop SATA Controller (IDE
> mode,
> >>>>>>> ports
> >>>>>>>> 4-5)
> >>>>>>>>
> >>>>>>>>
> >>>>>>>>> e.g., I can see, on one of my systems:
> >>>>>>>>>
> >>>>>>>>> 0/1f/6 8086 15b7 e1000g0 Intel Corporation
> >>>>>>>>> Ethernet Connection (2) I219-LM
> >>>>>>>>>
> >>>>>>>>>
> >>>>>>>>> Cheers.
> >>>>>>>>>
> >>>>>>>>> --
> >>>>>>>>> Joshua M. Clulow
> >>>>>>>>> http://blog.sysmgr.org
> >>>>>>>>>
> >>>>>>>> _______________________________________________
> >>>>>>>> openindiana-discuss mailing list
> >>>>>>>> openindiana-discuss at openindiana.org
> >>>>>>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> >>>>>>> _______________________________________________
> >>>>>>> openindiana-discuss mailing list
> >>>>>>> openindiana-discuss at openindiana.org
> >>>>>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> >>>>>>>
> >>>>> _______________________________________________
> >>>>> openindiana-discuss mailing list
> >>>>> openindiana-discuss at openindiana.org
> >>>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> >>>> Hi!
> >>>>
> >>>> The last few weeks i had some related symptom, that my connection to
> >>>> the internet is not reachable after a period of time.
> >>>>
> >>>> In my case, the default route gets lost somehow. When i add a new
> >>>> default route according to my home network everything is fine again.
> >>>>
> >>>> Some hints:
> >>>>
> >>>> $ route get default
> >>>>
> >>>> ...
> >>>>
> >>>> $ sudo route add 0.0.0.0 192.168.0.1
> >>>>
> >>>> ...
> >>>>
> >>>> I have a Ethernet Connection (5) I219-LM 8086:15e3
> >>>>
> >>>> Maybe this was since my pkg update on 2022-03-09.
> >>>>
> >>>> And i don't know for sure if this symptom is solved or not with my pkg
> >>>> update yesterday, we'll see..
> >>>>
> >>>>
> >>>> Regards,
> >>>>
> >>>> Stephan
> >>>>
> >>>>
> >>>> _______________________________________________
> >>>> openindiana-discuss mailing list
> >>>> openindiana-discuss at openindiana.org
> >>>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> >>> Hi!
> >>>
> >>> Just happened now:
> >>>
> >>> # ping 8.8.8.8
> >>> ping: sendto No route to host
> >>> # route get default
> >>> default: not in table
> >>> # ifconfig
> >>> lo0: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu
> >>> 8232 index 1
> >>> inet 127.0.0.1 netmask ff000000
> >>> e1000g4: flags=1004843<UP,BROADCAST,RUNNING,MULTICAST,DHCP,IPv4> mtu
> >>> 1500 index 2
> >>> inet 192.168.2.63 netmask ffffff00 broadcast 192.168.2.255
> >>> ether a4:4c:c8:79:c2:f2
> >>> lo0: flags=2002000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv6,VIRTUAL> mtu
> >>> 8252 index 1
> >>> inet6 ::1/128
> >>> e1000g4: flags=20002004841<UP,RUNNING,MULTICAST,DHCP,IPv6> mtu 1500
> index
> >>> 2
> >>> inet6 fe80::a64c:c8ff:fe79:c2f2/10
> >>> ether a4:4c:c8:79:c2:f2
> >>> # dladm show-link
> >>> LINK CLASS MTU STATE BRIDGE OVER
> >>> vboxnet0 phys 9706 up -- --
> >>> e1000g4 phys 1500 up -- --
> >>>
> >>> $ dmesg|tail
> >>> Apr 10 14:45:33 dell6510 in.routed[1035]: [ID 559541 daemon.warning]
> >>> 0.0.0.0 --> 192.168.2.1 disappeared from kernel
> >>>
> >>> How do i find the root cause ??
> >>>
> >>> Greetings,
> >>>
> >>> Stephan
> >>>
> >>>
> >>> _______________________________________________
> >>> openindiana-discuss mailing list
> >>> openindiana-discuss at openindiana.org
> >>> https://openindiana.org/mailman/listinfo/openindiana-discuss
> >>>
> > _______________________________________________
> > openindiana-discuss mailing list
> > openindiana-discuss at openindiana.org
> > https://openindiana.org/mailman/listinfo/openindiana-discuss
>
> Hello!
>
> I have those messages, too.
>
> $ dmesg |grep "0.0.0.0"
> Apr 10 14:40:33 dell6510 in.routed[1035]: [ID 749644 daemon.notice]
> e1000g4 has a bad address 0.0.0.0
> Apr 10 14:40:35 dell6510 in.routed[1035]: [ID 464608 daemon.error] route
> 0.0.0.0/24 --> 0.0.0.0 nexthop is not directly connected
> Apr 10 14:40:35 dell6510 in.routed[1035]: [ID 464608 daemon.error] route
> 0.0.0.0 --> 192.168.2.1 nexthop is not directly connected
> Apr 10 14:45:33 dell6510 in.routed[1035]: [ID 559541 daemon.warning]
> 0.0.0.0 --> 192.168.2.1 disappeared from kernel
> Apr 10 14:46:02 dell6510 in.routed[1035]: [ID 702693 daemon.warning]
> write(rt_sock) RTM_ADD 0.0.0.0 -->192.168.2.1 metric=0 flags=0x2:
> File exists
> Apr 10 14:50:32 dell6510 in.routed[1035]: [ID 559541 daemon.warning]
> 0.0.0.0 --> 192.168.2.1 disappeared from kernel
>
> The question is, after having successfully revceived a hdcp ip address
> and gateway, why should it disappear after some time ?
> I didn't have this issue last year i am shure, and i did not change the
> network setup since then, i had always nwam running and eth auto config
> with dhcp.
>
> But i followed the instructions to modify the dhcp config regarding the
> hostname, and we will see if the issue is solved this way.
>
> I still 'feel' that the dhcp config modification should not be necessary..
>
I agree. What do you use as your DHCP server? Mine is my Pi-hole
installation.
>
> Greetings,
>
> Stephan
>
>
>
> _______________________________________________
> openindiana-discuss mailing list
> openindiana-discuss at openindiana.org
> https://openindiana.org/mailman/listinfo/openindiana-discuss
>
More information about the openindiana-discuss
mailing list