Feature lost in transaction? M0n0 MAC addreses are gone?
-
No, I don't think we missed anything. We sync'd everything that I could find.
Word is that there will be a new m0n0wall release soon. If so, then we'll most likely import the captive portal changes (again).
-
yes they have 1.23b
-
Isn't that the FreeBSD 6 beta? Not exactly what I am talking about.
-
well I didnt really paid attention on what it runs but I know it has impruvcements for captive portal anyway…
-
what is the file name for captive portal index.php? and what is the name for accounting.php (or whatever it used to be called in mono) I want to chek if it cheks for MAC? Because in original it will not let it work if there is no user MAC….
-
dit you eneable the mac check on the pfsense portal pages ?
if not than mac adress is ignored and ipadress is used -
Isnt that function is tryyingto use MAC as both username and pass to identify user?
I will try it too? Just in case -
jeroen234, I did the trial ran for what u sudgested, and as I said it didnt work, because this fature is designed for diferent purpuse… it works like major cable troviders do for theit clients... so that they dont have to use username and passwords... they just go online right away...
BUT, what I found is that this feature dosnt work as it desined too... It suppose to send Radius-Request when I open web brower but it doesnt... Debug off everything is attached, I used my username to login...
So, I dont know why, but big part of m0n0 functionality is gone? :(
Ready to process requests.
rad_recv: Access-Request packet from host 192.168.0.102:60873, id=214, length=79
Service-Type = Login-User
User-Name = "alexus"
User-Password = "xxxxxxxx"
NAS-Identifier = "pfSense.local"
NAS-Port = 0
NAS-Port-Type = Ethernet
rlm_sql (sql): Reserving sql socket id: 3
rlm_sql (sql): Released sql socket id: 3
Sending Access-Accept of id 214 to 192.168.0.102 port 60873
rad_recv: Accounting-Request packet from host 192.168.0.102:50951, id=195, length=97
Service-Type = Login-User
User-Name = "alexus"
NAS-Identifier = "pfSense.local"
NAS-Port = 0
NAS-Port-Type = Ethernet
Acct-Status-Type = Start
Acct-Authentic = RADIUS
Acct-Session-Id = "1285ff05b364519a"
Framed-IP-Address = 192.168.1.199
rlm_sql (sql): Reserving sql socket id: 2
rlm_sql (sql): Released sql socket id: 2
Sending Accounting-Response of id 195 to 192.168.0.102 port 50951 -
The code is there, I promise you. Why its not working is beyond me.
-
I think, i found the proble, did you use the Captive Portal from M0n0 SVN? (http://svn.m0n0.ch/wall/branches/freebsd5/captiveportal/) Because I'm looking at the file right now and I think it is different from the one that they have in actual relseae.
-
Their file in SVN has not even been released yet! We are not using that until they release it.
-
ok, … can i take a look on the file that you are using? did you keep the original names? and what is the location of files?
-
Look in cvsweb.
-
i serched all over the plce but missed the directory i need (murphy's law) can u just tell me the location?
-
http://pfsense.com/cgi-bin/cvsweb.cgi/pfSense/etc/inc/captiveportal.inc
http://pfsense.com/cgi-bin/cvsweb.cgi/pfSense/usr/local/captiveportal/ -
ok, I think the problem is in Dropdown menu that select either "defult" or "cisco" type … thats the only thing that I can think off....
-
Did not modify that…
-
:-(
-
jeroen234, I did the trial ran for what u sudgested, and as I said it didnt work, because this fature is designed for diferent purpuse… it works like major cable troviders do for theit clients... so that they dont have to use username and passwords... they just go online right away...
BUT, what I found is that this feature dosnt work as it desined too... It suppose to send Radius-Request when I open web brower but it doesnt... Debug off everything is attached, I used my username to login...
So, I dont know why, but big part of m0n0 functionality is gone? :(
Ready to process requests.
rad_recv: Access-Request packet from host 192.168.0.102:60873, id=214, length=79
Service-Type = Login-User
User-Name = "alexus"
User-Password = "xxxxxxxx"
NAS-Identifier = "pfSense.local"
NAS-Port = 0
NAS-Port-Type = Ethernet
rlm_sql (sql): Reserving sql socket id: 3
rlm_sql (sql): Released sql socket id: 3
Sending Access-Accept of id 214 to 192.168.0.102 port 60873
rad_recv: Accounting-Request packet from host 192.168.0.102:50951, id=195, length=97
Service-Type = Login-User
User-Name = "alexus"
NAS-Identifier = "pfSense.local"
NAS-Port = 0
NAS-Port-Type = Ethernet
Acct-Status-Type = Start
Acct-Authentic = RADIUS
Acct-Session-Id = "1285ff05b364519a"
Framed-IP-Address = 192.168.1.199
rlm_sql (sql): Reserving sql socket id: 2
rlm_sql (sql): Released sql socket id: 2
Sending Accounting-Response of id 195 to 192.168.0.102 port 50951on this debug list you are oke
the only thing i can think off is that you dit'n open on youre wan conection the ports 1812 and 1813
on witch you radius server has to send its radius pakets to pfsense -
isnt it reverse? NAS send request to the radius server? and then gets replay with Access_accept or Access-Reject… ? Actuall accounting packets are stored in radius itself or im My Sql, but nas does not send accounting info