Netgate SG-1000 microFirewall

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Messages - xbipin

Pages: [1] 2 3 4 5 ... 109
Goto the pfsense web gui firmware settings page and select Dev branch rather than stable then check for updates from same place and it will show 2.4.2 Dev directly which you can upgrade to but if your already on 2.4.1 then editing the config file to rename the dot to _ is the only option to get internet working

well i too run many boxes which r located in different countries and after testing 2.4.2 dev locally upgraded all of them to it and all work fine, there isnt much changed between 2.4.1 and 2.4.2 dev so its fine, if the dev marking scares u then wait for the stable but for now the only way to solve this pppoe over vlan issue is to use the dev version

The biggest pain in the ass comes when you update remotely the box, through a VPN connecting via the PPPoE connection. You won't be able to fix anything until you go there physically. Which can cause severe downtime...

directly upgrade to 2.4.2 dev from 2.4 and it will be fine, just skip the 2.4.1 update

2.4 Development Snapshots / 6to4 tunnel lan dhcp static mapping confusion
« on: October 30, 2017, 11:58:27 pm »
my isp started using 6to4 tunnel over ipv4 pppoe so i wanted to try this in pfsense, being a beginner in ipv6 i fail to understand one thing or maybe something i have configured something wrong.

my isp gives out the below ip, at least thats what the interface page says (xxxx = masked bits)
Code: [Select]
IPv6 Address - 2002:xxxx:b185::
Subnet mask IPv6 - 16
Gateway IPv6 - 2002:xxxx:6301::

the wan interface ipv6 config type is set to 6to4 tunnel and the lan set to track wan interface with prefix id 0, so far this is all fine, im able to ping firewall from outside using ipv6 and some firewall rules. Problem is the DHCPv6 Server and RA. i have the set the below in dhcp server

Code: [Select]
Subnet - Prefix Delegation
Subnet Mask - 64 bits
Available Range - :: to ::ffff:ffff:ffff:ffff
From - ::0:0:0:0
To - ::0:0:0:ffff

the lan clients get proper ipv6 using dhcp and they r able to surf ipv6 sites also but suppose i want to add static dhcp mappings then suppose if the wan disconnects and reconnects and gets a new ipv6 ip then the lan clients ip dont get modified with the  new Prefix Delegation subnet appended at the start.

does this mean i need to use a dhcp pool only for lan clients and cant set static ip mappings or is it that the ipv6 address needs to be typed in a special format so the network id etc get auto added when it changes?

for now i had to rename all igb.20 to igb1_20 to make it connect, why would they release it with such a bug

I have two pppoe interface over VLAN



and doesn't can i rename for working?

u need to rename under the pppoe as well as the vlan section in the config file, works well for me so far

for now i had to rename all igb.20 to igb1_20 to make it connect, why would they release it with such a bug

i just updated to 2.4.1 on the apu2 and now cant connect to wan at all which is pppoe over vlan

yup this was the change i guess done at that time

no im on the serial image and as far as i remember i had filed a bug request at the time i found out this issue and i think some1 patched something at that time, let me go find what the patch was

whats in ur /boot/loader.conf and /boot/loader.conf.local

2.4 Development Snapshots / remove vidconsole from console settings for apu2
« on: September 26, 2017, 11:44:27 am »
can some1 patch the pfsense code such that the /boot/loader.conf sets console="comconsole" as default for apu2 board rather than console="comconsole,vidconsole" coz when vidconsole is present in that string then the welcome message on serial console comes broken making it impossible to boot into single user mode

this got fixed on the apu2 so im assuming it works on sg-1000 as well coz both run the exact same config and both gave same symptoms

i tried on 2 apu2 boxes and now works all good, can any1 point me to the actual commit that fixed this?

Hardware / Re: apu2 internal TTL com port
« on: September 26, 2017, 03:37:02 am »
ok finally got it working, the reason for garbage was along with the tx and rx line gnd also needs to be connected and my gnd pin on the adapter had a loose solder joint so gnd pin wasnt making contact, on the new adapter connected it and serial console started showing on com2 without issues, thanks for all the help

my crash log attached as follows, im also having same issue on client box when i enable shaping, sorry the log was too long to capture completely

Pages: [1] 2 3 4 5 ... 109