Why would it behave any differently then the old netgear I have plugged
into it for another part of the house? Both the netgear and the pfsense
box are essentially doing the same thing.
On 1/15/2014 3:55 AM, Ulrik Lunddahl wrote:
Hi Brian!
Cable Modem (public ip with a 192.168.100.1 management port -> Linksys AP dhcp to
modem 192.168.100.1 lan ip with all connected pc's in this range including -> PF
192.168.100.20 and pf lan of 192.168.1.1 of which is dhcp assigns my laptop .101 when
plugged in.
Have you remembered to tell you NAT router (the first one) to route traffic to
the 192.168.1.x subnet via 192.168.100.20 (pfSense WAN), you will use a static
route for that, on the NAT router, not the pfSense box.
- Ulrik
-----Oprindelig meddelelse-----
Fra: [email protected] [mailto:[email protected]] 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.
UGH
Anyone willing to remote connect and help me out?
Brian
[email protected]
207-212-6560
On 1/14/2014 10:16 PM, Brian Caouette wrote:
Would you be willing to do a remote connection? If so email
[email protected] 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 server addresses from the DHCP
server. Check that. Check that the rule passes TCP&UDP. When I've had
this problem before, I also check from the shell, but then again, I'm
an oldtime FreeBSD user, so I don't fear the CLI (check
/etc/resolv.conf).
Walter
_______________________________________________
List mailing list
[email protected]
http://lists.pfsense.org/mailman/listinfo/list
