15. januar 2014 05:00
Til: pfSense support and discussion
Emne: Re: [pfSense] WAN not accepting traffic
This software is very frustrating. Last night captive portal was prompting for
logon info and today its not.
UGH
Anyone willing to remote connect and help me out?
Brian
bri...@dlois.com
207-212
e.org [mailto:list-boun...@lists.pfsense.org] På
vegne af Brian Caouette
Sendt: 15. januar 2014 05:00
Til: pfSense support and discussion
Emne: Re: [pfSense] WAN not accepting traffic
This software is very frustrating. Last night captive portal was prompting for
logon info and today its not.
This software is very frustrating. Last night captive portal was
prompting for logon info and today its not.
UGH
Anyone willing to remote connect and help me out?
Brian
bri...@dlois.com
207-212-6560
On 1/14/2014 10:16 PM, Brian Caouette wrote:
Would you be willing to do a remote connection?
Would you be willing to do a remote connection? If so email
bri...@dlois.com and I'll share the details to the machine.
Brian Caouette
207-212-6560
On 1/14/2014 8:33 PM, Walter Parker wrote:
If the WAN interface is set to DHCP, then I think there is an option
to override/not override the DNS s
wrote:
>
>> It has 8.8.8.8 & 8.8.4.4
>>
>> What do you mean by over ride? Where is that located? As for a rule for
>> 53 I have one I'm there to allow all. Wouldn't that cover it?
>>
>> Sent from my HTC
>>
>>
>> - Reply mes
l. Wouldn't that cover it?
>
> Sent from my HTC
>
>
> - Reply message -
> From: "Walter Parker"
> To: "pfSense support and discussion"
> Subject: [pfSense] WAN not accepting traffic
> Date: Tue, Jan 14, 2014 8:04 pm
>
>
> You mi
It has 8.8.8.8 & 8.8.4.4
What do you mean by over ride? Where is that located? As for a rule for 53 I
have one I'm there to allow all. Wouldn't that cover it?
Sent from my HTC
- Reply message -
From: "Walter Parker"
To: "pfSense support and discussion
You might check the DNS settings on the PFSense router itself to make sure
that it has valid IP addresses for DNS servers. Also check on the override
flags (and maybe add a rule for 53 DNS traffic).
Walter
On Tue, Jan 14, 2014 at 4:47 PM, Brian Caouette wrote:
> I think we've made progress.
I think we've made progress. Things in management that didn't work are
now working. Before it was not able to do a ping or tracert and now they
do. I think the issue is dns related now because Windows 8 laptop
reports a dns error. Also the dns lookup in management doesn't give me
any results. S
Thank you! I will give that a try after 4 hours. I do not have remote
access to the machine.
Brian
On 1/14/2014 1:13 PM, Walter Parker wrote:
From the PFSense UI, select Firewall->NAT. Then click on the Outbound
tab. Then select the Manual Outbound NAT rule generation radio button
(this turns
>From the PFSense UI, select Firewall->NAT. Then click on the Outbound tab.
Then select the Manual Outbound NAT rule generation radio button (this
turns off Automatic outbound NAT rule generation). Then delete/deactive the
mapping that has your LAN network as a source. This is what is messing up
yo
The pf wan port is plugged into my Linksys ap so it is already behind
nat hence the reason I unchecked the option under the interface tab to
block reserved ips. I see no reason to use nat again. I'm open to
recommendations as to the easiest solution. Pretty sure I did create a
rule to allow all
By default, PFSense blocks WAN to LAN traffic. If you want WAN to LAN
traffic, you will need to allow it (add rules on both the WAN and LAN
sides). But you might want to notice something else. If PFSense is
operating as a straight up router where you don't want NATing of the LAN
packets, then you w
Are you sure your WAN and LAN networks are on different subnets?
PfSense by default has LAN on 192.168.1.0/24. Make sure that you Linksys
provides IPs different from this.
-N
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.___
L
Confirmed but as I said its the WAN blocking external traffic from what
I see.
Brian
On 1/14/2014 12:04 PM, Robert Pickett wrote:
I would start off by checking the firewall section of pfSense to make
sure that the LAN has a default allow statement. It should say
something like LAN -> any or s
I would start off by checking the firewall section of pfSense to make
sure that the LAN has a default allow statement. It should say something
like LAN -> any or something like that.
-Robert
On 1/14/2014 8:53 AM, Brian Caouette wrote:
I've downloaded Pfsense Live 2.1 and installed it on an ol
I've downloaded Pfsense Live 2.1 and installed it on an old machine
with two nics. The pf machine can ping internally and externally with no
issues. I was able to jump to shell and telnet out to a bbs I'm part of.
Now on the LAN nothing works except the pf web management screen. I have
looked
17 matches
Mail list logo
