On Thursday, February 13, 2014 09:43:36 PM Jostein Elvaker
Haande wrote:
The latter exposes not only the core of the product, but
also the workflow and priorities of those involved in
the making of pfSense. It's a level of transparency that
you see more and more of, and for me personally, is
It looks like you can ping. The packet is taking much time to return than
the average, in my servers its take about 100ms (and I don't know where you
are from, so it can be normal there).
Once, I got an issue that the domain pfsense.com was blocking my IP address
(I had two links, and using the
OpenVPN allows you to push routes to the client side… not sure if those routes
can be bypassed (it other words, if it’s just a rule sent to the client only,
or if the firewall actually enforces that rule as well).
I’m not sure about the grouping component. But you could define each user with
On 13/02/2014 19:43, Jostein Elvaker Haande wrote:
The thing that brand names as Netgear now sells out of the box
products with re-imaged pfSense distributions is for me a no brainer.
Not only does it increase the user base of pfSense, meaning that bugs,
performance issues etc are more easily
On 14 February 2014 11:54, Brian Candler b.cand...@pobox.com wrote:
On 13/02/2014 19:43, Jostein Elvaker Haande wrote:
The thing that brand names as Netgear now sells out of the box
[..]
I welcome Netgear to the pfSense community as a most welcome addition,
and I hope to see similar
On 14/02/14 11:53, Chuck Mariotti wrote:
OpenVPN allows you to push routes to the client side... not sure if
those routes can be bypassed (it other words, if it's just a rule sent
to the client only, or if the firewall actually enforces that rule as
well).
I'm not sure about the grouping
On Feb 14, 2014, at 5:15 AM, Jostein Elvaker Haande jehaa...@gmail.com wrote:
On 14 February 2014 11:54, Brian Candler b.cand...@pobox.com wrote:
On 13/02/2014 19:43, Jostein Elvaker Haande wrote:
The thing that brand names as Netgear now sells out of the box
[..]
I welcome Netgear to
Dear all,
Firewall: Aliases: IP
=
I have had entered some domain names there in the past, which always
worked flawlessly.
Recently I changed ISP and since then the domain names are not resolved
anymore to IPs, so that the traffic using those aliases gets blocked by
the
Dear all,
Firewall: Aliases: IP
=
I have had entered some domain names there in the past, which always
worked flawlessly.
Recently I changed ISP and since then the domain names are not resolved
anymore to IPs, so that the traffic using those aliases gets blocked by
the
On 14/2/14 3:37 pm, Thinker Rix wrote:
I have had entered some domain names there in the past, which always
worked flawlessly.
Recently I changed ISP and since then the domain names are not resolved
anymore to IPs, so that the traffic using those aliases gets blocked by
the firewall.
When
On 2014-02-14 17:57, Chris Bagnall wrote:
On 14/2/14 3:37 pm, Thinker Rix wrote:
I have had entered some domain names there in the past, which always
worked flawlessly.
Recently I changed ISP and since then the domain names are not resolved
anymore to IPs, so that the traffic using those
On 14/2/14 4:48 pm, Thinker Rix wrote:
Any ideas what could be the problem?
Have you tried entering the DNS servers your ISP supplies via PPP or
DHCP (look on the Status - Interfaces page, they should be listed on
there) manually on the General settings page, then disabling DNS via
On 14/02/2014 16:48, Thinker Rix wrote:
- Everything works fine, pfsense can resolve IPs. Examples: The
dashboard says that I am on the latest version (=url is resolved),
diagnosticsping and diagnosticstraceroute work with domain names.
...
Any ideas what could be the problem?
I suggest
On 2014-02-14 18:51, Chris Bagnall wrote:
On 14/2/14 4:48 pm, Thinker Rix wrote:
Any ideas what could be the problem?
Have you tried entering the DNS servers your ISP supplies via PPP or
DHCP (look on the Status - Interfaces page, they should be listed on
there) manually on the General
14 matches
Mail list logo
