Re: [pfSense] Mini-USB console on new pfSense certified hardware

[Jeremy Porter]

There is an on-board UART to USB converter on the
RCC-VE/DFFv2/4860/8880/2440/2220.   This is wired directly to the
chipset uart on the Rangely, at system voltage levels, not at RS232
levels.  (The USB convert chip is cost comparable to a RS-232 voltage
driver chip in cost, and has a smaller board footprint.)  Additionally
the connect takes up less back-panel space.

There are no test points brought out, if there were you would need a
level shifter, and an isolator to protect the SOC.

Most modern systems have USB Host ports, which is all that is required
for the USB serial interface to work.  Any small system, can manage
quite a few hosts with a powered usb hub.  (We actually use Beaglebone
black as terminal servers).  We actually switched all our remaining
terminal server systems over to these types, by getting a rack-mount 32
port USB to RS-232 converter.

On 8/1/2016 3:10 PM, Karl Fife wrote:
> USB HOST to RS232 adapter
>
> It appears that the new rangely-based pfSense certified hardware
> (2440, 4860) has a mini-USB (client) port for console access.
>
> This "convenience" is ironic for us because I actually prefer RS232,
> (because that's the interface everything else uses).  As far as I
> know, I can't buy a USB-to-RS232 adapter because the dongles you buy
> are all USB *clients* (as is the router) therefore I couldn't connect
> a dongle adapter to pfSense and connect with hardware RS232.
>
> The other irony is that the pfSense board doubtless has the UART right
> there on the board ahead of the USB adapter.   I wish there were a USB
> Header I could grab.  Can anyone say whether there's a way to grab
> serial from the board directly?
>
> While this baked-in adapter may be in improvement for many, I'm
> guessing it's as inconvenient others because RS232 is a standard
> handoff.  Everything else uses it, so we build solutions around it. 
> With hardware RS232, I can attach a Serial-to-IP adapter connected to
> our management network, or I can run serial over twisted pair to a
> remote hardware serial port.
>
> Any elegant solutions to this change?
>
>
>
>
> ___
> 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] Mini-USB console on new pfSense certified hardware

[Moshe Katz]

I don't have one of these myself yet, but they look to be based on the ADI
RCC-VE 
platform.
The documentation there suggests no way to get around needing the USB
drivers.

It is implied in the manual for the board that the reason for this is to
allow an FPGA serial console and a CPU serial console to share the same
cable - it would just show up on the computer as two COM ports.

The easiest solution I can think of offhand would be to get a small
computer like a Raspberry Pi and use that as your Console-to-IP adapter.
You could also use a set of USB over twisted pair adapters, but those
aren't necessarily the most dependable pieces of hardware over long
distances.

Moshe

--
Moshe Katz
-- mo...@ymkatz.net
-- +1(301)867-3732

On Mon, Aug 1, 2016 at 4:10 PM, Karl Fife  wrote:

> USB HOST to RS232 adapter
>
> It appears that the new rangely-based pfSense certified hardware (2440,
> 4860) has a mini-USB (client) port for console access.
>
> This "convenience" is ironic for us because I actually prefer RS232,
> (because that's the interface everything else uses).  As far as I know, I
> can't buy a USB-to-RS232 adapter because the dongles you buy are all USB
> *clients* (as is the router) therefore I couldn't connect a dongle adapter
> to pfSense and connect with hardware RS232.
>
> The other irony is that the pfSense board doubtless has the UART right
> there on the board ahead of the USB adapter.   I wish there were a USB
> Header I could grab.  Can anyone say whether there's a way to grab serial
> from the board directly?
>
> While this baked-in adapter may be in improvement for many, I'm guessing
> it's as inconvenient others because RS232 is a standard handoff.
> Everything else uses it, so we build solutions around it.  With hardware
> RS232, I can attach a Serial-to-IP adapter connected to our management
> network, or I can run serial over twisted pair to a remote hardware serial
> port.
>
> Any elegant solutions to this change?
>
>
>
>
> ___
> 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] Mini-USB console on new pfSense certified hardware

[Karl Fife]

USB HOST to RS232 adapter

It appears that the new rangely-based pfSense certified hardware (2440, 
4860) has a mini-USB (client) port for console access.


