Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - megah3rtz

#1
Just noticed, that the dashboard doesnt show any sign of a reboot, but I can see it clearly i dmesg.
#2
Thanks for your response chemlud,

I have tried a brand new install, and that is what I am using now, but that doesnt seem to have had any affect. I am also not using suricata, and am just running a base install with the prometheus exporter added. I am planning to try another Intel NIC, and have a i350T2 on the way, but was hoping I could find a log or something that would give me some useful info about what was going on in the mean time.
#3
Hello, Im really hoping someone can help me out with this issue, because it is driving me nuts!

I am running Opnsense (20.7.5) on a Dell optiplex 3020 SFF desktop( 3rd gen I3, 8GB ram 256GB SATA SSD ). I am using the onboard NIC as my WAN interface, that connects to my Virgin Media Router in modem mode. I have also added an Intel NIC ( I cant remember the model number now but I think it is a Pro 1000T) as my LAN interface. My setup is really uncomplicated from what I can tell, but for some reason my LAN interface goes up and down at random times.

Lastnight it was down for 6 hours while we were asleep, but today most of the day I could use it with no noticeable issues, but then it dropped again while someone was in the middle of a Zoom call this evening.

I have checked dmesg and can see the interface go Up / Down, and can even see holes in the metrics I am getting from OpnSense, but still can work out a cause. I have even tried three different switches connected to the lan interface to see if they were the problem, but still no dice.

Some relevant (I hope) output is attached, and I would love to hear any suggestions.
root@OPNsense:~ # pciconf -l
hostb0@pci0:0:0:0: class=0x060000 card=0x05771028 chip=0x01508086 rev=0x09 hdr=0x00
pcib1@pci0:0:1:0: class=0x060400 card=0x05771028 chip=0x01518086 rev=0x09 hdr=0x01
-- trim --
em1@pci0:0:25:0: class=0x020000 card=0x052c1028 chip=0x15028086 rev=0x04 hdr=0x00
em0@pci0:1:0:0: class=0x020000 card=0xa01f8086 chip=0x10d38086 rev=0x00 hdr=0x00

[/code]

root@OPNsense:~ # ifconfig
em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=802008<VLAN_MTU,WOL_MAGIC>
ether 68:05:ca:b5:f3:37
inet6 fe80::%em0 prefixlen 64 scopeid 0x1
inet <MY PUBLIC IP> netmask 0xffffff00 broadcast <PUBLIC BROADCAST>
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=23<PERFORMNUD,ACCEPT_RTADV,AUTO_LINKLOCAL>
em1: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu 1500
options=802008<VLAN_MTU,WOL_MAGIC>
ether b8:ca:3a:a8:86:f6
inet6 fe80::baca:3aff:fea8:86f6%em1 prefixlen 64 scopeid 0x2
inet 192.168.1.1 netmask 0xffffff00 broadcast 192.168.1.255
media: Ethernet autoselect (1000baseT <full-duplex>)
status: active
nd6 options=21<PERFORMNUD,AUTO_LINKLOCAL>


root@OPNsense:~ # tail -n 20 /var/log/dmesg.today
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
arp: 192.168.1.167 moved from 24:da:33:d6:bc:42 to 40:4d:7f:15:4c:9f on em1
arp: 192.168.1.167 moved from 40:4d:7f:15:4c:9f to 24:da:33:d6:bc:42 on em1
arp: 192.168.1.164 moved from 50:0f:f5:ad:2c:40 to 24:da:33:d6:bc:42 on em1
em1: link state changed to DOWN
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
em1: link state changed to UP
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
em1: link state changed to DOWN
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled
em1: link state changed to UP
pflog0: promiscuous mode disabled
pflog0: promiscuous mode enabled


While posting this output, I have noticed that dmesg,today contains output for a reboot I didnt realise happened, also there are a lot of messages for pid 90870 (syslog-ng), jid 0, uid 0: exited on signal 6 (core dumped)  that I will have a look into (the syslog messages seem to be more to do with the reboot, than linked to any of the up/down of the interfaces).