On 26.05.2014 21:07, Giancarlo Razzolini wrote:
Em 26-05-2014 04:30, bodie escreveu:
On 22.05.2014 22:35, Mihai Popescu wrote:
Will collect pcap here as well of whole process for interested
devs in
private replies.
It should be interesting for other people too, especially for the
ones
reading your long and confuse posts.
Try to present here your setup (configuration files) and what you
want
to do then try to put some tcpdump logs online.
A few folks asked you for tcpdump logs but you are more interested
in
testing the AlienBSD system responses in order to fix OpenBSD !!!
Stop, think and ... describe.
DNS setup in company fixed.
What was wrong with it?
Leftover config for old wireless network not in use for over one year
leading to authentication portal on that strange IP
Specific MTU for inw0 and tun0 is needed here for VPN else troubles
with services, fixed (on Mac it's detected automatically)
This is only needed when you have some broken router along the path.
I
had an adsl modem that, no matter what you did, you had to use an mtu
of
1492, otherwise things being accessed from outside, wouldn't work.
Also
some issues with UDP downloads where seem, but most applications
corrected those. But these are extreme and rare circumstances and,
most
of them, if not all, can be corrected. Perhaps a second sweep of your
network problems might be needed. Anyway, you can take a look at
net.inet.ip.mtudisctimeout and play a little with it to see if you
can
improve your situation without the need to change your mtu on the
interfaces themselves.
Hardly think that it will be fixed. There are eg. firmware updates for
those
HP boxes, but can't be updated because after that some stuff is not
working.
I know, sounds strange,but can't fix whole world. And for wifi setup I
made
config scripts so MTU is set only here and nowhere else.
Now it works as expected on OpenBSD. But thanks to OpenBSD such
issues
were detected in the first place.
Once again thanks a lot to all
Now you know what I meant on the previous e-mail that, if OpenBSD was
seeing something wrong, it was because there was something, indeed,
wrong. Not only OpenBSD try to follow all the standards to the
letter,
but they generally do so securely.
I know that for years already. Bad that others can't see that and
continue
to use some ......... HW/SW
Cheers,