This "convenience" is ironic for us because I actually prefer RS232, 
(because that's the interface everything else uses).  As far as I know, 
I can't buy a USB-to-RS232 adapter because the dongles you buy are all 
USB *clients* (as is the router) therefore I couldn't connect a dongle 
adapter to pfSense and connect with hardware RS232.


The other irony is that the pfSense board doubtless has the UART right 
there on the board ahead of the USB adapter.   I wish there were a USB 
Header I could grab.  Can anyone say whether there's a way to grab 
serial from the board directly?


While this baked-in adapter may be in improvement for many, I'm guessing 
it's as inconvenient others because RS232 is a standard handoff.  
Everything else uses it, so we build solutions around it.  With hardware 
RS232, I can attach a Serial-to-IP adapter connected to our management 
network, or I can run serial over twisted pair to a remote hardware 
serial port.


Any elegant solutions to this change?




___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

[pfSense] 502 Bad Gateway

[Paul Galati]

This morning I logged into the router to bring up the dashboard as I usually 
do.  I began my day and some time later I revisited the dashboard to check on 
things and I get a 502 bad gateway error.  I did not make any changes to the 
config at all today.  From the beginning I did enable https login and so when I 
attempt to login I do get the certificate notice. Once I accept that I then get 
the 502 bad gateway error with a nginx underneath it.  The router has been up 
about 5 days.

Before I posted this I did a search and found this was a common issue.  Was 
2.3.2 supposed to fix this?  I do have openvpn and IPSec widgets enabled on the 
dashboard.  Should they be turned off?  What about the OS update engine?

Thanks for your help.
Paul
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

[pfSense] 32-to-64 bit upgrade - unbound needn't be un-bound

[Karl Fife]

Over the weekend I did some 32-to-64 bit architecture upgrades on 
NanoBSD systems with 64-bit hardware.


The migrations were seamless EXCEPT that in every case, the DNS 
forwarder [sic] would fail to work unless selectively un-bound from IPv6 
interfaces.


On all of the systems, there was at least one interface included by the 
default "all" which is not dual-stack.  I suspect this is why dnsmasq 
was choking.  HOWEVER, I bring it up here in the forum because the very 
same configs would not cause DNS to choke if restored to 32-bit 
architecture of the same version.


Strange.

In my case, I've switched those systems to use unbound/Resolver, and in 
all cases, all systems with unbound don't need to be un-bound from IPv6 
interfaces.


Most of these configs have been rolled forward since early 2.0, so I 
suspect that there may be idiosyncrasies in the config (e.g. old 
defaults) that might be responsible (e.g. settings that may not cause 
this issue to express itself in a brand new install).


Any hypotheses of this weird observation?



___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Installation issues of latest release (2.3.2) resolved?

[Vick Khera]

On Sat, Jul 30, 2016 at 12:19 AM, Jim Thompson  wrote:
> As a reminder, pfSense 2.4 will not support i386, and will not support the
> 'nano' image.

Does this imply that we will need to do a full re-install on our
Netgate APU's or will there be a clean self-upgrade process?
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Installation issues of latest release (2.3.2) resolved?

[Vick Khera]

On Fri, Jul 29, 2016 at 10:37 PM, Ryan Coleman  wrote:
> So does this effect APUs running the AMD64 architecture?

I updated from 2.3.1 to 2.3.2 the APU at my home office with zero
problems. It just took a good long time to clone the boot slice before
updating, which also took a long time. The actual downtime was minimal
as it does boot really fast.
___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold

Re: [pfSense] Unable to check for updates?

[Kemecsei Gábor]

Helped console update!
(ssh -> 13)

thx

2016.07.29. 21:03 keltezéssel, Dan Langille írta:

On Jul 29, 2016, at 5:20 AM, Kemecsei Gábor  wrote:

"Unable to check for updates"

It's ok?

I use:
"2.3.1-RELEASE-p5 (i386)
built on Thu Jun 16 12:53:31 CDT 2016
FreeBSD 10.3-RELEASE-p3 "

The Package Manager reply:
"Unable to retrieve package information."

I have a bug or pfSense?


Is this a DNS issue?  Sounds like a problem I had until enabled DNS Forwarder 
on localhost:

see https://forum.pfsense.org/index.php?topic=115197.msg641301#msg641301 




___
pfSense mailing list
https://lists.pfsense.org/mailman/listinfo/list
Support the project with Gold! https://pfsense.org/gold