On 12/08/18 01:35, Antony Stone wrote:
> On Saturday 11 August 2018 at 15:26:40, Amos Jeffries wrote:
>
>> On 11/08/18 09:43, Antony Stone wrote:
>>> On Friday 10 August 2018 at 20:13:06, erdosain9 wrote:
Thanks to all!!
Now is working fine.
Just, one question to know... i
On Saturday 11 August 2018 at 15:26:40, Amos Jeffries wrote:
> On 11/08/18 09:43, Antony Stone wrote:
> > On Friday 10 August 2018 at 20:13:06, erdosain9 wrote:
> >> Thanks to all!!
> >> Now is working fine.
> >>
> >> Just, one question to know... i make this accessible from the
> >> internet...
On 11/08/18 09:43, Antony Stone wrote:
> On Friday 10 August 2018 at 20:13:06, erdosain9 wrote:
>
>> Thanks to all!!
>> Now is working fine.
>>
>> Just, one question to know... i make this accessible from the internet...
>> so, i create some acl 0.0.0.0/0 and it's working.
That is almost but
On Friday 10 August 2018 at 20:13:06, erdosain9 wrote:
> Thanks to all!!
> Now is working fine.
>
> Just, one question to know... i make this accessible from the internet...
> so, i create some acl 0.0.0.0/0 and it's working.
> But.. this is a security issue??? or it's ok declare that ACL.
If
Thanks to all!!
Now is working fine.
Just, one question to know... i make this accessible from the internet...
so, i create some acl 0.0.0.0/0 and it's working.
But.. this is a security issue??? or it's ok declare that ACL.
Thanks to all.
--
Sent from:
On 11/08/18 02:56, erdosain9 wrote:
> Antony Stone wrote
>>> I create two entries pointing to squid in DNS now.
>>> site1.mydomain.lan
>>> site2.mydomain.lan
>>
>> So, both of those resolve to 192.168.1.21, right?
>>
>> Yes, the resolve to the ip of squid.
>>
The config example you want to
Antony Stone wrote
>> I create two entries pointing to squid in DNS now.
>> site1.mydomain.lan
>> site2.mydomain.lan
>
> So, both of those resolve to 192.168.1.21, right?
>
> Yes, the resolve to the ip of squid.
>
>> > The config example you want to follow is
>> >
On Friday 10 August 2018 at 16:26:31, erdosain9 wrote:
> > php.mydomain.lan 192.168.1.223
> > ticket.mydomain.lan 192.168.1.246
> >
> >.. and clients never connect to the above directly. So these domains are
> >never to be accessed by users/clients.
>
> The client can connect directly from the
> php.mydomain.lan 192.168.1.223
> ticket.mydomain.lan 192.168.1.246
>.. and clients never connect to the above directly. So these domains are
>never to be accessed by users/clients.
The client can connect directly from the domain. (i mean they can connect
directly in work, but i want to do
On Friday 10 August 2018 at 15:54:01, erdosain9 wrote:
> Ok, thanks. I change that.
1. Changed what?
2. Show us your current DNS entries, and tell us which steps you followed from
https://wiki.squid-cache.org/ConfigExamples/Reverse/MultipleWebservers
> Now, if i go to reverse.mydomain.lan i
Ok, thanks. I change that.
Now, if i go to reverse.mydomain.lan i get this error:
"Unable to forward this request at this time."
1533909140.268 0 192.168.6.20 TCP_IMS_HIT/304 355 GET
http://reverse.mydomain.lan/squid-internal-static/icons/SN.png - HIER_NONE/-
image/png
but what would be
11 matches
Mail list logo
