Wednesday, November 29, 2017

PPPoE Gateway Issue with ISP

Ok, so i'm having a bit of an issue with my ISP.

They are setting the remote/gateway address as a private address instead of a public address, which conflicts with my own network

My linux firewall has an IP address of 10.0.0.1

I have internet in my building, provided by ethernet.

When I connect, it shows the following in pppd

Nov 28 23:42:21 firewall pppd[19591]: local IP address 211.122.156.12 Nov 28 23:42:21 firewall pppd[19591]: remote IP address 10.0.0.1 

(I have changed my external ip address in this post for security)

Note the remote IP address is also 10.0.0.1

So, my ISP is using 10.0.0.1 as the PtP address as shown here:

ppp0 Link encap:Point-to-Point Protocol inet addr:211.122.156.12 P-t-P:10.0.0.1 Mask:255.255.255.255 UP POINTOPOINT RUNNING NOARP MULTICAST MTU:1480 Metric:1 RX packets:1669 errors:0 dropped:0 overruns:0 frame:0 TX packets:1479 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:3 RX bytes:681954 (665.9 KiB) TX bytes:148840 (145.3 KiB) 

now, when I connect, it sets the default route on the firewall to 10.0.0.1 which conflicts with the LAN ip.

eg:

root@firewall:~# ip route show 10.0.0.1 dev ppp0 proto kernel scope link src 211.122.156.12 10.0.0.0/24 dev eth0 proto static scope link root@firewall:~# ping 8.8.8.8 connect: Network is unreachable 

I currently get around this by using the following options in pppd:

nodefaultroute noreplacedefaultroute 

Then setting an interface route:

ip route add default dev ppp0 

so the routes look like this:

root@firewall:~# ip route show 10.0.0.0/24 dev eth0 proto static scope link default dev ppp0 proto static scope link root@firewall:~# ping 8.8.8.8 PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data. 64 bytes from 8.8.8.8: icmp_req=1 ttl=60 time=11.1 ms 

The issue is, I want to use different routing software, which doesn't do device routes and runs into the conflict.

How can I prove to my ISP that the issue is on their end? Am I missing something myself?



No comments:

Post a Comment