What are you replying to there?

@andrealucia said in Chrome password auto-fill breaking IPv6:

This prevents the IPv6 gateway from starting. In years of running pfsense, I've never seen this behaviour.

When pfSense boots, interfaces are mounted, protocols are started, things like IPv4 and IPv6 are activated, links are build. IP's are set, masks and gateways are defined.
All this happens long before processes like a web server (nginx), that hosts the pfSense GUI, are started.

Yet the login of a user using some browser disrupts the IPv6 gateway ?
How ?

@andrealucia said in Chrome password auto-fill breaking IPv6:

Is there any other work-around?

I thought the issue was solved. It's a browser behaviour.

I work in remote! with a time sheet, I never work like that, but I know im blessing. A lot companys is going down cause this virus.

You will also need a WAN connection, as well as a switch or device to connect to the LAN port.

Xmas in April ;) heheheh

edit the topic please [solved]
brNP

Graphène based sensors might pull this one off.

Enter your router's IP address into your favorite web browser. Log in as the administrator. Go to settings and look for an option titled WiFi name or SSID. Enter your new WiFi name.

@Bob-Dig said in VLAN possible with virtual Switches in Hyper-V?:

@Mats said in VLAN possible with virtual Switches in Hyper-V?:

The first one is to create a trunk adapter and then assign Vlans in PFSense. This had some issues on 2012R2 but is rock solid on 2016. I do use this config myself

I had absolute no success with that.
xxCapture.PNG

Also is it normal that if you add those virtual NICs, that you lose the normal NIC? And then have to use vlan on everything?

And also I am using VMware WS on the other side (Client), which probably making things worse.

The "normal" nic is vlan 0 so that should be doable. I did not have a VM with that config at the moment so I couldn't test it.

You can try method2 and see if that works for you. If it does we know the issue is with the trunking of the adapter

I have no idea, I've never tried them. I know some VPN services can use IPSec, most are OpenVPN only though.

Personally I consider all those VPN services of limited use at best. Setting up your own VPN server that you control is better in many ways.

Steve

This is going to be the attacker's machine if you want to have an internal pentesting environment.

I mean I realise this is off-topic but I don't think you'll get much love for dropping pfSense. 😉

The one area where a device like that might be a better choice is if you need to connect multiple games consoles to the same game/server from behind it. For some reason I've yet to understand the networking code in many consoles/games appears to be straight out of 2002. They often use fixed source and destination ports and cannot cope with that being changed. Hence the need to set outbound NAT rules with fixed ports for games consoles. They often also require inbound connections be allowed directly and that often means UPnP. A terrible idea in a security product.
The actual issue appears to be the fact that miniupnpd, the UPnP daemon used in pfSense, does not support 'masquerade' for FreeBSD/pf. It does in Linux which is what almost every other sogo router is using.
See: https://redmine.pfsense.org/issues/7727#note-3

If that is something that may apply you could always try OpenWRT on whatever hardware you're running pfSense on.

Steve