WAN over PPPOE - default Route is not set #850

andreasvel · 2016-03-23T08:05:31Z

Hi,
im using PPPOE for my WAN - if its the default gateway the IPv4 default is not set.
The Default IPv6 is set corect

fichtner · 2016-05-30T19:36:39Z

Andreas, the problem with your reports is that they miss vital information. Please read the following and report back:

https://github.com/opnsense/core/blob/master/CONTRIBUTING.md

It's simply not possible to help with no information about your setup, logs, etc.

fichtner · 2016-06-21T18:33:40Z

I'll still need version info and additionally a dump of the following file(s), but careful with embedded credentials...

# ls /var/etc/mpd_*.conf

andreasvel · 2016-06-22T11:30:07Z

i will sent you an email

andreasvel · 2016-07-07T19:27:06Z

any news with the infos from my email?

fichtner · 2016-07-16T18:10:16Z

Experimental patch at b349470, it looks like a missing Multi-WAN awareness issue.

fichtner · 2016-07-23T05:54:25Z

This is on the 17.1 development track for now (opnsense-devel package under 16.7)

fichtner · 2016-07-23T07:17:09Z

I haven't heard of further problems from @andreasvel and it's currently queued up for inclusion in 16.7.1. Thanks!

andreasvel · 2016-09-14T12:03:52Z

Its there again.. 👎
on OPNsense 16.7.3-amd64

tadaog · 2017-01-17T15:34:42Z

The bug is back now too in OPNsense 16.7.13-amd64
If I set:

route add -net default -interface pppoe0

everythings works but any change in config (such as in Web Proxy removes the IPv4 default route manually added previously.

fichtner · 2017-01-17T15:51:03Z

It looks like "the" bug never went away completely, looking like a narrow race condition, which makes this hard to trace with the amount of additional info provided.

17.1 is almost out, featuring a new FreeBSD version. If anything we need to see how it performs there and think about what can be done?

JackTrapper · 2017-05-17T03:00:38Z

I had this today. I couldn't figure out why it could not ping, traceroute, or connect to anything on the Internet. If i forced the use of WAN interface it would work fine.

Finally i found the routes screen. The default route is set to go the physical WAN port, rather than the PPPoE virtual port:

I couldn't find anything in the UI to repair, reset, change, or fix it. So i had to yank the live USB stick and revert to pfSense.

fichtner · 2017-05-17T03:39:32Z

I couldn't find anything in the UI to repair, reset, change, or fix it.

How about release/renew the PPP lease from the Interfaces: Overview page? Or saving/reapplying the WAN configuration? Or console option 11 or reboot... ;)

JackTrapper · 2017-05-17T12:09:46Z

I did disconnect the PPPoE connection, so the WAN interface was down; and then connected it again
I did re-save the WAN configuration; thinking (hoping) that it simply would fix itself

Strictly speaking i did reboot; but without the Live USB stick in. I'll try again tonight. I had to get the Internet back up before people started complaining too much.

JackTrapper · 2017-05-18T01:33:53Z

Well i tried it again; live booting off a USB stick. The wizard ran on first use because it was, by definition, a fresh install.

Same thing. The default route is set to go out the physical WAN port:

Unpluged the USB stick to revert to pfSense in order to wait for a fix.

fichtner · 2017-05-25T10:36:22Z

@JackTrapper, can you walk me through your setup sequence? You use the wizard to configure PPPoE?

fichtner · 2017-05-25T10:37:37Z

(in the context of this older bug, we have found some caching files that were never cleared, so that might have something to do this this no default gateway behaviour previously reported for when this was referencing 16.7)

JackTrapper · 2017-05-26T00:03:51Z

So i plugged in the USB stick and booted it up again.

OPNSense 17.1.4

Welcome to OPNSense! Starting wizard.

Next

General information.

Next

Time Server Information.

Timezone: America/Toronto
Next

Configure WAN Interface

Selected Type: PPPoE
PPPoE Username: [redacted]
PPPoE Password: [redacted]
Next

Configure LAN Interface

Next

Set Admin Web GUI Password

Admin Password: [redacted]
Admin Password AGAIN: [redacted]
Next

Reload Configuration

Reload

Finished initial configuration!

Congratulations! OPNsense is now configured.
Click to continue to the dashboard.

You are currently running in LiveCD mode. A reboot will reset the configuration. SSH remote login is disabled.

How are the routes

