On Wed, May 21, 2014 at 7:20 AM, bodie <bodz...@openbsd.cz> wrote:

> On 21.05.2014 12:50, bodie wrote:
>
>> On 21.05.2014 11:18, bodie wrote:
>>
>>> Hi,
>>>
>>> testing http://marc.info/?t=140024539000003&r=1&w=2 further and now I
>>> hit issue with corporate WIFI. I can connect perfectly fine to 2 of
>>> them provided with WPA2-PSK, either with regular ifconfig or with
>>> wpa_supplicant from packages, but the thing is that my
>>> /var/log/messages is flooded by these messages repeating like every
>>> 3s:
>>>
>>> /bsd: arp info overwritten for GW_IP by MAC_1 on iwn0
>>> /bsd: arp info overwritten for GW_IP by MAC_2 on iwn0
>>>
>>> arp -a shows only one MAC all the time and that's MAC_2 no matter if
>>> I reboot or just reconnect to network. Info from inside about setup of
>>> those APs is:
>>>
>>> There actually are 2 gateways having the same IP address GW_IP and
>>> the mac addresses belong to them. They work as failover and also load
>>> balacer.
>>>
>>> Not sure if it's because of that or because of ARP flooding in
>>> /var/log/messages, but performance of those WiFi is quite strange like
>>> ping replies over 20ms, a lot of web services doesn't work, takes
>>> years to connect, some are running perfectly fine immediately and
>>> such.
>>>
>>> So.....
>>>
>>> 1) Is there anything I can do with ARP messages in /var/log/messages?
>>> Nothing in man arp and some sysctl switch I found only in FreeBSD
>>> 2) Is there anything what can be tweaked from OpenBSD side to improve
>>> general performance of WiFi connection or is it just either AP fix or
>>> nothing?
>>>
>>> Thanks a lot
>>>
>>
>>
>> Still trying to get much more info, but that setup must be horrible.
>> Trying arping results in:
>>
>> 30 packets sent, 60 received. Always doubled response with MAC_1 and MAC_2
>>
>> When trying to ping some of the internal servers they all have
>> 123.123.123.123 IP which is of course totally wrong. Same if tried
>> with dig @GW_IP server_IP (as GW_IP is set as DNS by dhclient)
>>
>> So now not so sure if it's terrible AP setup or if it's something in
>> ARP, dhclient, ieee80211 code in OpenBSD
>>
>
>
> Even more suspicious details:
>
> option dhcp-client-identifier 1:0:c2:c6:1c:af:ac in lease from dhclient,
> but my MAC is 00:c2:c6:1c:af:ac. It got mangled or is it on purpose?
> (investigating in the meantime of course :-))
>

that looks like dnsmasq identifier:

It is allowed to use client identifiers (called client DUID in IPv6-land
rather than hardware addresses to identify hosts by prefixing with 'id:'.
Thus: --dhcp-host=id:01:02:03:04,..... refers to the host with client
identifier 01:02:03:04. It is also allowed to specify the client ID as
text, like this: --dhcp-host=id:clientidastext,.....


> dhcp-server-identifier is IP of totally different subnet (10..) instead of
> 192... of that AP/GW
>





-- 
---------------------------------------------------------------------------------------------------------------------
() ascii ribbon campaign - against html e-mail
/\

Reply via email to