[pfSense] FreeBSD on uFW

[Jim Thompson]

U-Boot SPL 2016.03 (May 31 2016 - 19:23:56)
Trying to boot from MMC
Card doesn't support part_switch
MMC partition switch failed
*** Warning - MMC partition switch failed, using default environment

reading u-boot.img
reading u-boot.img


U-Boot 2016.03 (May 31 2016 - 19:23:56 -0500)

   Watchdog enabled
I2C:   ready
DRAM:  512 MiB
MMC:   OMAP SD/MMC: 0, OMAP SD/MMC: 1
reading u-boot.env

** Unable to read "u-boot.env" from mmc0:1 **
Using default environment

Net:not set. Validating first E-fuse MAC
cpsw, usb_ether
Hit any key to stop autoboot:  0 
Booting from: mmc 0 ubldr.bin
reading ubldr.bin
224696 bytes read in 23 ms (9.3 MiB/s)
## Starting application at 0x8800 ...
Consoles: U-Boot console  
Compatible U-Boot API signature found @0x9ef3ab58

FreeBSD/armv6 U-Boot loader, Revision 1.2
(root@fbsd-current-amd64-loos, Sun May 29 01:24:33 CDT 2016)

DRAM: 512MB
Number of U-Boot devices: 3
U-Boot env: loaderdev='mmc 0'
Found U-Boot device: disk
  Checking unit=0 slice= partition=... good.
Booting from disk0s2a:
/boot/kernel/kernel data=0x5b85e4+0x93a1c syms=[0x4+0x805f0+0x4+0x94566]

Hit [Enter] to boot immediately, or any other key for command prompt.
Booting [/boot/kernel/kernel]...   
/boot/dtb/ufw.dtb size=0x7c61
Loaded DTB from file 'ufw.dtb'.
Kernel entry at 0x0x88200100...
Kernel args: (null)
ARM Debug Architecture not supported
KDB: debugger backends: ddb
KDB: current backend: ddb
Copyright (c) 1992-2016 The FreeBSD Project.
Copyright (c) 1979, 1980, 1983, 1986, 1988, 1989, 1991, 1992, 1993, 1994
The Regents of the University of California. All rights reserved.
FreeBSD is a registered trademark of The FreeBSD Foundation.
FreeBSD 11.0-ALPHA1 #0 0671027(master)-dirty: Sun May 29 01:24:06 CDT 2016

root@fbsd-current-amd64-loos:/usr/home/luiz/git/crochet-ubmc/work/obj/arm.armv6/usr/home/luiz/git/freebsd-ubmc/sys/uFW
 arm
FreeBSD clang version 3.8.0 (tags/RELEASE_380/final 262564) (based on LLVM 
3.8.0)
WARNING: WITNESS option enabled, expect reduced performance.
CPU: Cortex A8-r3 rev 2 (Cortex-A core)
 Supported features: ARM_ISA THUMB2 JAZELLE THUMBEE ARMv4 Security_Ext
 WB enabled LABT branch prediction disabled
LoUU:2 LoC:3 LoUIS:1 
Cache level 1: 
 32KB/64B 4-way data cache WT WB Read-Alloc
 32KB/64B 4-way instruction cache Read-Alloc
Cache level 2: 
 256KB/64B 8-way unified cache WT WB Read-Alloc Write-Alloc