So now it is setup. Lets check the routes

System -> Routes -> Status

Proto	Destination	Gateway	Flags	Use	MTU	Netif	Netif (name)
ipv4	Default	link#2	U	5083	1500	re0
ipv4	[ISP gateway IP redacted]	link#7	UH	0	1492	pppoe	wan

So it's using the wrong interface as the default route. Lets try pinging.

Interfaces -> Diagnostics -> Ping

Host: 8.8.8.8
IP Protocol: IPv4
Source Address: Default

Count: 3

PING 8.8.8.8 (8.8.8.8): 56 data bytes

 --- 8.8.8.8 ping statistics ---
 3 packets transmitted, 0 packets received, 100.0% packet loss
 ping: sendto: Host is down
 ping: sendto: Host is down
 ping: sendto: Host is down

Fails. Lets force use of the WAN (i.e. pppoe0) interface:

Host: 8.8.8.8
IP Protocol: IPv4
Source Address: WAN

Count: 3

PING 8.8.8.8 (8.8.8.8) from [redacted]: 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=51 time=24.503 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=51 time=24.306 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=51 time=28.037 ms

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 24.306/25.615/28.037/1.714 ms

So if i force the use of the interface, the packets will go. It just doesn't realize the default route.

Disconnect and reconnect PPPoE

Lets try forcing a disconnect and reconnect of the PPPoE interface

Interfaces -> Overview -> WAN Interface (wan, pppoe0)

Status: up
PPPOE: up
Disconnect
Status: down
PPPoE: down
Connect
Status: up
PPPoE: up

And check the routes again

Proto	Destination	Gateway	Flags	Use	MTU	Netif	Netif (name)
ipv4	Default	link#2	U	10400	1500	re0
ipv4	[ISP gateway IP redacted]	link#7	UH	0	1492	pppoe	wan

Still the wrong route. What about pinging again

Interface -> Diagnostics -> Ping

Host: 8.8.8.8
IP Protocol: IPv4
Source Address: Default

Count: 3

PING 8.8.8.8 (8.8.8.8): 56 data bytes

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down

Nope, still cannot ping using the default gateway.

Disable and re-enable the WAN interface

Lets disable the interface:

Interfaces -> [WAN]

Enable: [x] Enable Interface
Uncheck
Enable: [ ] Enable Interface
Save
Apply changes

And re-enable it:

Enable: [ ] Enable Interface
Check
Enable: [x] Enable Interface
Save
Apply changes

And check the routes again:

System -> Routes -> Status

Proto	Destination	Gateway	Flags	Use	MTU	Netif	Netif (name)
ipv4	Default	link#2	U	12152	1500	re0
ipv4	[ISP gateway IP redacted]	link#7	UH	0	1492	pppoe	wan

Still the wrong route. And ping still fails:

Interfaces -> Diagnostics -> Ping

Host: 8.8.8.8
IP Protocol: IPv4
Source Address: Default

Count: 3

PING 8.8.8.8 (8.8.8.8): 56 data bytes

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
ping: sendto: Host is down
ping: sendto: Host is down
ping: sendto: Host is down

And again if i force the use of PPPoE interface directly, it works:

Host: 8.8.8.8
IP Protocol: IPv4
Source Address: WAN

Count: 3

PING 8.8.8.8 (8.8.8.8) from [redacted]: 56 data bytes
64 bytes from 8.8.8.8: icmp_seq=0 ttl=51 time=24.503 ms
64 bytes from 8.8.8.8: icmp_seq=1 ttl=51 time=24.306 ms
64 bytes from 8.8.8.8: icmp_seq=2 ttl=51 time=28.037 ms

--- 8.8.8.8 ping statistics ---
3 packets transmitted, 3 packets received, 0.0% packet loss
round-trip min/avg/max/stddev = 24.306/25.615/28.037/1.714 ms

Now to go back downstairs, pull the USB stick, let pfSense boot up, and put my nicely formatted, long, verbose, findings into Github markdown. Should be posted in about an hour.

7:43pm EDT
Current time: 8:03pm EDT (quicker than i thought)

fichtner · 2017-07-11T13:38:24Z

Lots of progress here in the backgrounds, eventually cleaning up the IP renewal facilities for 17.7. 17.7-RC1 is out soon, please retest then.

JackTrapper · 2017-09-17T13:23:20Z

So i finally tried 17.7 and it still happens: Even though the PPPoE interface is up, the default interface is out the physical WAN port - with traffic going nowhere.

