Am 02/18/15 um 00:05 schrieb Todd C. Miller:
> One thing to check is the MTU on the Fritz!Box. If the MTU is set
> to, for example, 1448 instead of 1500 you may need to reduce the
> MTU on your laptop to match.
>
> - todd
>
Hi Todd,
thank you for caring!
Well - the Fritz!Box-web-interface is not really telling... So I go
with what it's dhcpd gives me. Here is what 'ifconfig' shows for em0,
wpi0 and trunk0:
em0:
flags=8b43<UP,BROADCAST,RUNNING,PROMISC,ALLMULTI,SIMPLEX,MULTICAST>
mtu 1500
lladdr 00:15:58:81:15:fb
priority: 0
trunk: trunkdev trunk0
media: Ethernet autoselect (1000baseT
full-duplex,master,rxpause,txpause)
status: active
wpi0: flags=8943<UP,BROADCAST,RUNNING,PROMISC,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:15:58:81:15:fb
priority: 4
trunk: trunkdev trunk0
groups: wlan
media: IEEE802.11 autoselect (DS1 mode 11b)
status: active
ieee80211: nwid dlink chan 11 bssid 00:1b:11:61:cf:a1 15dBm wpakey
<not displayed> wpaprotos wpa1,wpa2 wpaakms psk wpaciphers tkip,ccmp
wpagroupcipher tkip
trunk0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> mtu 1500
lladdr 00:15:58:81:15:fb
priority: 0
trunk: trunkproto failover
trunkport wpi0
trunkport em0 master,active
groups: trunk egress
media: Ethernet autoselect
status: active
inet 192.168.178.31 netmask 0xffffff00 broadcast 192.168.178.255
Everything is set to 'mtu 1500'
You know ...- what puzzles me is the fact that the OpenBSD-run server
running in parallel (amd64-current as well) does not show the same
behaviour!
Strange ...
