Menu

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.

Show posts Menu

Messages - raspberryswirl2

#1
21.7 Legacy Series / IPv6 NAT driving me nuts
April 06, 2022, 08:41:37 PM
Hi,

I am behind a cable router, which is not handing me down prefixes - so my opensense needs to NAT the IPv6 - this is possible - and I know, not the optimal solution, but please no discussion about that :(
I was looking already in several documentations - and hence I upgraded the opensense I am really thinking of reinstalling with a fresh install, because its driving me crazy, because I had success but only for a short time.
I am doing something wrong - or misconfigured something

Here are the details:
Cable Router - Opensense - WLAN ROUTER - CLIENTS

System is on 21.7.8 - I have enabled DHCPv6 and also in the Services Router Advertisments Asssisted - so its is doing SLAAC.
Behind opensense is an ddwrt wifi router - configured with radv - nothing else, FW disabled
The linux and the windows system get an IPv6 address from opensense, also a lease and know their DNS server now.
from those systems I can ping each other and also the opensense (!)
but although the Firewall OUTBOUND NAT is configured with my source adresses (like (fd42:4242:4242:4242:ffff:ffff:ffff:8 and WAN address) its not going out:

on windows:
tracert -6 google.com

Tracing route to google.com [2a00:1450:4016:809::200e]
over a maximum of 30 hops:

  1     *        *        1 ms  OPNsense.localdomain [fd42:4242:4242:4242::]
  2     *        *        *     Request timed out.


From opensense shell - I can ping google successfull.
In the FW:
LAN: LAN TO ANY - all traffic IPv6 allowed
WAN:
WAN TO ANY -  TCP/IP V6 allowed
WAN TO ANY -  ICMP V6 allowed

thanks
jon

funfact: I played around with restarting the DHCP and also configured the WLAN router with DDWRT and I had some successes, but there are not reproducible. So really some assistance would be very apricated.
#2
Hi Franco!

thank you! i thought about that. And as you explained, I did this - there is still a switch between the FW and the rest - BUT: I am using a virtual IP as the default GW in the same network. could that be the problem? Or a bridge i put over the WAN?

best regards
jonathan
#3
Hi!

I am new to opnsense, it is a great product.
I recently noticed, that running ssh on the same subnet brings me to connection interruption with ssh -
I changed allready Firewall Optimization to conservative, in FW -> Settings -> Advanced
regarding to this post
https://servernetworktech.com/2013/05/pfsense-vlans-and-ssh-disconnects/
and it is better working!
Today also in Settings -> Normalization
IP Do-Not-Fragment   
and now testing again)

Does anybody has another hint, to improove this issue?
thank you
rasp