System -> Routes -> Status

Proto	Destination	Gateway	Flags	Use	MTU	Netif	Netif (name)	Expire
ipv4	default	link#2	U	81208	1500	re0
ipv4	216.8.136.169	link#7	UH	0	1492	pppoe0	wan

Even though my PPPoE interface is up

System -> Gateways -> Status

Name	Gateway	Monitor	RTT	Loss	Status	Description
WAN_PPPOE	216.8.136.169	none	0.0 ms	0.0 %	Online	Interface WAN_PPPOE Gateway

If you compare that to pfSense:

Destination	Gateway	Flags	Use	Mtu	Netif
default	216.8.136.169	UGS	48915	1492	pppoe0
192.168.1.0/24	link#1	U	9999049	1500	em0
216.8.136.169	link#7	UH	172033	1492	pppoe0

So i guess where at a point where we're stuck.

JackTrapper · 2017-10-15T17:51:14Z

So what's needed to help get this fixed?

By definition i'm starting a fresh install - Live USB stick.

Somebody on the planet must understand why the operating system refuses to use the correct default route. Is there a logfile that opnSense needs to log to?

andreasvel changed the title ~~WAN over PPPOE - default Route is not made~~ WAN over PPPOE - default Route is not set Mar 23, 2016

fichtner added this to the 16.7 milestone Jun 21, 2016

fichtner self-assigned this Jun 21, 2016

fichtner added the bug Production bug label Jun 21, 2016

fichtner mentioned this issue Jun 21, 2016

BUG PPPOE Disconnects after Time - Routing Problems #974

Closed

fichtner closed this as completed Jul 23, 2016

fichtner reopened this May 25, 2017

fichtner modified the milestones: 17.7, 16.7 May 25, 2017

fichtner closed this as completed Jul 21, 2017

JackTrapper mentioned this issue Feb 10, 2018

wizard: WAN over PPPOE - default Route is not set correctly #2186

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

WAN over PPPOE - default Route is not set #850

WAN over PPPOE - default Route is not set #850

andreasvel commented Mar 23, 2016

fichtner commented May 30, 2016 •

edited

Loading

fichtner commented Jun 21, 2016

andreasvel commented Jun 22, 2016

andreasvel commented Jul 7, 2016

fichtner commented Jul 16, 2016

fichtner commented Jul 23, 2016

fichtner commented Jul 23, 2016

andreasvel commented Sep 14, 2016

tadaog commented Jan 17, 2017

fichtner commented Jan 17, 2017

JackTrapper commented May 17, 2017 •

edited

Loading

fichtner commented May 17, 2017

JackTrapper commented May 17, 2017

JackTrapper commented May 18, 2017

fichtner commented May 25, 2017

fichtner commented May 25, 2017

JackTrapper commented May 26, 2017 •

edited

Loading

fichtner commented Jul 11, 2017

JackTrapper commented Sep 17, 2017 •

edited

Loading

JackTrapper commented Oct 15, 2017

WAN over PPPOE - default Route is not set #850

WAN over PPPOE - default Route is not set #850

Comments

andreasvel commented Mar 23, 2016

fichtner commented May 30, 2016 • edited Loading

fichtner commented Jun 21, 2016

andreasvel commented Jun 22, 2016

andreasvel commented Jul 7, 2016

fichtner commented Jul 16, 2016

fichtner commented Jul 23, 2016

fichtner commented Jul 23, 2016

andreasvel commented Sep 14, 2016

tadaog commented Jan 17, 2017

fichtner commented Jan 17, 2017

JackTrapper commented May 17, 2017 • edited Loading

fichtner commented May 17, 2017

JackTrapper commented May 17, 2017

JackTrapper commented May 18, 2017

fichtner commented May 25, 2017

fichtner commented May 25, 2017

JackTrapper commented May 26, 2017 • edited Loading

OPNSense 17.1.4

How are the routes

Disconnect and reconnect PPPoE

Disable and re-enable the WAN interface

fichtner commented Jul 11, 2017

JackTrapper commented Sep 17, 2017 • edited Loading

JackTrapper commented Oct 15, 2017

fichtner commented May 30, 2016 •

edited

Loading

JackTrapper commented May 17, 2017 •

edited

Loading

JackTrapper commented May 26, 2017 •

edited

Loading

JackTrapper commented Sep 17, 2017 •

edited

Loading