Messages

Hi there,

GEOIP Service stopt working on Dec 30 / 2019. Obviously  maxmind is no more providing the geolite database via
geolite.maxmind.com/download/geoip/database/*

Any hints / solutions to get this fuction working again ?

Best regards
Michael

Are you using ipv4 or ipv6?

ipv4: you should check if someone loged into pfsense. The lan-devices are not reachable from internet unless you set up NAT

ipv6: the lan devices could be reached from internet - but if the device firewalls are "up to date" there should be no problem. The accesspoint without firewall should be checked twice

Michael

I've got two wan connections
- pppoe0 - DTAG VDSL
- em0_vlan51 - Vodafone Cable
both with fix ipv4-adress and fix ipv6 /56 subnet. Both providers need dhcp to hand out an ipv6 ip to the opnsense/router. I'm able to set up wan1 (DTAG) OR wan2 (Vodafone) and it works trouble-free.
When i'm trying to set up wan1 AND wan2 the opnsense will start two dhcp6c processes - both bindung to *:546 and the problems start.

# sockstat|grep dhcp6c
root     dhcp6c     55384 3  dgram  -> /var/run/logpriv
root     dhcp6c     55384 7  udp6   *:546                 *:*
root     dhcp6c     85812 3  dgram  -> /var/run/logpriv
root     dhcp6c     85812 7  udp6   *:546                 *:*

# ps ax|grep dhcp6c
55384  -  Is      0:00.16 /usr/local/sbin/dhcp6c -d -c /var/etc/dhcp6c_opt5.conf -p /var/run/dhcp6c_pppoe0.pid pppoe0
85812  -  Is      0:00.12 /usr/local/sbin/dhcp6c -d -c /var/etc/dhcp6c_opt13.conf -p /var/run/dhcp6c_em0_vlan51.pid em0_vlan51

if one dhcp6c process will start renewing adress, the other one will get the answer
/var/log/dhcpd.log:
Nov  6 07:48:18 OPNsense dhcp6c[55384]: Sending Solicit
Nov  6 07:48:18 OPNsense dhcp6c[85812]: unexpected interface (26)

so only one ipv6 connection will be ok - ipv4 works without trouble.

Is there a way to bind the dhcp6c client to an interface or merge the config files so only one dhcp6c is used?

Michael

Hi Nils,

bridge mode is activated and i'm not getting an ip in the Range 192.168.x.x. The problem still exists even if the modem ist powered off -> no change to get a wrong answer by the modem.

Michael

Hi Franco,

faulty leases could be an option, but in my case the new vodafone modem is still "offline". There's nothing connected to the wan2-opnsense-interface - nevertheless after an reboot the DHCP is marked "up" with ip "0.0.0.0"

Michael

Hi,

i'm using opnsense the last years without any issue, but now i've got a problem i can't handle.

I've got an pppoe as WAN (Telekom VDSL - working flawless for years) and just want to add an second WAN connection for failover (Vodafone cable) which uses DHCP. Everything is working, but if i reboot the opnsense while the Vodafone dhcp-server is not reachable (modem offline), the WAN2 interface get's 0.0.0.0 as IP and so  its not possible to set the default route for opnsense -> no traffic from LAN to WAN.
In "Interfaces / Overview" i can see, dhcp for WAN2 is marked "UP" - if i "renew" dhcp lease on WAN2 it is marked "down", the 0.0.0.0 on WAN2 is gone and i can setup an default route via pppoe.

It seems to be a problem with dhcp lease on startup - any idea? Am i doing something wrong?

opnsense 17.7.6

wfr
Michael