OPNsense Forum
Archive => 15.7 Legacy Series => Topic started by: lukepower on November 18, 2015, 06:17:23 pm
-
Hi there,
I was wondering if it is technically possible to connecto to two different PPPoE connections over one interface (network card). I actually was able to set this up, but strangerly Opnsense shows me both connections with the same IP, even if they have different ones if I test them with traceroute. In addition, the second connection seems to not being used, even if I modify the firewall rules accordingly.
-
perhaps you can make it with different VLANs on one Network Connection?!
-
I think this is not supposed to work, some PPPoE negotiation uses broadcast addresses, the winner in terms of response time gets it all... :)
You can use VLANs, but you have to make sure that PPPoE is put on top terminated VLANs (server and client), because PPPoE itself won't speak VLAN.
-
Okay, now I put both connections on two different VLANs. The first one is working as expected, but showing a wrong IP address in teh web interface. The second one shows no IP address, but is actually active. A ping over both is working correctly, as long as I don't send any client traffic over the second - that is failing. Not sure if it is VLAN-caused or something else, though. In the logs there is a "Matched bundle OPT4", which I am not sure if it's the cause of the problems. Here a part of the PPP logs:
Nov 19 08:00:07 ppp: [opt4_link0] LCP: no reply to 1 echo request(s)
Nov 19 07:59:29 ppp: [opt4] IFACE: Rename interface ng1 to pppoe3
Nov 19 07:59:29 ppp: [opt4] IFACE: Up event
Nov 19 07:59:25 ppp: [opt4] 100.65.105.248 -> 81.174.0.21
Nov 19 07:59:25 ppp: [opt4] IPCP: LayerUp
Nov 19 07:59:25 ppp: [opt4] IPCP: state change Ack-Sent --> Opened
Nov 19 07:59:25 ppp: [opt4] SECDNS 88.149.128.12
Nov 19 07:59:25 ppp: [opt4] PRIDNS 88.149.128.22
Nov 19 07:59:25 ppp: [opt4] IPADDR 100.65.105.248
Nov 19 07:59:25 ppp: [opt4] IPCP: rec'd Configure Ack #25 (Ack-Sent)
Nov 19 07:59:25 ppp: [opt4] IPADDR 81.174.0.21
Nov 19 07:59:25 ppp: [opt4] IPCP: SendConfigAck #2
Nov 19 07:59:25 ppp: [opt4] 81.174.0.21 is OK
Nov 19 07:59:25 ppp: [opt4] IPADDR 81.174.0.21
Nov 19 07:59:25 ppp: [opt4] IPCP: rec'd Configure Request #2 (Ack-Sent)
Nov 19 07:59:25 ppp: [opt4] SECDNS 88.149.128.12
Nov 19 07:59:25 ppp: [opt4] PRIDNS 88.149.128.22
Nov 19 07:59:25 ppp: [opt4] IPADDR 100.65.105.248
Nov 19 07:59:25 ppp: [opt4] IPCP: SendConfigReq #25
Nov 19 07:59:23 ppp: [opt4] SECDNS 88.149.128.12
Nov 19 07:59:23 ppp: [opt4] PRIDNS 88.149.128.22
Nov 19 07:59:23 ppp: [opt4] IPADDR 100.65.105.248
Nov 19 07:59:23 ppp: [opt4] IPCP: SendConfigReq #24
Nov 19 07:59:23 ppp: [opt4] SECDNS 88.149.128.12
Nov 19 07:59:23 ppp: [opt4] PRIDNS 88.149.128.22
Nov 19 07:59:23 ppp: [opt4] 100.65.105.248 is OK
Nov 19 07:59:23 ppp: [opt4] IPADDR 100.65.105.248
Nov 19 07:59:23 ppp: [opt4] IPCP: rec'd Configure Nak #23 (Ack-Sent)
Nov 19 07:59:23 ppp: [opt4] IPV6CP: LayerFinish
Nov 19 07:59:23 ppp: [opt4] IPV6CP: state change Req-Sent --> Stopped
Nov 19 07:59:23 ppp: [opt4] IPV6CP: protocol was rejected by peer
Nov 19 07:59:23 ppp: [opt4_link0] LCP: protocol IPV6CP was rejected
Nov 19 07:59:23 ppp: [opt4_link0] LCP: rec'd Protocol Reject #2 (Opened)
Nov 19 07:59:23 ppp: [opt4] SECDNS 0.0.0.0
Nov 19 07:59:23 ppp: [opt4] PRIDNS 0.0.0.0
Nov 19 07:59:23 ppp: [opt4] IPADDR 0.0.0.0
Nov 19 07:59:23 ppp: [opt4] IPCP: SendConfigReq #23
Nov 19 07:59:23 ppp: [opt4] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Nov 19 07:59:23 ppp: [opt4] IPCP: rec'd Configure Reject #22 (Ack-Sent)
Nov 19 07:59:23 ppp: [opt4] IPCP: state change Req-Sent --> Ack-Sent
Nov 19 07:59:23 ppp: [opt4] IPADDR 81.174.0.21
Nov 19 07:59:23 ppp: [opt4] IPCP: SendConfigAck #1
Nov 19 07:59:23 ppp: [opt4] 81.174.0.21 is OK
Nov 19 07:59:23 ppp: [opt4] IPADDR 81.174.0.21
Nov 19 07:59:23 ppp: [opt4] IPCP: rec'd Configure Request #1 (Req-Sent)
Nov 19 07:59:23 ppp: [opt4] IPV6CP: SendConfigReq #4
Nov 19 07:59:23 ppp: [opt4] IPV6CP: state change Starting --> Req-Sent
Nov 19 07:59:23 ppp: [opt4] IPV6CP: Up event
Nov 19 07:59:23 ppp: [opt4] SECDNS 0.0.0.0
Nov 19 07:59:23 ppp: [opt4] PRIDNS 0.0.0.0
Nov 19 07:59:23 ppp: [opt4] COMPPROTO VJCOMP, 16 comp. channels, no comp-cid
Nov 19 07:59:23 ppp: [opt4] IPADDR 0.0.0.0
Nov 19 07:59:23 ppp: [opt4] IPCP: SendConfigReq #22
Nov 19 07:59:23 ppp: [opt4] IPCP: state change Starting --> Req-Sent
Nov 19 07:59:23 ppp: [opt4] IPCP: Up event
Nov 19 07:59:23 ppp: [opt4] IPV6CP: LayerStart
Nov 19 07:59:23 ppp: [opt4] IPV6CP: state change Initial --> Starting
Nov 19 07:59:23 ppp: [opt4] IPV6CP: Open event
Nov 19 07:59:23 ppp: [opt4] IPCP: LayerStart
Nov 19 07:59:23 ppp: [opt4] IPCP: state change Initial --> Starting
Nov 19 07:59:23 ppp: [opt4] IPCP: Open event
Nov 19 07:59:23 ppp: [opt4] Bundle: Status update: up 1 link, total bandwidth 64000 bps
Nov 19 07:59:23 ppp: [opt4_link0] Link: Join bundle "opt4"
Nov 19 07:59:23 ppp: [opt4_link0] Link: Matched action 'bundle "opt4" ""'
Nov 19 07:59:23 ppp: [opt4_link0] LCP: authorization successful
Nov 19 07:59:23 ppp: [opt4_link0] PAP: rec'd ACK #1 len: 5
Nov 19 07:59:23 ppp: [opt4_link0] LCP: LayerUp
Nov 19 07:59:23 ppp: [opt4_link0] PAP: sending REQUEST #1 len: 26
Nov 19 07:59:23 ppp: [opt4_link0] PAP: using authname "W16582285579"
Nov 19 07:59:23 ppp: [opt4_link0] LCP: auth: peer wants PAP, I want nothing
Nov 19 07:59:23 ppp: [opt4_link0] LCP: state change Ack-Sent --> Opened
Nov 19 07:59:23 ppp: [opt4_link0] MAGICNUM de0684c0
Nov 19 07:59:23 ppp: [opt4_link0] MRU 1492
Nov 19 07:59:23 ppp: [opt4_link0] PROTOCOMP
Nov 19 07:59:23 ppp: [opt4_link0] LCP: rec'd Configure Ack #6 (Ack-Sent)
Nov 19 07:59:23 ppp: [opt4_link0] LCP: state change Req-Sent --> Ack-Sent
Nov 19 07:59:23 ppp: [opt4_link0] MAGICNUM 0d4865de
Nov 19 07:59:23 ppp: [opt4_link0] AUTHPROTO PAP
Nov 19 07:59:23 ppp: [opt4_link0] MRU 1492
Nov 19 07:59:23 ppp: [opt4_link0] LCP: SendConfigAck #1
Nov 19 07:59:23 ppp: [opt4_link0] MAGICNUM 0d4865de
Nov 19 07:59:23 ppp: [opt4_link0] AUTHPROTO PAP
Nov 19 07:59:23 ppp: [opt4_link0] MRU 1492
Nov 19 07:59:23 ppp: [opt4_link0] LCP: rec'd Configure Request #1 (Req-Sent)
Nov 19 07:59:23 ppp: [opt4_link0] MAGICNUM de0684c0
Nov 19 07:59:23 ppp: [opt4_link0] MRU 1492
Nov 19 07:59:23 ppp: [opt4_link0] PROTOCOMP
Nov 19 07:59:23 ppp: [opt4_link0] LCP: SendConfigReq #6
Nov 19 07:59:23 ppp: [opt4_link0] LCP: state change Starting --> Req-Sent
Nov 19 07:59:23 ppp: [opt4_link0] LCP: Up event
Nov 19 07:59:23 ppp: [opt4_link0] Link: UP event
-
Ok,
got it halfway running. There were still two PPPoE connections running on the real interface (instead of the two VLANs), so they were interfering with each other.
pppoe2 is running fine, pppoe3 is not getting assigned an IP address correctly, or maybe the route is not ok. Looking at the logs all seems fine, but a ping already shows some problems:
PING google.de (216.58.210.195) from 100.90.227.193: 56 data bytes
--- google.de ping statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
Looking at this, the IP should be fine, but somehow the data is not coming through correctly...
-
Okay, I guess I found the problem. Basically, both PPPoE connections have different IP addresses, but get assigned the same gwateway (as they are both from the same ISP. So my question should be, do I need to put a router between the second PPPoE connection and OPNsense? Or is there a way around this? Looking at the pfSense docs, it seems to be a limitation of the system there.
-
Sorry, got caught up in daytime work. It's sounds like a constraint that should be there, but maybe it has to do with the ppp daemon (mpd). Let me check and get back on this.