How to access pfSense GUI via IPV6 ?
-
@jknott thank you! Any idea what caused it and how do I revert the appliance to the 'normal' operation with IP4 address used?
Do you get IPv6 from your ISP
no, I am getting static IP from my ISP. I put the appliance on LAN temporarily, just to-preset it without losing internet, and it switched to the local address... -
Every IPv6 capable device should have one of those. There's really no need to turn it off, as any packets with a link local address aren't going anywhere.
Also, "static" has nothing to do with this. IP addresses, can be static or automatically assigned. If you have IPv6 from your ISP, you should see an address starting with 2. I get my IPv6 addresses from my ISP, using DHCPv6-PD, which provides both a WAN address and prefix for local networks.
-
Sorry, I must be not explaining myself correctly... how can I force pfSense to assign IP4 gateway to its LAN, so I can get back to GUI?
-
@tzheruh Reset it again? You must do something wrong.
-
You normally just assign an IPv4 address to the LAN interface. What's happening or not happening?
-
@jknott
After the reset it just did not assign IPv4 address. Now I can not check it or fix it it, since GUI is linked to the IP6 local link and I can not log in... I reset it multiple times since, it does not change anything. -
Another possibility is to use ssh. It ssh root@<link local address><interface>. Use the link local address of pfsense and the interface is whatever is used on your computer to connect to it. I just tried this command with eth0 on my notebook. Once there, there's an option to set IP addresses.
Here is the command I used:
ssh root@fe80::4262:31ff:fe12:b66c%eth0Failing that, you're left with a serial port connection.
-
And what about the most important access you have ?
The console access.If something is wrong with an interface, like the LAN, you are locked out.
That's where the console access comes in.edit : @JKnott is talking about the same thing.
No "help me" PM's please. Use the forum, the community will thank you.
Edit : and where are the logs ?? -
If you see no IP address on your LAN the most common cause in a subnet conflict.
After resetting it the LAN will try to use the default IP, 192.168.1.1, but it your WAN is connected to something also using that subnet it will be invalid.
Disconnect the WAN or set the LAN to a different subnet.
Steve
-
Of course, the problem with that is you need a serial port on the computer(s) and a "null modem" cable. I use a USB serial port, as most computers don't have built in serial ports available. My Qotom computer does though.
-
Guys, thank you, ended up with the console access and rebuilding the LAN configuration through it, all is working now...
