Project

General

Profile

Actions
Copy link

Bug #4562

closed

PPPoe Server

Added by ian Clifford about 10 years ago. Updated about 10 years ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
03/28/2015
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:

Description

setting PPPoe server config for LAN
using built in user database
when changing remote address range to 172.168.60.11 from 172.168.60.0 when applying change it reverts back to original.
and when setting up pppoe users without an ip the first user gets 172.168.60.0 (non routable)
if i then give the user an IP (172.168.60.14) they get the new address, if i then configure a second user with an address below the first user (172.168.60.13) the issued address is 172.168.60.15.
server address is 172.168.60.130
subnet mask is /25
DHCP range is 172.168.60.10 to 172.168.60.117
hope this is helpfull
IanC

Actions
Copy link
 #1

Updated by ian Clifford about 10 years ago

using latest version 64bit

Actions
Copy link
 #2

Updated by Chris Buechler about 10 years ago

  • Status changed from New to Rejected

.0 is a valid, usable IP in that circumstance. The code there will set the address range to the network address for the entered IP and mask if it's not already the network address. For the mentioned circumstance, that is .0. There is no such network as a .11/25, it corrects the invalid entry to the correct one. That's the correct behavior, not a bug.

On an unrelated note, 172.168. is not private IP space, assuming you're NATing clients you shouldn't be using that.

Actions
Copy link

Also available in: Atom PDF