Ingo , Martin, All,
i can confirm
when the issue occured the command
arp -s gateway-ip-address gateway-mac-address
worked to restore connectivity
Cheers,
Tom Smyth
On 1 May 2018 at 21:16, Tom Smyth wrote:
> Hello Ingo, Martin,All,
>
> I think you hit the nail on the head, (I was too busy l
Hello Ingo, Martin,All,
I think you hit the nail on the head, (I was too busy looking at the
routing table (and forgot the fundamental principle of longest prefix
match)
so if I have a static arp entry before adding in the
(more specific than the connected route) i should be OK
just to explain
On 01/05/18(Tue) 21:28, Ingo Schwarze wrote:
> [...]
> So what you are doing seems fragile to me. It may sometimes work
> due to order of configuration, timeouts, whatever, i'm not sure.
It can work if the ARP entry, what Ingo called the /32 is created
before you add your /23.
> But once part o
Hi Tom,
i think i am able to reproduce your problem on -current:
# sh /etc/netstart em0
# route -n show -inet
default192.168.2.1UGS00 - 8 em0
192.168.2/24 192.168.2.100 UCn10 - 4 em0
192.168.2.1link#1
I'm not an expert but i had same issue while using 6.1 as a guest os on a
kvm.
I updated to 6.2 and problem vanished.
On Tue, 1 May 2018, 09:07 Tom Smyth, wrote:
> Hello,
>
> I have encountered this issue for a while, it happens irregularly
> on my systems on this lan
> basically when the issue
Hello,
I have encountered this issue for a while, it happens irregularly
on my systems on this lan
basically when the issue occurs
I cant route out the interface with the default route on it,
I cant ping the gateway
I cant see the arp of the gateway
but i can see the routes installed in the routin
6 matches
Mail list logo