search for: llinfo

> On Aug 13, 2018, at 06:17, Charles Lepple <clepple at gmail.com> wrote: > > On Aug 12, 2018, at 11:03 PM, Kevin Mychal M. Ong <kevindd992002 at yahoo.com> wrote: >> >> Hi, >> >> I installed apcupsd through pfsense and noticed some discrepancy with the NUT package. I'm not sure if this is a bug regarding the BATTDATE (apcupsd) and battery.date

...0:00, Kevin Mychal Ong <kevindd992002 at yahoo.com> wrote: > > Denny, > > The first three commands had outputs but the "clog /var/log/system.log | grep -i ups” didn't output any. Did I do anything wrong? This is the output without the grep: > > can't allocate llinfo for <Public IP> on igb0 > Aug 14 18:14:59 pfSense kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0 > Aug 14 18:15:00 pfSense kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0 > Aug 14 18:15:26 pfSense kernel: arpresolve: can't...

...t 00:00, Kevin Mychal Ong <kevindd992002 at yahoo.com> wrote: > > Denny, > > The first three commands had outputs but the "clog /var/log/system.log | grep -i ups” didn't output any. Did I do anything wrong? This is the output without the grep: > > can't allocate llinfo for <Public IP> on igb0 Aug 14 18:14:59 pfSense > kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0 Aug > 14 18:15:00 pfSense kernel: arpresolve: can't allocate llinfo for > <Public IP> on igb0 Aug 14 18:15:26 pfSense kernel: arpresolve: can't...

Denny, The first three commands had outputs but the "clog /var/log/system.log | grep -i ups” didn't output any. Did I do anything wrong? This is the output without the grep: can't allocate llinfo for <Public IP> on igb0 Aug 14 18:14:59 pfSense kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0 Aug 14 18:15:00 pfSense kernel: arpresolve: can't allocate llinfo for <Public IP> on igb0 Aug 14 18:15:26 pfSense kernel: arpresolve: can't allocate llinfo...

...to MAC addresses, which enables hosts on a local network segment to communicate with each other directly. These mappings are stored in the system's ARP cache. FreeBSD's ARP cache is implemented within the kernel routing table as a set of routes for the address family in use that have the LLINFO flag set. This is most commonly often AF_INET (for IPv4). Normally, when a FreeBSD system receives an ARP request for a network address configured on one of its interfaces from a system on a local network, it adds a reciprocal ARP entry to the cache for the system from where the request originate...

...on't know exactly why this lookup is performed, nevertheless the route does exists and box is alive: axxem.hide:~# route get -inet6 fe80:0006::02d0:baff:fef4:0e80 route to: fe80::2d0:baff:fef4:e80%tun0 destination: fe80::2d0:baff:fef4:e80%tun0 interface: tun0 flags: <UP,HOST,DONE,LLINFO> recvpipe sendpipe ssthresh rtt,msec rttvar hopcount mtu expire 0 0 0 0 0 0 1500 0 axxem.hide:~# ping6 fe80:0006::02d0:baff:fef4:0e80 PING6(56=40+8+8 bytes) fe80::290:27ff:fe78:9275%tun0 --> fe80:6::2d0:baff:fef4:e8...

...to MAC addresses, which enables hosts on a local network segment to communicate with each other directly. These mappings are stored in the system's ARP cache. FreeBSD's ARP cache is implemented within the kernel routing table as a set of routes for the address family in use that have the LLINFO flag set. This is most commonly often AF_INET (for IPv4). Normally, when a FreeBSD system receives an ARP request for a network address configured on one of its interfaces from a system on a local network, it adds a reciprocal ARP entry to the cache for the system from where the request originate...

...to MAC addresses, which enables hosts on a local network segment to communicate with each other directly. These mappings are stored in the system's ARP cache. FreeBSD's ARP cache is implemented within the kernel routing table as a set of routes for the address family in use that have the LLINFO flag set. This is most commonly often AF_INET (for IPv4). Normally, when a FreeBSD system receives an ARP request for a network address configured on one of its interfaces from a system on a local network, it adds a reciprocal ARP entry to the cache for the system from where the request originate...

...to MAC addresses, which enables hosts on a local network segment to communicate with each other directly. These mappings are stored in the system's ARP cache. FreeBSD's ARP cache is implemented within the kernel routing table as a set of routes for the address family in use that have the LLINFO flag set. This is most commonly often AF_INET (for IPv4). Normally, when a FreeBSD system receives an ARP request for a network address configured on one of its interfaces from a system on a local network, it adds a reciprocal ARP entry to the cache for the system from where the request originate...