Király István's questions

We have a fairly large, network with several switches, and a router. Suddenly we observed two PC's getting IP addresses in a range we don't use.

The network uses the 10.0.0.0/16 range, and one device always got 192.168.0.114, with no internet access. The gateway address on that pc was 192.168.0.1. We could ping that gateway, and even login, it turned out it is the TP-Link T2600G-52TS switch, which had an uptime of ~500 days. Checking the configs, we saw that there are L3 / VLAN functions, and DHCP clients - even though the DHCP server is NOT enabled. ...

Trying to switch off L3 functions had only the result of the web interface beeing inaccessible. A physical restart restored login though.

We want to use the switch as a pure switch, without L3 functions like VLANs and without a DHCP server, .. but have access to the switch admin interface. The manual is a bit confusing on this subject, it says we can set the VLAN interface to a different IP and range ...

Trying to update the firmware now. Any suggestions how to set the switch as a pure switch?

We have a device that sends POST requests or TCP messages in fixed intervals, with a JSON payload, through the internet to our server running a node application, on another location.

The JSON payload has a timestamp and some other values. We compare that timestamp to the server's timestamp to calculate the time difference, that we call lag.

The interval is 100ms. What we experience, is that initially, the lag is under 200ms. We let the system run for a few days and we observe the lag is increasing, after 2-3 days it is 2000 - 3000ms, and increasing further .. after 6 days around 6000ms.

Once we restart the server process the lag is back to normal, so I assume the sender is OK. This happens with both, the POST requests implementation, and the TCP messages implementation.

Does anyone have any idea why this may happen, or how to narrow down the problem?

We use saslauthd 2.1.27 with postfix and rimap authentication. We experience a strange issue after an update: terribly slow response times soon after a restart.

If the saslauthd process is restarted, the response is fast, under one second. Then a few seconds later response is around one second. After one minute several seconds, and after several minutes up to several minutes.

While testsaslauthd always gives a response after a certain time, the mailing client's timeout.

The imap servers respond normally, so it seems to be an issue with saslauthd. Anyone ha sany ideas how to troubleshoot this?

Proxy version 1.7.9 2017/08/18

Simple GET requests made within script tags in the index file are getting dropped randomly, and instead the custom 400 error html is returned with the status code of 200. Sometimes 2-3 times in a row, sometimes not even 30 times in a row. It seems to appear completely randomly. These are js files served by a node backend static configuration.

From the server logs listening at the backend, it seems that the requests do not arrive. Accessing the file directly always work. Accessing the backend with bypassing the proxy do not reproduce the problem.

Since the Error is clearly the custom error message, it has to be HAproxy. Adding option accept-invalid-http-request, and option accept-invalid-http-response did not resolve the issue. The socat admin command's do not show any errors, and the stat's do not to count these to the 4xx responses.

I'm out of ideas. Anyone has any suggestions how to examine why this is happening?

Logs include ---- in all requests. So an index HTML file requests 7-8 files as dependency. Some css, js files as GET requests. From all those requests, sometimes one or two files are not served, but the custom error 408 HTML is served as data with response code 200. This response 200 is only visible on the browser, where it says Uncaught SyntaxError: Unexpected token < while trying to parse the HTML as JS file. Now on the log via rsyslog these requests do not show up. The backend does not log these requests either. Then, after clicking refresh the next request to the set of files is served, and if served for real, the code for them is 200. Since I just keep refreshing the page, and the content does not change, all requests should show up in all logs, with code 304. ...

global
    daemon
    maxconn 4096
    log         127.0.0.1 local2 debug
    chroot      /var/lib/haproxy
    pidfile     /var/run/haproxy.pid
    user        haproxy
    group       haproxy
    stats socket /var/lib/haproxy/stats
    ssl-default-bind-ciphers PROFILE=SYSTEM
    ssl-default-server-ciphers PROFILE=SYSTEM
    tune.ssl.default-dh-param 2048
    ssl-server-verify none
    stats socket /var/run/haproxy.stat

defaults
        mode                    http
        log                     global
        option                  httplog
        option                  dontlognull
        option http-server-close
        option forwardfor       except 127.0.0.0/8
        option                  redispatch
        retries                 3
        timeout http-request    1s
        timeout queue           1m
        timeout connect         1s
        timeout client          1m
        timeout server          1m
        timeout http-keep-alive 10s
        timeout check           10s
        maxconn                 3000
        option forwardfor
        option http-server-close
       stats enable
       stats uri /stats
       stats realm Haproxy\ Statistics
       stats auth stat:stat
        errorfile 400 /var/www/html/400.html
        errorfile 403 /var/www/html/400.html
        errorfile 408 /var/www/html/400.html
        errorfile 500 /var/www/html/500.html
        errorfile 501 /var/www/html/501.html
        errorfile 502 /var/www/html/502.html
        errorfile 503 /var/www/html/503.html
        errorfile 504 /var/www/html/504.html
        option accept-invalid-http-request
        option accept-invalid-http-response

I recognize the custom error file 400.html content in the browser, when it fails.