real memory  = 536870912 (512 MB)
avail memory = 512077824 (488 MB)
Texas Instruments AM335x Processor, Revision ES1.2
random: entropy device external interface
ofwbus0: 
simplebus0:  on ofwbus0
simplebus1:  on simplebus0
simplebus2:  mem 0x21-0x211fff on 
simplebus1
ti_scm0:  mem 0-0x7ff on simplebus2
aintc0:  mem 0x4820-0x48200fff on simplebus0
aintc0: Revision 5.0
cpulist0:  on ofwbus0
cpu0:  on cpulist0
pmu0:  irq 3 on ofwbus0
am335x_prcm0:  mem 0x20-0x203fff on 
simplebus1
am335x_prcm0: Clocks: System 24.0 MHz, CPU 550 MHz
ti_pinmux0:  mem 0x800-0xa37 on simplebus2
gpio0:  mem 0x44e07000-0x44e07fff irq 96 
on simplebus0
gpiobus0:  on gpio0
gpioc0:  on gpio0
gpio1:  mem 0x4804c000-0x4804cfff irq 98 
on simplebus0
gpiobus1:  on gpio1
gpioc1:  on gpio1
gpio2:  mem 0x481ac000-0x481acfff irq 32 
on simplebus0
gpiobus2:  on gpio2
gpioc2:  on gpio2
gpio3:  mem 0x481ae000-0x481aefff irq 62 
on simplebus0
gpiobus3:  on gpio3
gpioc3:  on gpio3
uart0:  mem 0x44e09000-0x44e0afff irq 72 on 
simplebus0
uart0: console (115384,n,8,1)
iichb0:  mem 0x44e0b000-0x44e0bfff irq 70 on simplebus0
iichb0: I2C revision 4.0 FIFO size: 32 bytes
iicbus0:  on iichb0
iic0:  on iicbus0
icee0:  at addr 0xa0 on iicbus0
icee1:  at addr 0xa0 on iicbus0
iichb1:  mem 0x4802a000-0x4802afff irq 71 on simplebus0
iichb1: I2C revision 4.0 FIFO size: 32 bytes
iicbus1:  on iichb1
iic1:  on iicbus1
sdhci_ti0:  mem 0x4806-0x48060fff irq 64 on simplebus0
mmc0:  on sdhci_ti0
sdhci_ti1:  mem 0x481d8000-0x481d8fff irq 28 on simplebus0
mmc1:  on sdhci_ti1
ti_wdt0:  mem 0x44e35000-0x44e35fff irq 91 on simplebus0
ti_mbox0:  mem 0x480c8000-0x480c81ff irq 77 on simplebus0
ti_mbox0: revision 4.0
am335x_dmtimer0:  mem 0x4804-0x480403ff irq 68 on 
simplebus0
Event timer "DMTimer2" frequency 2400 Hz quality 500
am335x_dmtimer1:  mem 0x48042000-0x480423ff irq 69 on 
simplebus0
Timecounter "DMTimer3" frequency 2400 Hz quality 500
usbss0:  mem 0x4740-0x47400fff on 
simplebus0
usbss0: TI AM335X USBSS v0.0.13
musbotg0:  mem 
0x47401400-0x474017ff,0x47401000-0x474011ff irq 18 on usbss0
usbus0: Dynamic FIFO sizing detected, assuming 16Kbytes of FIFO RAM
usbus0 on musbotg0
musbotg1:  mem 
0x47401c00-0x47401fff,0x47401800-0x474019ff irq 19 on usbss0
usbus1: Dynamic FIFO sizing detected, assuming 16Kbytes of FIFO RAM
usbus1 on musbotg1
am335x_pwmss0:  mem 0x4830-0x483f on simplebus0
am335x_ecap0:  mem 0x48300100-0x4830017f irq 31 on am335x_pwmss0
am335x_ehrpwm0:  mem 0x48300200-0x4830027f on am335x_pwmss0
am335x_pwmss1:  mem 0x48302000-0x4830200f on simplebus0
am335x_ecap1:  mem 

Re: [pfSense] Kibana ELK Stack logging

[Daniel Eschner]

i fixed everything by my self ;)

Its working now ;)



> Am 31.05.2016 um 16:23 schrieb Koray AGAYA :
> 
> Hi daniel
> 
> How can I help yours for ELK
> 30 May 2016 23:27 tarihinde "Daniel Eschner"  yazdı:
> 
>> Hi all,
>> 
>> is anyone here using Kibana with ELK Stack in actual Versions?
>> I cant get it running and maybe someone can help me out ;)
>> 
>> Cheers
>> 
>> Daniel
>> 
>> ___
>> 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] Kibana ELK Stack logging

[Koray AGAYA]

Hi daniel

How can I help yours for ELK
30 May 2016 23:27 tarihinde "Daniel Eschner"  yazdı:

> Hi all,
>
> is anyone here using Kibana with ELK Stack in actual Versions?
> I cant get it running and maybe someone can help me out ;)
>
> Cheers
>
> Daniel
>
> ___
> 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] Internet access for LAN to LAN router

[Pete Boyd]

I have a scenario where pfSense1 is running the gateway to the Internet
for LAN1 in an office with its own WAN. Another box, pfSense2, is
running the gateway out to another LAN2, a network administered by other
people, where there's a shared printer on a LAN shared by other
organisations and that LAN has its own Internet connection for those
other organisations.

pfSense2's LAN interface is on LAN1 and its WAN interface is on LAN2.
pfSense2 has as its gateway the LAN2 gateway address, which doesn't work
(for whatever reason, maybe it requires a subscription, I don't know). I
access pfSense2 using VNC from a PC on LAN1, upgrading using .tgz files,
but now that pfSense 2.3 doesn't support upgrade in this way, I need to
get pfSense2's Internet access working. I presume I do this by swapping
pfSense2's WAN and LAN assignments around, and giving its WAN the
gateway address of pfSense1?

I administer this remotely. Is there a way to do the above without
losing connection to pfSense2 half way through the procedure?

If I swap the WAN and LAN around, is different firewalling rules going
to come into play, or some other issue, and break access to the printer
for PCs on LAN1?

Or is there an alternate means of getting Internet access to pfSense2,
maybe by adding a gateway address to its LAN interface?

I already specifically allow traffic out to the printer's IP address,
and turn this off:
Interfaces -> WAN -> [ ] Block private networks and loopback addresses

Thanks in advance


-- 
Pete Boyd

Open Plan IT - http://openplanit.co.uk
The Golden Ear - http://thegoldenear.org
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold