Messages

16

18.7 Legacy Series / Re: WAN Interface not obtaining IPv6 prefix.

« on: January 16, 2019, 11:03:07 pm »

Yea I guess that makes sense.  Just request the address anyway and use the prefix.

But now when I do that, it's using the prefix I previously had (starts with 2601) instead of the one comcast just gave me (2001).  Tried rebooting, etc.  Why wont the lan update to the new prefix?


Edit:  After going back to my old config just to test a few things (DHCPv6 WAN with track interface LAN, no DHCPv6 on lan), comcast gave my router an IP starting with 2001, but all my clients are still getting IPs that start with 2601 (my old prefix).  Why are they doing that?

And is it possible to have clients that are configured with SLAAC still be registered in the local DNS so that I can resolve them using 'asdf.lan6.example.com'?

Also an issue Im having is that using Track Interface for lan, it doesn't seem to be clearing the previous settings, thus why it's using the wrong prefix.  How can I clear this?

17

18.7 Legacy Series / Re: WAN Interface not obtaining IPv6 prefix.

« on: January 15, 2019, 11:21:28 pm »

Only info I can see on the Interfaces > Overview page on WAN is that the Gateway IPv6 is fe80::259:dcff:fe79:2422.  I don't see anything about it hinting at what I should be requesting.  The DHCPv6 server fails to start currently because it isn't fetching a prefix.

18

18.7 Legacy Series / Re: WAN Interface not obtaining IPv6 prefix.

« on: January 15, 2019, 10:55:53 am »

I don't exactly know which prefix size comcast gives me.  Its a gigabit home connection.  I know they give me at least a /64 prefix because when I originally had it set to track interface on LAN, and had the WAN DHCPv6 request an ip and not just a prefix, it worked, and clients configured with SLAAC with comcast as the DHCP.

19

18.7 Legacy Series / WAN Interface not obtaining IPv6 prefix.

« on: January 14, 2019, 11:18:12 am »

I have my WAN configured to use DHCPv6 to request only a /64 prefix, and have DHCPv6 server configured to dish out addresses with the entire /64 subnet.

But when I try to renew the DHCP lease for the WAN to actually obtain a prefix, it doesn't seem to grab one. 

Running dhcp6c manually to see what happens yields the following: (em0 is WAN interface, em1 is LAN)

Code: [Select]

root@opnsense:/var/etc # dhcp6c -Df em0
Jan/14/2019 05:14:39: extracted an existing DUID from /var/db/dhcp6c_duid: 00:01:00:01:23:cf:17:58:1c:c1:de:06:d7:70
Jan/14/2019 05:14:39: cfparse: fopen(/usr/local/etc/dhcp6c.conf): No such file or directory
Jan/14/2019 05:14:39: reset a timer on em0, state=INIT, timeo=0, retrans=891
Jan/14/2019 05:14:39: Sending Solicit
Jan/14/2019 05:14:39: a new XID (c0b30) is generated
Jan/14/2019 05:14:39: set client ID (len 14)
Jan/14/2019 05:14:39: set elapsed time (len 2)
Jan/14/2019 05:14:39: send solicit to ff02::1:2%em0
Jan/14/2019 05:14:39: reset a timer on em0, state=SOLICIT, timeo=0, retrans=1091
Jan/14/2019 05:14:41: Sending Solicit
Jan/14/2019 05:14:41: set client ID (len 14)
Jan/14/2019 05:14:41: set elapsed time (len 2)
Jan/14/2019 05:14:41: send solicit to ff02::1:2%em0
Jan/14/2019 05:14:41: reset a timer on em0, state=SOLICIT, timeo=1, retrans=2083
Jan/14/2019 05:14:43: Sending Solicit
Jan/14/2019 05:14:43: set client ID (len 14)
Jan/14/2019 05:14:43: set elapsed time (len 2)
Jan/14/2019 05:14:43: send solicit to ff02::1:2%em0
Jan/14/2019 05:14:43: reset a timer on em0, state=SOLICIT, timeo=2, retrans=3982


20

18.7 Legacy Series / IPv6 addresses not accessible over internet.

« on: January 02, 2019, 11:16:53 am »

I have an experimental gitlab server accessible only on IPv6 (I set the listen address to "[::]")

I can access it over IPv6 fine, but only on my home network.  If I try to access it over the internet (say from my phone over LTE [confirmed LTE had ipv6 by going to ipv6.google.com]), the connection times out. 

My WAN interface is using DHCPv6, and the server is confirmed to have IPv6 connectivity.

Why can't I access it using ipv6 over internet?

21

19.1 Legacy Series / Adding LDAP Users?

« on: December 31, 2018, 01:57:00 am »

I was following the docs on how to add LDAP auth to OPNSense.  I added an LDAP server and using the tester, I authenticated against it successfully.

But how do I go about adding an LDAP user to opnsense?  I tried going to System -> Access -> Users but I don't see a cloud import icon anywhere.

22

18.7 Legacy Series / Re: Use Extra NIC for VLAN support.

« on: December 31, 2018, 12:23:03 am »

Do I set it to static, IP, DHCP, etc to get it to properly connect?  (The wireless router isn't being assigned an IP from DHCP, I set it manually on the wireless router itself.

23

18.7 Legacy Series / Use Extra NIC for VLAN support.

« on: December 30, 2018, 12:01:22 pm »

I have 2 NICs in the server I use with OPNSense (2 port/4 port).  Currently, the 2 port has my WAN interfance and LAN interface (plugged into an unmanaged switch).

Because the switch is unmanaged, it doesn't support VLAN tagging, so when the wireless router tries to use a VLAN it gets stripped away.

But can I use the 4 ports on the other NIC as extra LAN ports, so say any traffic coming from bce0 is assigned to a certain VLAN, that way I can just plug the wireless router directly into that.

24

18.7 Legacy Series / IKEv2/Wireguard Client

« on: December 12, 2018, 01:12:24 am »

I have Algo set up a VPN on a VPS instance that I use my for a VPN most of the time.   It only supports IKEv2 and Wireguard.

Currently there's some issues on Xbox that only affect the Northeast, but tunnelling with a VPN (not located in northeast US) fixes the issue. 

Can I configure OPNSense to tunnel all traffic (possibly only for 1 client) through a VPN tunnel?

25

Web Proxy Filtering and Caching / Re: Nginx Proxy not working?

« on: November 15, 2018, 01:23:30 am »

Ok I added the upstream server to the location.  I still can't connect.  I doubt its a firewall issue because I'm accessing it on LAN, and ufw is disabled on the machine its trying to proxy to.

I am not familiar with tcpdump, but when I tried to access it in the ssh shell, I couldn't immediately see any useful information.

If it means anything, the page I'm trying to connect to is also protected by a .htpasswd file.

26

Web Proxy Filtering and Caching / Nginx Proxy not working?

« on: November 14, 2018, 02:46:03 am »

Here are my settings: https://imgur.com/a/2aa6CRY

I'm trying to use the nginx plugin to add a few proxy addresses to my network.  For example, I want to proxy `nzb.example.com:80` to `10.0.1.11:6789`, but with the above settings, when I go to nzb.example.com, it times out when trying to connect.

Any advice on configuring this plugin?

27

Web Proxy Filtering and Caching / HAProxy configuration questions

« on: October 23, 2018, 11:09:50 am »

I'm trying to configure HAProxy to allow outside access to some services (like webgui's for various services).

As an example, I'm trying to allow `freeipa.example.com:443` redirect to `ipa.example.com:443` (this being the hostname of the virtual machine.  Internal DNS resolves this to 10.0.0.15)

But connections timeout when I try to connect to them.  I also tried port forwarding 443 to 10.0.0.1 (the IP of opnsense)

Any help?  Am I doing something fundamentally wrong?

(Attached is my Real Server, Backend Pool, and Virtual Service configurations)
Edit: attachments too large.  Here's imgur album: https://imgur.com/a/DRvd5AM

28

18.7 Legacy Series / Re: Am I doing Port Forwarding Wrong?

« on: October 19, 2018, 12:37:47 am »

Bump.  Anyone?  I've read guides and believe I have it set up properly, but it just won't work.  Any help?

29

18.7 Legacy Series / Am I doing Port Forwarding Wrong?

« on: October 17, 2018, 12:00:42 am »

I'm trying to get port forward working, but it just doesn't seem to be working.

My Xbox has an Open NAT, but I'm not sure which of the 3 rules I have enabled are allowing that.
Plex isn't accessible outside my network.
And when I try to ssh using `ssh user@example.com -p 22333`, the connection times out.

I also can't connect to the VPN server.

How do I get port forwarding working

30

18.7 Legacy Series / Unable to port forward SSH and unable to SSH on IPv6?

« on: October 11, 2018, 09:10:46 am »

I'm trying to make it so that when I ssh mydomain.com on port 22555, it will redirect it to 10.0.0.15 on port 22.

My NAT port forward rule is as follows:
Source Address: *
Source Ports: *
Destination Address: WAN address
Destination Ports: 22555
NAT IP: 10.0.0.15
NAT Ports: 22

But it doesn't seem to be letting me connect when I try `ssh user@mydomain.com -p 22555` my VPS.

Also when I try to `ssh ipv6:addr:here -p 22555` or `ssh ipv6:addr:here`, it also times out.

What am I doing wrong?