Thanks!

Here are some more datapoints.

Yeah the switch for the lan is a simple Netgear GS105. My previous df
gateway was connected in the same way, also with an internal em0,

Turning pf off does not help.
Switching cable and port between df and the switch does not help.
Pinging www.google.com on the external interface from df gives
consistant < 2 ms so it's on the internal interface the problem is.
Pinging from a device on wifi (access point connected to the same
switch) to df also gives very high latency.
Pinging from the same wifi device to my desktop gives good latency.
Pinging from df to my desktop gives bad latency.

On 16 October 2016 at 17:24, Justin Sherrill <jus...@shiningsilence.com> wrote:
> This is a problem that's going to require more data.
>
> - If you turn pf off, does the problem go away?
> - If you ping from the DragonFly machine to your desktop, do you get
> the same results?
> - If you ping for an extended period (ping -t), do you get more timeouts?
> - Are you directly connected to the DragonFly machine?  I assume it's
> all going through a network switch.
> - Can you swap out network cables?
> - If you are using some sort of home switch, are any NAT capabilities
> turned off?
>
> If turning pf off does not affect it, it's not pf.
> If pinging DragonFly -> desktop does not do it, it's the desktop
> If you get more timeouts, or if it goes away on a direct link, I'm
> thinking it's something with the physical connection.
>
> On Sun, Oct 16, 2016 at 4:53 AM, Richard Nyberg <rnyb...@murmeldjur.se> wrote:
>> Hi users!
>>
>> I've just changed hardware for my gateway. It's now built on the asus
>> z170i pro gaming motherboard and runs df 4.6. Unfortunately it suffers
>> extreme latency on my lan and I don't know how to troubleshoot this.
>> Between other devices on the lan there's no problem. The gateway isn't
>> loaded in the least since I haven't installed any other services other
>> dhcp yet.
>>
>> ### Gateway lan interface config:
>>
>> shoebox# ifconfig em0
>> em0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
>>         options=1b<RXCSUM,TXCSUM,VLAN_MTU,VLAN_HWTAGGING>
>>         inet 10.5.2.1 netmask 0xffffff00 broadcast 10.5.2.255
>>         inet6 fe80::2e56:dcff:fe96:5961%em0 prefixlen 64 scopeid 0x2
>>         ether 2c:56:dc:96:59:61
>>         media: Ethernet autoselect <rxpause> (1000baseT 
>> <full-duplex,rxpause>)
>>         status: active
>>
>> # ## /etc/pf.conf
>>
>> ext_if="re0"
>> int_if="em0"
>>
>> scrub in
>>
>> nat on $ext_if from !($ext_if) -> ($ext_if:0)
>>
>> block in
>> pass out keep state
>>
>> pass quick on { lo0 $int_if }
>> antispoof quick for { lo0 $int_if }
>>
>> pass on $ext_if proto { icmp }
>>
>> ### Pinging from my desktop:
>>
>> C:>ping 10.5.2.1
>>
>> Pinging 10.5.2.1 with 32 bytes of data:
>> Request timed out.
>> Reply from 10.5.2.1: bytes=32 time=66ms TTL=64
>> Reply from 10.5.2.1: bytes=32 time=559ms TTL=64
>> Reply from 10.5.2.1: bytes=32 time=1647ms TTL=64
>>
>> Ping statistics for 10.5.2.1:
>>     Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
>> Approximate round trip times in milli-seconds:
>>     Minimum = 66ms, Maximum = 1647ms, Average = 757ms
>>
>> ###
>>
>> Any ideas?
>>
>> Best regards,
>> -Richard

Reply via email to