Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Topics - mtrogg

Pages: [1]
1
Hello,

Since a few months I'm running a first Zentyal setup, up to now to my very satisfaction. Zentyal is applicated as gateway to provide non-professional free wireless internet on small scale on bigger distance (some trees in between, 5-15 users). Installed on thin client, 2 gb (800Mhz) ram, core2duo 2.66, use DNS, HTTP Proxy, Traffic Balancing and Traffic Shaping, http filter (to reduce overkill on very limited bandwidth in rural area keep the system in the air), NTP and Webserver, FYI - Great solution, very accessible and managable!

Question;

Now I was accessing Zentyal to find upgrade offer to 3.5 although with remark of removal of bandwidth monitoring?

I use that module to check up on buggy constantly hanging couple of repeaters, can somebody confirm what happens while upgrading from 3.4.8 to 3.5 in regard to these files;

/var/log/zentyal/bwmonitor/*

I use it to check if ip is down through cron scripts, if it is theres a trigger trick to get the crap back up, it was very handy for that. I also check through number of bytes in the night whether a reboot ( and thus NTP request) finished correctly, that eth0.log was very easy to use for that.

Thanks already!

[edit]I'm remote from some ppl I helped out, wouldnt like couple of happy internet users to take the internet from them until i return to visit my friends, which is in a month, thats why i cant easily check myself and thus ask here.. just FYI. cant ask them, oldsters that luckily via super zentyal gui can do a silly thing, hardly, so except for pushing a button under heavy cellphone surveillance i cant ask them a thing. so anybody running a 3.5 community edition setup: is there a way to keep /var/log/zentyal/bwmonitor maintained or a different way in this new 3.5 edition or do I need to do it manually?

2
Excuse me everybody, missed the 501 error from the logs, stupid stupid stupid I know. Tracing that I found myself to forget about the mail.live.com domain. So, putting both mail.live.com and login.live.com as excluded from auth/cache and transparent proxying made us able to 'enjoy' hotmail. And I forgot about the akadns and other akamai domains too, which I blocked amongst some apple and nix update domains to save on this relatively limited bandwidth eaten by autoupdating. I'll continue some testing with those domains in a bit and if results are interesting I will share that. Which is finished. All akamai domains can be blocked to still offer hotmail access.

Hello Everybody!

First of all thanks to the Zentyal company and community. Thanks to your effort I was able to provide solution to some old folks that don't have a clue about digital equipment. Some other guy that was trying to get in IT made them pay some whole lot for stuff that didn't work for over two years. These old folks run a camping where they wanted to offer free internet access to their guests.

That's where I came in, and your product. I'm a former IT guy (this is over a decade ago and mostly I'm done with computers) but nevertheless still of course a little into it. Now I figured to work some things out with BSDOS or packetfence, still I'm just voluntarily offering them my help and need to be travelling alot so they need be able to maintain and manage themselves. Even packetfence becomes a hassle there, can't rely that kid next door to be helping out correctly not accidently crashing the whole network.

Therefor I chose Zentyal. I'm pretty impressed by its usability, these old folks can manage through such a gui. One expensive NAC has been thrown out, two cloudtrax based Senao devices got replaced and some repeaters got from bridge mode into client router mode (bridging (OSI layer 2) gives DHCP trouble, this much faster, for those who want to know) working all happy and shiny with a Zentyal gateway. Perfect! Thumbs up for Zentyal!

The only problem I encountered after deploying (Zentyal is active for two days now) is when one user informed me that hotmail could not be reached. I checked out and saw a blank page indeed! Okay, we all know things happen. So I started digging a bit;

First I figured to try a bit by excluding both hotmail as live domains from transparent (intercepting) proxy, through Zentyal GUI. I have tried with excluding from caching/auth too. It didn't work, then I figured that this might be that content encoding as chunked header from MS servers to the HTTP version 1.0 which Squid uses. So I checked a bit using squidclient and found this not to be true. Squidclient moans a bit about;

X-Squid-Error: ERR_UNSUP_REQ 0

Also, in the cache.log (/var/log/squid3) I get this;
2014/04/18 09:27:55| ERROR: No forward-proxy ports configured.
Although Zentyal has two different ports configured;

/etc/squid3/squid.conf:4:http_port 0.0.0.0:3128 intercept
/etc/squid3/squid.backup.conf:4:http_port 0.0.0.0:3128 intercept
/etc/squid3/squid-external.conf:5:http_port 0.0.0.0:3130

And, when I have the time the next week I hope to unravel some strange bug with wildcards in DNS/BIND section. But that aside, does any of you have a clue what the problem might be with this hotmail?

When I exclude from transparent proxying I seem to have minor improvement, get redirected a little further on but still stuck at https://login.live.com;

I paste you some logs, these are all greped from /var/log recursively;

./squid3/external-store.log.1:36009:1397746821.646 RELEASE -1 FFFFFFFF 417DB3A842E85DC533475EB3A394AAA3  200 1397746820        -1 1397746820 text/html 7399/7399 GET http://login.live.com/
./squid3/external-store.log.1:36011:1397746822.562 RELEASE -1 FFFFFFFF F95F364E411101B35C1964F8451ADFD1  200 1397746821        -1 1397746821 text/html 7402/7402 GET http://login.live.com/
./squid3/external-store.log.1:36017:1397746833.105 RELEASE -1 FFFFFFFF CEFAB8B4F91F142F00601A428A5D9AC3  200 1397746831        -1 1397746831 text/html 7396/7396 GET http://login.live.com/
./squid3/access.log.1:9875:1397742472.131      0 127.0.0.1 NONE/501 22930 GET https://login.live.com/ - HIER_NONE/- text/html
./squid3/access.log.1:9899:1397742875.792      2 127.0.0.1 TCP_MISS/403 23107 GET http://login.live.com/ - HIER_NONE/- text/html
./squid3/access.log.1:9900:1397742875.793      7 127.0.0.1 TCP_MISS/403 23263 GET http://login.live.com/ - HIER_DIRECT/127.0.0.1 text/html
./squid3/access.log.1:9901:1397742952.222      1 127.0.0.1 TCP_MISS/403 23107 GET http://login.live.com/ - HIER_NONE/- text/html
./squid3/access.log.1:9902:1397742952.222      5 127.0.0.1 TCP_MISS/403 23263 GET http://login.live.com/ - HIER_DIRECT/127.0.0.1 text/html
./squid3/access.log.1:9903:1397742956.746      0 127.0.0.1 NONE/501 22930 GET https://login.live.com/ - HIER_NONE/- text/html
./squid3/access.log.1:9904:1397742960.114      0 127.0.0.1 NONE/501 22930 GET https://login.live.com/ - HIER_NONE/- text/html
./squid3/access.log.1:9906:1397742966.034      0 127.0.0.1 NONE/501 22930 GET https://login.live.com/ - HIER_NONE/- text/html
./squid3/access.log.1:9907:1397742971.790      0 127.0.0.1 NONE/501 22930 GET https://login.live.com/ - HIER_NONE/- text/html
./squid3/access.log.1:10339:1397745177.459      0 127.0.0.1 NONE/501 22930 GET https://login.live.com/ - HIER_NONE/- text/html
./squid3/access.log.1:11263:1397746821.375    312 172.16.191.3 TCP_MISS_ABORTED/000 0 GET http://login.live.com/ - FIRSTUP_PARENT/127.0.0.1 -
./squid3/access.log.1:11265:1397746822.562   1180 172.16.191.3 TCP_MISS/200 8658 GET http://login.live.com/ - FIRSTUP_PARENT/127.0.0.1 text/html
./squid3/access.log.1:11271:1397746833.105   2056 172.16.191.3 TCP_MISS/200 8652 GET http://login.live.com/ - FIRSTUP_PARENT/127.0.0.1 text/html
./squid3/access.log.1:11300:1397747229.812      1 127.0.0.1 NONE/501 22930 GET https://login.live.com/ - HIER_NONE/- text/html
./squid3/access.log.1:17347:1397783307.548      0 127.0.0.1 NONE/501 22930 GET https://login.live.com/ - HIER_NONE/- text/html
./squid3/store.log.1:9960:1397742472.131 RELEASE -1 FFFFFFFF E7D01290BC95BD73B1D632270AD0EFBC  501 1397742472         0        -1 text/html 22511/22511 GET https://login.live.com/
./squid3/store.log.1:9986:1397742875.792 RELEASE -1 FFFFFFFF 43E2A90A077D5596499FBE9A9F03DA24  403 1397742875         0        -1 text/html 22685/22685 GET http://login.live.com/
./squid3/store.log.1:9987:1397742875.793 RELEASE -1 FFFFFFFF 4616D74D04B8A80CF2240AED843B46C8  403 1397742875        -1        -1 text/html 22685/22685 GET http://login.live.com/
./squid3/store.log.1:9988:1397742952.222 RELEASE -1 FFFFFFFF 340091C7712199BBAD64721F2B079144  403 1397742952         0        -1 text/html 22685/22685 GET http://login.live.com/
./squid3/store.log.1:9989:1397742952.222 RELEASE -1 FFFFFFFF C6F2BB26C1B3780DBA9C6423558E7346  403 1397742952        -1        -1 text/html 22685/22685 GET http://login.live.com/
./squid3/store.log.1:9990:1397742956.746 RELEASE -1 FFFFFFFF E7D01290BC95BD73B1D632270AD0EFBC  501 1397742956         0        -1 text/html 22511/22511 GET https://login.live.com/
./squid3/store.log.1:9991:1397742960.114 RELEASE -1 FFFFFFFF DFD21A9F2020E0A0E0D10D1F952B6134  501 1397742960         0        -1 text/html 22511/22511 GET https://login.live.com/
./squid3/store.log.1:9993:1397742966.034 RELEASE -1 FFFFFFFF BA319B39AE5017AAB0C63F1340149338  501 1397742966         0        -1 text/html 22511/22511 GET https://login.live.com/
./squid3/store.log.1:9994:1397742971.790 RELEASE -1 FFFFFFFF 5E3AB64E64748383661D3624D9F99ADB  501 1397742971         0        -1 text/html 22511/22511 GET https://login.live.com/
./squid3/store.log.1:10436:1397745177.459 RELEASE -1 FFFFFFFF 8E06A2D2809CB5977A847303612B81D3  501 1397745177         0        -1 text/html 22511/22511 GET https://login.live.com/
./squid3/store.log.1:11370:1397746821.375 RELEASE -1 FFFFFFFF 12458C343D021F962EE781FA025EDE35    0        -1        -1        -1 unknown -1/-1 GET http://login.live.com/
./squid3/store.log.1:11372:1397746822.562 RELEASE -1 FFFFFFFF F953284F6277845627700C40AFE33BE1  200 1397746821        -1 1397746821 text/html 7402/7402 GET http://login.live.com/
./squid3/store.log.1:11378:1397746833.105 RELEASE -1 FFFFFFFF A433B9F79C1966B53F6A54D0E268E10F  200 1397746831        -1 1397746831 text/html 7396/7396 GET http://login.live.com/
./squid3/store.log.1:11408:1397747229.812 RELEASE -1 FFFFFFFF 6D987FE735C17364276949F6E96FA6E8  501 1397747229         0        -1 text/html 22511/22511 GET https://login.live.com/
./squid3/store.log.1:17469:1397783307.548 RELEASE -1 FFFFFFFF F2C3EC1DDDB13B0F504393E524981C2C  501 1397783307         0        -1 text/html 22511/22511 GET https://login.live.com/
./squid3/cache.log.1:21023:Host: login.live.com
./squid3/cache.log.1:21036:Host: login.live.com
./squid3/external-access.log.1:11472:1397746821.646    361 172.16.191.3 TCP_MISS/200 8508 GET http://login.live.com/ - HIER_DIRECT/131.253.61.82 text/html
./squid3/external-access.log.1:11474:1397746822.562   1179 172.16.191.3 TCP_MISS/200 8497 GET http://login.live.com/ - HIER_DIRECT/131.253.61.82 text/html
./squid3/external-access.log.1:11480:1397746833.105   2055 172.16.191.3 TCP_MISS/200 8491 GET http://login.live.com/ - HIER_DIRECT/131.253.61.82 text/html
./dansguardian/access.log.1:10799:1397746822.562   1179 172.16.191.3 TCP_HIT/200 7402 GET http://login.live.com 172.16.191.3 DEFAULT_PARENT/127.0.0.1 text/html
./dansguardian/access.log.1:10805:1397746833.105   2056 172.16.191.3 TCP_HIT/200 7396 GET http://login.live.com 172.16.191.3 DEFAULT_PARENT/127.0.0.1 text/html

First, do any of you have working hotmail/live logins through Zentyal?

Second, is this a known problem or do any of you know of a solution?

Any suggestions are of course welcome. Thanks already!

Thanks again Zentyal and community, for quite some time I'm out of IT still I can tell that this is a pretty nice package that most probably helps out alot of people. Thus, if you need me for some testing, translating or such, I'm planning to contribute too, since opensource needs stay alive and this package as well! When I have a little time, I'll try finish on those bugs too. See you and have fun!

Oh, ps, we make donations to your project, because its nice.

Pages: [1]