PPPOE is constantly reconnecting

Started by altione, October 22, 2024, 06:55:35 PM

Previous topic - Next topic
Hello friends. I have a problem with the PPPoE connection.
- I have an Internet service provider linked to the MAC address
- I get a static local address, gateway   
- And then, according to this data, I am assigned a public address

The problem is that I see an error in the /var/log/system/system_20241022.log file 
I see a mistakes:
arpresolve: can't allocate llinfo for 10.0.x.x on vtnet1
and
/usr/local/etc/rc.newwanip: Failed to detect IP for interface wan

And the pppoe connection is constantly reconnecting.

And this advice did not help
https://forum.opnsense.org/index.php?topic=29556.msg143071#msg143071

root@OPNsense:~ # opnsense-patch 7aaa6a263b1 bb4743a7322
Found local copy of 7aaa6a263b1, skipping fetch.
Found local copy of bb4743a7322, skipping fetch.
1 out of 1 hunks failed while patching etc/inc/system.inc
1 out of 1 hunks failed while patching www/services_dhcp.php
1 out of 1 hunks failed while patching www/services_dhcpv6.php

Type   opnsense Version 24.7.6. Deployed on a proxmox virtual machine. pppoe works fine on another router.

Please tell me what else can I try to solve?

Quote from: altione on October 22, 2024, 06:55:35 PM
arpresolve: can't allocate llinfo for 10.0.x.x on vtnet1
I guess, this is your gateway IP. No reason to obscure private IPs here. We will not able to access it anyway.

This almost means, that the node is not reachable in the configured L2.

See https://wiki.opnsense.org/troubleshooting/gateways.html

I don't think, that the private gateway IP should really be outside of the interface subnet.
But maybe you can give some more details on how you set up the interface.

Yes, that's right. This is the address of my gateway.

root@OPNsense:~ # cat /var/db/dhclient.leases.vtnet1
lease {
  interface "vtnet1";
  fixed-address 10.0.38.193;
  option subnet-mask 255.255.252.0;
  option routers 10.0.36.1;
  option domain-name-servers 10.0.36.3;
  option dhcp-lease-time 864000;
  option dhcp-message-type 5;
  option dhcp-server-identifier 172.16.0.3;
  option option-82 1:6:0:4:0:3:1:19:2:8:0:6:e8:28:c1:b5:b0:40;
  option classless-routes 22,172,16,0,10,0,36,1,16,10,0,10,0,36,1;
  renew 6 2024/10/26 18:14:34;
  rebind 3 2024/10/30 12:14:34;
  expire 4 2024/10/31 18:14:34;
}
lease {
  interface "vtnet1";
  fixed-address 10.0.38.193;
  option subnet-mask 255.255.252.0;
  option routers 10.0.36.1;
  option domain-name-servers 10.0.36.3;
  option dhcp-lease-time 864000;
  option dhcp-message-type 5;
  option dhcp-server-identifier 172.16.0.3;
  option option-82 1:6:0:4:0:3:1:19:2:8:0:6:e8:28:c1:b5:b0:40;
  option classless-routes 22,172,16,0,10,0,36,1,16,10,0,10,0,36,1;
  renew 6 2024/10/26 19:02:54;
  rebind 3 2024/10/30 13:02:54;
  expire 4 2024/10/31 19:02:54;
}
root@OPNsense:~ #

And I don't see this gateway in System-Routes-Status when the pppoe connection is established.
Do I need to specify OPNsense somewhere that this IP is a provider?

Check if you have "Block private networks" checked in the interface settings. If so, try unchecking it.

Yes, I tried to remove this checkmark, but to no avail :(

When I configure my WAN interface in DHCP mode, I get the desired IP address and the gateway is displayed 10.0.36.1.
When I switch my WAN interface to PPPoE mode, I am assigned a public address, but the default gateway is replaced with 192.168.0.1. And information about the route 10.0.36.1 does not appear anywhere else

Quote from: altione on October 22, 2024, 09:21:43 PM
And I don't see this gateway in System-Routes-Status when the pppoe connection is established.
Which one?

10.0.36.1 is obviously given to you as default gateway. Is it this one, arpresolve is logging errors?

So you get your interface IP via DHCP. From a local device?

Presumably it doesn't respond to the ARP request if the error appears. The ARP cache is flushed after 20 minutes by default and OPNsense needs to renew it then. But seems, this fails.

Did you obey the installation hints for virtualization?
https://docs.opnsense.org/manual/virtuals.html

Friends, thanks to all those who are not indifferent. I think you've given me the right idea.
Initially, I only had two WAN (PPPoE) and LAN interfaces.
I have now slightly modified the scheme and added a new OPT1 interface(PPPoE).
So now my WAN interface receives DHCP from the provider and the gateway automatically.
The OPT1 interface is connected via PPPoE. The default route has become 192.168.10.1.
And the provider's gateway 10.0.36.1 is also pinged.
The message
arpresolve: can't allocate llinfo for 10.0.36.1 on vtnet1
really just said that the gateway was basically unavailable. With this setup, everything seems to work well. Thanks!