Second Lan network same interface

[Derelict]

And with NPt to an unused /64 on pfSense WAN:
derelict@Host-B1:~$ ping6 -n -c 3 -I fd08:1e26:8fea:525b:98b3:deff:fe87:fa4b www.google.com
PING www.google.com(2607:f8b0:400e:c05::63) from fd08:1e26:8fea:525b:98b3:deff:fe87:fa4b : 56 data bytes
64 bytes from 2607:f8b0:400e:c05::63: icmp_seq=1 ttl=46 time=59.6 ms
64 bytes from 2607:f8b0:400e:c05::63: icmp_seq=2 ttl=46 time=83.8 ms
64 bytes from 2607:f8b0:400e:c05::63: icmp_seq=3 ttl=46 time=58.7 ms

–- www.google.com ping statistics ---
3 packets transmitted, 3 received, 0% packet loss, time 2003ms
rtt min/avg/max/mdev = 58.704/67.398/83.847/11.640 ms

[JKnott]

I'll have to go through the stuff you provided, howerver I made some changes and did some more testing.  At the moment, the configuration is as follows:

LAN global & ULA
LAN4 ULA only
VLAN3 ULA only

The desktop computer has both LAN and VLAN3 configured and the notebook is on LAN4 only.

If I ping the laptop by forcing ping over VLAN3, it works.  However, when via LAN, no response.  Wireshark on the notebook shows both request and reply, but on the desktop, only the request.  From the pfSense computer, I can ping the notebook and the VLAN3 address of the desktop, but not the LAN address.  Wireshark does not show any ping requests from pfSense to the LAN interface  So, there is still something about the LAN interface that's causing problems.

I see you have a ULA address fd08:1e26:8fea:525b::1 on the LAN interface.  How did you put it there?  I do not have one.  I used a virtual IP last night, but this morning, the virtual IP was there, but the global address was gone.

The network ULA addresses are as follows:
LAN  fd48:1a37:2160:0::
VLAN3  fd48:1a37:2160:3::
LAN4  fd48:1a37:2160:4::

Netstat -r on pfSense shows:

fd48:1a37:2160:3:: link#8            U      bge0_vla
fd48:1a37:2160:3:: link#8            UHS        lo0
fd48:1a37:2160:4:: link#2            U          em0
fd48:1a37:2160:4:: link#2            UHS        lo0

Note there is no line for fd48:1a37:2160:0::.

There is also this on the WAN interface:

fd07:f798:3:16e::  link#3            U          re0
fd07:f798:3:4172:: link#3            U          re0

There are no other ULA addresses listed.  So, pfSense doesn't have a route to fd48:1a37:2160:0::.

[JKnott]

I think I found it.  I had to set the VIP prefix to /64.  Also, curious that the pfSense graphical admin doesn't show the 2nd address on either the dashboard or interface status.  Netstat -r does though.

[johnpoz]

"I had to set the VIP prefix to /64"

what else would you have set it too?

[JKnott]

The default is /128, so if you forget to change it…

Now I can add gazillions of security cameras to that network!  ;)

[JKnott]

I just tried pinging ipv6.google.com from a computer with a ULA and I see the requests heading out of the WAN port.  I guess I should create a rule to block ULA addresses.

[Derelict]

Yup. Just like RFC1918.

[JKnott]

I just created a floating rule to block fc::/7 in both directions, but the pings are still leaving the firewall.

[Derelict]

Did you kill the existing states?

Or at least stop and restart the ping?

[Derelict]

You should also check quick there.

[JKnott]

I did try it and it didn't make any difference.  I'm using Wireshark, to monitor the cable from the firewall to cable modem.  I just set it again and it's still not blocking.

[JKnott]

Well, that virtual IP killed my network again.  I had to remove it for things to work properly.

[Derelict]

IDK again, man. Works here…

Packet capture on WAN for fc00::/7 shows nothing as well.


[JKnott]

I have absolutely no idea what's causing these problems.  I'm running the latest version on a refurb computer.

[Derelict]

Everything I am doing is 2.4-RC on a XenServer VM. I have no reason to believe 2.3.4_1 on a physical would be any different.