Re: [pfSense] WLAN reboot loop

2016-02-25 Thread Larry Rosenman 

On 2016-02-25 08:29, Sean Pohl wrote:
I started over with a fresh install and was able to get the wireless 
working by
putting it on a different subnet from the LAN.  Then I made firewall 
rules that

allowed the two to communicate.  Thank you!

One follow-up question though.  As I was setting the rules for the two 
subnets
to communicate, I was wondering if things like mDNS/Apple 
Bonjour/zeroconf or
link-local traffic would pass between the two subnets with Layer 3 
firewall
rules separating them?  I think that mDNS uses UDP port 5353 but I 
thought it

also would send to an Ethernet MAC as well.

My generic concern is that have small IoT devices or older devices that 
only
send to Ethernet MAC addresses and the Layer 3 firewall rules between 
the two

segments may break some things and not others.  Have you or anyone else
encountered this problem?

Just curious why a bridge interface has problems or should be avoided?

Many thanks.


Install the avahi/mDNS package and enable the wide-area stuff.

I have a similar setup for my house with WiFi on one subnet and Wired on 
a different one.




--
Larry Rosenman http://www.lerctr.org/~ler
Phone: +1 214-642-9640 E-Mail: l...@lerctr.org
US Mail: 7011 W Parmer Ln, Apt 1115, Austin, TX 78729-6961
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] WLAN reboot loop

2016-02-25 Thread Sean Pohl 
I started over with a fresh install and was able to get the wireless working by
putting it on a different subnet from the LAN.  Then I made firewall rules that
allowed the two to communicate.  Thank you!

One follow-up question though.  As I was setting the rules for the two subnets
to communicate, I was wondering if things like mDNS/Apple Bonjour/zeroconf or
link-local traffic would pass between the two subnets with Layer 3 firewall
rules separating them?  I think that mDNS uses UDP port 5353 but I thought it
also would send to an Ethernet MAC as well.  

My generic concern is that have small IoT devices or older devices that only
send to Ethernet MAC addresses and the Layer 3 firewall rules between the two
segments may break some things and not others.  Have you or anyone else
encountered this problem?

Just curious why a bridge interface has problems or should be avoided?

Many thanks.

On Wed, Feb 24, 2016 at 07:15:21PM +, Espen Johansen wrote:
> Remove the wlan card. Then remove config. It sounds like you might have a
> irq or other resource allocation problem. But without any more details its
> hard to say.
> 
> On Wed, Feb 24, 2016, 19:51 Sean Pohl  wrote:
> 
> > Ok. Thank you very much. Any advice on how to get it out of the endless
> > boot loop? Or will my path of least resistance be to simply do a fresh
> > install again? Many thanks.
> > On Feb 24, 2016 12:26, "Espen Johansen"  wrote:
> >
> > > Do not bridge and do not use same subnet. If you want lan and wlan to
> > talk
> > > add rules for the subnets to talk to each other.
> > >
> > > On Wed, Feb 24, 2016, 19:12 Sean Pohl 
> > > wrote:
> > >
> > > > The problem is an endless boot-loop on my pfSense installation after I
> > > > made one
> > > > change to the WLAN interface.
> > > >
> > > > I have an older x86 32 bit machine with three NICs:
> > > >   1. On-board Ethernet
> > > >   2. Ethernet card
> > > >   3. WLAN 801.11g
> > > >
> > > > I was able to configure the WAN & LAN interfaces just fine.  When I
> > > > enabled the
> > > > WLAN interface and set about configuring and saving WLAN interface
> > things
> > > > went
> > > > well until I set the WLAN as DHCP.  When I did and saved it then the
> > > > monitor
> > > > directly attached to the pfSense box filled completely with random
> > > > characters
> > > > and then it would reboot.  During the boot, it would come to the
> > > > "configuring
> > > > WLAN" and then the screen would fill with random characters and reboot
> > > > again.
> > > >
> > > > I read about creating a bridge between a WLAN interface and a LAN
> > > > interface.  I
> > > > was able to do that successfully and was able to connect to the WLAN on
> > > > the box
> > > > but it never assigned me an IP address.  So, it wasn't until I changed
> > > the
> > > > WLAN
> > > > interface setting to DHCP that it would get into this loop.
> > > >
> > > > Should I just set that WLAN interface to be static and then give it a
> > > fixed
> > > > address in the same subnet as the LAN that I trying to bridge to or
> > > > something
> > > > else?
> > > >
> > > > Any suggestions are greatly appreciated.
> > > >
> > > > Thanks.
> > > > ___
> > > > pfSense mailing list
> > > > https://lists.pfsense.org/mailman/listinfo/list
> > > > Support the project with Gold! https://pfsense.org/gold
> > > >
> > > ___
> > > pfSense mailing list
> > > https://lists.pfsense.org/mailman/listinfo/list
> > > Support the project with Gold! https://pfsense.org/gold
> > >
> > ___
> > pfSense mailing list
> > https://lists.pfsense.org/mailman/listinfo/list
> > Support the project with Gold! https://pfsense.org/gold
> >
> ___
> pfSense mailing list
> https://lists.pfsense.org/mailman/listinfo/list
> Support the project with Gold! https://pfsense.org/gold
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] APinger times wrong after a few hours

2016-02-25 Thread Vick Khera 
On Wed, Feb 24, 2016 at 8:28 PM, Jim Thompson  wrote:

> Apinger is… not very good.
>
> This is why we’ve gone to dpinger in pfSense software v2.3


Yay. I'll be glad to not have that PoS software being critical to my
infrastructure.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold