It seems that if you reset the nvram on these e1200v2's with a mega build installed, it will break the nvram settings (MACs and WAN IPs, ect) and you will have to follow the steps above to reset it. Resetting or selecting to reset during upgrade always caused my boxes to not have a WAN IP and all kinds of bogus MAC issues.
Yes Sir, they can try your nerves. I was just playing around to see what I could and couldn't do. The k3-26866 does seem to run well on the e1200. When I get around to trying the k3-26947 again I'll take your advice.....thanks
Joined: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Thu May 21, 2015 21:51 Post subject:
Router: e900
Firmware: dd-wrt.v24-26947_NEWD-2_K3.x_mega-e900.bin
Kernel: Linux 3.10.79 #7989 Tue May 19 08:12:29 CEST 2015 mips
Status: Working great
Reset: During the downgrade to the required first mini build, yes.
Errors: None thus far, running smoothly as a client bridge.
____________________________________
Here's a formal report
Router: e1200v2
Firmware: dd-wrt.v24-26947_NEWD-2_K3.x_mega-e1200v2.bin
Kernel: Linux 3.10.79 #7989 Tue May 19 08:12:29 CEST 2015 mips
Status: Working great
Reset: During the downgrade to the required first mini build, yes.
Errors: None thus far, running smoothly as a client bridge. Streaming music and movies from the net and my NAS no problems. _________________ Deployed Routers:
Netgear R7800 - 1x build 46979
- Gateway (USB /w Entware, CAKE QoS)
Netgear R7000 - 3x build 46979
Router: Netgear R7000
Firmware: r26947
Status: Working, but issues with Radius !!!
Reset: yes
Errors: SEE BELOW:
Unable to use WPA2 Enterprise, due to freeradius issues.
result of running radiusd -X is:
Code:
rlm_eap: SSL error error:02001002:lib(2):func(1):reason(2)
rlm_eap_tls: Error reading certificate file /etc/freeradius/certs/server.pem
rlm_eap: Failed to initialize type tls
/etc/freeradius/eap.conf[17]: Instantiation failed for module "eap"
/etc/freeradius/sites-enabled/default[312]: Failed to find "eap" in the "modules" section.
/etc/freeradius/sites-enabled/default[254]: Errors parsing authenticate section.
I have formatted jffs and re-generated all certificates to rule out old certs being the problem. Router was fully reset and reconfigured from the GUI, with the same settings that worked fine with build 26653.
Still getting a bridge error:
<4>may 10 16:03:16 kernel: br0: received packet on vlan1 with own address as source address
The radius issues appear to be because radiusd is looking at "/etc/freeradius" for files, instead of looking at "/jffs/etc/freeradius" like it should be. This is a compile/configuration error with the new version of Freeradius?
Can anyone else who uses radius and client certs (not just a password) on their wireless also confirm this please?
Ticket UPDATED, to show that this issue is still present.
Can any of the devs please fix this? It sppears it is just an issue with the file paths in the new version of radius that was added. Brainslayer? Kong?
There seems to be an error with mstpd, but it does not seem to cause connectivity problems, here's the log data if anyone is interested:
Code:
mstpd: set_br_up: br0 was up
mstpd: set_br_up: set bridge br0 up
mstpd: set_if_up: port eth1 : up
mstpd: error, ethtool_get_speed_duplex: cannot get speed/duplex for eth1: not supported
mstpd: set_br_up: br0 was up
mstpd: set_br_up: set bridge br0 up
mstpd: set_if_up: port eth1 : up
mstpd: error, ethtool_get_speed_duplex: cannot get speed/duplex for eth1: not supported
mstpd: set_br_up: br0 was up
mstpd: set_br_up: set bridge br0 up
mstpd: set_if_up: port eth1 : up
mstpd: error, ethtool_get_speed_duplex: cannot get speed/duplex for eth1: not supported
mstpd: set_br_up: br0 was up
mstpd: set_br_up: set bridge br0 up
mstpd: set_if_up: port eth1 : up
mstpd: error, ethtool_get_speed_duplex: cannot get speed/duplex for eth1: not supported
mstpd: set_br_up: br0 was up
mstpd: set_br_up: set bridge br0 up
mstpd: set_if_up: port eth2 : up
mstpd: error, ethtool_get_speed_duplex: cannot get speed/duplex for eth2: not supported
mstpd: set_br_up: br0 was up
mstpd: set_br_up: set bridge br0 up
mstpd: set_if_up: port eth2 : up
mstpd: error, ethtool_get_speed_duplex: cannot get speed/duplex for eth2: not supported
mstpd: set_br_up: br0 was up
mstpd: set_br_up: set bridge br0 up
mstpd: set_if_up: port eth2 : up
mstpd: error, ethtool_get_speed_duplex: cannot get speed/duplex for eth2: not supported
mstpd: set_br_up: br0 was up
mstpd: set_br_up: set bridge br0 up
mstpd: set_if_up: port eth2 : up
mstpd: error, ethtool_get_speed_duplex: cannot get speed/duplex for eth2: not supported
@SirSilentBob
BrainSlayer closed the FreeRadius ticket http://svn.dd-wrt.com/ticket/4099#comment:4 with specification:
radiusd -X is the wrong way to start freeradius and will result in the error you showed
you must start it with -d /jffs/etc/freeradius
otherwise the wrong paths are used. so no bug, just wrong use
_________________ THERE ARE NO STRANGERS HERE; ONLY FRIENDS YOU HAVEN'T YET MET.
________________________________________________________________________________________________________
DD-WRT CHANGELOG | DEVICES | DD-WRT BUILDS | KONG BUILDS | UNOFFICIAL BUILDS | DD-WRT in VIRTUALBOX
Router: asus rt-n18u
Firmware: asus_rt-n18u-firmware.trx
Status: Wireless connection not working: very weak signal (RSSI -92 at 50cm.), clients can't connect.
Reset: Yes, 30/30/30 before and after flashing the firmware
Errors: None
Posted: Fri May 22, 2015 8:35 Post subject: Bandwidth monitoring
I have the r7000 and have noticed for the past few builds my wireless interfaces show up weird in the bandwidth monitoring page. They used to show up as wl0 and wl1. Now they are showing up as some number in the billion range. I dont think the r7000 has this many radios
Yes I have a r7000 too, And the wireless transmission to clients drops significantly all the time. It's not consistent to maintain a decent mbps. I had to revert back to stock firmware and the wireless signal has never been better since. I still want to go back to dd-wrt but I need the signal problems to be fix. TRUST ME when I say I've ALMOST tried everything from full wipes/telnet/regulatory domain/qos/security off/40mhz & 80mhz switch/channel change/tcp change.. I think the drops in the signal are coming from dhcp. Since netgear fix it in their last firmware update due to wireless speed drops. Also I believe it may have to do with packet lost and tcp control as well.
Yes I have a r7000 too, And the wireless transmission to clients drops significantly all the time. It's not consistent to maintain a decent mbps. I had to revert back to stock firmware and the wireless signal has never been better since. I still want to go back to dd-wrt but I need the signal problems to be fix. TRUST ME when I say I've ALMOST tried everything from full wipes/telnet/regulatory domain/qos/security off/40mhz & 80mhz switch/channel change/tcp change.. I think the drops in the signal are coming from dhcp. Since netgear fix it in their last firmware update due to wireless speed drops. Also I believe it may have to do with packet lost and tcp control as well.
Let me guess, yo are using an intel wireless client adapter with older drivers?
Yes I have a r7000 too, And the wireless transmission to clients drops significantly all the time. It's not consistent to maintain a decent mbps. I had to revert back to stock firmware and the wireless signal has never been better since. I still want to go back to dd-wrt but I need the signal problems to be fix. TRUST ME when I say I've ALMOST tried everything from full wipes/telnet/regulatory domain/qos/security off/40mhz & 80mhz switch/channel change/tcp change.. I think the drops in the signal are coming from dhcp. Since netgear fix it in their last firmware update due to wireless speed drops. Also I believe it may have to do with packet lost and tcp control as well.
Let me guess, yo are using an intel wireless client adapter with older drivers?
No sir. My laptop has a Qualcomm Atheros. And I also use a PS4 which I believe has a Marvell Avastar 88W8797. I also have one AC phone which is a HTC M9 connected and two other wifi N phones connected as well. And one ipad and iphone 6. So do you think it's one of wifi chipsets in the phones breaking the wifi transmissions? (By the way I was using this latest build)
WNDR3700v3
DD-WRT v24-sp2 (05/19/15) mega - build 26947M as was install couple days ago.
Linux 3.10.79 #7989 Tue May 19 08:12:29 CEST 2015 mips
[dd-wrt.v24-26947_NEWD-2_K3.x_mega-nv64k.bin]
GUI reset
Erase NVRAM
default settings, add wl0.1 VAP, cannot connect -- same as previous posted.
Add 5GHz wl1.1 VAP with same results as other..... cannot connect to VAP.
Erase kernel
TFTP netgear [WNDR3700v3-V1.0.0.38_1.0.31.chk]
Netgear MAC addresses:
2C:B0:5D:42:BB:8A - WAN
2C:B0:5D:42:BB:89 - LAN
2C:B0:5D:42:BB:89 - 2.4GHz b/g/n (activate guest for 2.4 no MAC showing in GUI)
2C:B0:5D:42:BB:88 - 5GHz a/n (activate guest for 5GHz no MAC showing in GUI)
Install
DD-WRT v24-sp2 (05/19/15) mini - build 26947
Linux 2.6.24.111 #25448 Tue May 19 00:20:35 CEST 2015 mips
[dd-wrt.v24-26947_NEWD-2_K2.6_mini-WNDR3700v3.chk]
dd-wrt MAC addresses:
2C:B0:5D:42:BB:8A - WAN
2C:B0:5D:42:BB:88 - LAN
2C:B0:5D:42:BB:8B - Wireless
2C:B0:5D:42:BB:8B - 2.4 wl0
2E:B0:5D:42:BB:8C - 2.4 wl0.1
2C:B0:5D:42:BB:88 - 5GHz wl1
2E:B0:5D:42:BB:89 - 5GHz wl1.1
Connection to VAPs GOOD.
Install
[dd-wrt.v24-26947_NEWD-2_K3.x_mega-nv64k.bin]
Cannot connect to VAP with WPA2-AES .. also just enabling security on the wl0.1 VAP will break the wl1.1 and it didn't have any security.
Have NOT seen any 'kern.warn kernel: br0: received packet on eth2 with own address as source address' since wiped the kernel.
Flashed two E3000 with dd-wrt.v24-26947_NEWD-2_K2.6_big-nv60k.bin and one E4200 with dd-wrt.v24-26947_NEWD-2_K3.x_mega-e4200.bin (no reset). Seem to work ok. I did not test radvd on the E3000. _________________ 2 times APU2 Opnsense 21.1 with Sensei
2 times RT-AC56U running DD-WRT 45493 (one as Gateway, the other as AP, both bridged with LAN cable)
3 times Asus RT-N16 shelved
E4200 V1 running freshtomato 2020.8 (bridged with LAN cable)
3 times Linksys WRT610N V2 converted to E3000 and 1 original E3000 running freshtomato 2020.8 (bridged with LAN cable)
@SirSilentBob
BrainSlayer closed the FreeRadius ticket http://svn.dd-wrt.com/ticket/4099#comment:4 with specification:
radiusd -X is the wrong way to start freeradius and will result in the error you showed
you must start it with -d /jffs/etc/freeradius
otherwise the wrong paths are used. so no bug, just wrong use
Thanks for the info, Kryptex! Unfortunately, there is still a problem. Here's the raw output, with the proper directory, and also the actual attempted authentication attempt. I'll add this information to the ticket. This occurs when simply using mschap (username/password), and also if I actually download the certificate and put it on the device and properly set it up.
Nothing has changed on any of the clients (Computers, a phone and tablet) and this issue happened after the radius upgrade in 26776.
Here's an image of the radius setup in the webif.
And sorry for the looooooong code clip of info......
Code:
radiusd: FreeRADIUS Version 2.2.7, for host arm-uclibc-linux, built on Apr 30 2015 at 00:58:18
Copyright (C) 1999-2015 The FreeRADIUS server project and contributors.
There is NO warranty; not even for MERCHANTABILITY or FITNESS FOR A
PARTICULAR PURPOSE.
You may redistribute copies of FreeRADIUS under the terms of the
GNU General Public License.
For more information about these matters, see the file named COPYRIGHT.
Starting - reading configuration files ...
including configuration file /jffs/etc/freeradius/radiusd.conf
including configuration file /jffs/etc/freeradius/clients.conf
including configuration file /jffs/etc/freeradius/clients.manual
including files in directory /jffs/etc/freeradius/modules/
including configuration file /jffs/etc/freeradius/modules/soh
including configuration file /jffs/etc/freeradius/modules/cui
including configuration file /jffs/etc/freeradius/modules/pam
including configuration file /jffs/etc/freeradius/modules/pap
including configuration file /jffs/etc/freeradius/modules/otp
including configuration file /jffs/etc/freeradius/modules/expr
including configuration file /jffs/etc/freeradius/modules/attr_filter
including configuration file /jffs/etc/freeradius/modules/passwd
including configuration file /jffs/etc/freeradius/modules/expiration
including configuration file /jffs/etc/freeradius/modules/preprocess
including configuration file /jffs/etc/freeradius/modules/radutmp
including configuration file /jffs/etc/freeradius/modules/sqlcounter_expire_on_login
including configuration file /jffs/etc/freeradius/modules/logintime
including configuration file /jffs/etc/freeradius/modules/dynamic_clients
including configuration file /jffs/etc/freeradius/modules/unix
including configuration file /jffs/etc/freeradius/modules/checkval
including configuration file /jffs/etc/freeradius/modules/rediswho
including configuration file /jffs/etc/freeradius/modules/attr_rewrite
including configuration file /jffs/etc/freeradius/modules/dhcp_sqlippool
including configuration file /jffs/etc/freeradius/sql/mysql/ippool-dhcp.conf
including configuration file /jffs/etc/freeradius/modules/etc_group
including configuration file /jffs/etc/freeradius/modules/sql_log
including configuration file /jffs/etc/freeradius/modules/replicate
including configuration file /jffs/etc/freeradius/modules/wimax
including configuration file /jffs/etc/freeradius/modules/detail
including configuration file /jffs/etc/freeradius/modules/always
including configuration file /jffs/etc/freeradius/modules/radrelay
including configuration file /jffs/etc/freeradius/modules/opendirectory
including configuration file /jffs/etc/freeradius/modules/exec
including configuration file /jffs/etc/freeradius/modules/inner-eap
including configuration file /jffs/etc/freeradius/modules/acct_unique
including configuration file /jffs/etc/freeradius/modules/digest
including configuration file /jffs/etc/freeradius/modules/files
including configuration file /jffs/etc/freeradius/modules/linelog
including configuration file /jffs/etc/freeradius/modules/detail.log
including configuration file /jffs/etc/freeradius/modules/cache
including configuration file /jffs/etc/freeradius/modules/mschap
including configuration file /jffs/etc/freeradius/modules/redis
including configuration file /jffs/etc/freeradius/modules/policy
including configuration file /jffs/etc/freeradius/modules/sradutmp
including configuration file /jffs/etc/freeradius/modules/ntlm_auth
including configuration file /jffs/etc/freeradius/modules/smbpasswd
including configuration file /jffs/etc/freeradius/modules/mac2ip
including configuration file /jffs/etc/freeradius/modules/realm
including configuration file /jffs/etc/freeradius/modules/perl
including configuration file /jffs/etc/freeradius/modules/mac2vlan
including configuration file /jffs/etc/freeradius/modules/detail.example.com
including configuration file /jffs/etc/freeradius/modules/krb5
including configuration file /jffs/etc/freeradius/modules/counter
including configuration file /jffs/etc/freeradius/modules/echo
including configuration file /jffs/etc/freeradius/modules/ippool
including configuration file /jffs/etc/freeradius/modules/smsotp
including configuration file /jffs/etc/freeradius/modules/ldap
including configuration file /jffs/etc/freeradius/modules/chap
including configuration file /jffs/etc/freeradius/eap.conf
including files in directory /jffs/etc/freeradius/sites-enabled/
including configuration file /jffs/etc/freeradius/sites-enabled/default
including configuration file /jffs/etc/freeradius/sites-enabled/control-socket
including configuration file /jffs/etc/freeradius/sites-enabled/inner-tunnel
including dictionary file /jffs/etc/freeradius/dictionary
main {
name = "radiusd"
prefix = "/usr"
localstatedir = "/var"
sbindir = "/usr/sbin"
logdir = "/var/log"
run_dir = "/var/run"
libdir = "/usr/lib"
radacctdir = "/var/db/radacct"
hostname_lookups = no
max_request_time = 30
cleanup_delay = 5
max_requests = 1024
pidfile = "/var/run/radiusd.pid"
checkrad = "/usr/sbin/checkrad"
debug_level = 0
proxy_requests = no
log {
stripped_names = yes
auth = yes
auth_badpass = yes
auth_goodpass = no
}
security {
max_attributes = 200
reject_delay = 1
status_server = yes
allow_vulnerable_openssl = no
}
}
radiusd: #### Loading Realms and Home Servers ####
radiusd: #### Loading Clients ####
client 192.168.50.1 {
require_message_authenticator = no
secret = "blahblah"
shortname = "DD-WRT-RADIUS"
}
radiusd: #### Instantiating modules ####
instantiate {
Module: Linked to module rlm_expiration
Module: Instantiating module "expiration" from file /jffs/etc/freeradius/modules/expiration
expiration {
reply-message = "Password Has Expired "
}
}
radiusd: #### Loading Virtual Servers ####
server { # from file /jffs/etc/freeradius/radiusd.conf
modules {
Module: Checking authenticate {...} for more modules to load
Module: Linked to module rlm_pap
Module: Instantiating module "pap" from file /jffs/etc/freeradius/modules/pap
pap {
encryption_scheme = "auto"
auto_header = yes
}
Module: Linked to module rlm_chap
Module: Instantiating module "chap" from file /jffs/etc/freeradius/modules/chap
Module: Linked to module rlm_mschap
Module: Instantiating module "mschap" from file /jffs/etc/freeradius/modules/mschap
mschap {
use_mppe = yes
require_encryption = yes
require_strong = yes
with_ntdomain_hack = no
allow_retry = yes
}
Module: Linked to module rlm_eap
Module: Instantiating module "eap" from file /jffs/etc/freeradius/eap.conf
eap {
default_eap_type = "peap"
timer_expire = 60
ignore_unknown_eap_types = no
cisco_accounting_username_bug = no
max_sessions = 1024
}
Module: Linked to sub-module rlm_eap_tls
Module: Instantiating eap-tls
tls {
rsa_key_exchange = no
dh_key_exchange = yes
rsa_key_length = 512
dh_key_length = 512
verify_depth = 0
CA_path = "/jffs/etc/freeradius/certs"
pem_file_type = yes
private_key_file = "/jffs/etc/freeradius/certs/server.pem"
certificate_file = "/jffs/etc/freeradius/certs/server.pem"
CA_file = "/jffs/etc/freeradius/certs/ca.pem"
private_key_password = "blahblah"
dh_file = "/jffs/etc/freeradius/certs/dh"
fragment_size = 1024
include_length = yes
check_crl = no
cipher_list = "DEFAULT"
verify {
}
ocsp {
enable = no
override_cert_url = yes
url = "http://127.0.0.1/ocsp/"
use_nonce = yes
timeout = 0
softfail = no
}
}
Module: Linked to sub-module rlm_eap_peap
Module: Instantiating eap-peap
peap {
default_eap_type = "mschapv2"
copy_request_to_tunnel = yes
use_tunneled_reply = yes
proxy_tunneled_request_as_eap = no
soh = no
}
Module: Linked to sub-module rlm_eap_mschapv2
Module: Instantiating eap-mschapv2
mschapv2 {
with_ntdomain_hack = no
send_error = no
}
Module: Checking authorize {...} for more modules to load
Module: Linked to module rlm_always
Module: Instantiating module "reject" from file /jffs/etc/freeradius/modules/always
always reject {
rcode = "reject"
simulcount = 0
mpp = no
}
Module: Linked to module rlm_files
Module: Instantiating module "files" from file /jffs/etc/freeradius/modules/files
files {
usersfile = "/jffs/etc/freeradius/users"
acctusersfile = "/jffs/etc/freeradius/acct_users"
preproxy_usersfile = "/jffs/etc/freeradius/preproxy_users"
compat = "no"
}
reading pairlist file /jffs/etc/freeradius/users
reading pairlist file /jffs/etc/freeradius/users.manual
reading pairlist file /jffs/etc/freeradius/acct_users
reading pairlist file /jffs/etc/freeradius/preproxy_users
Module: Checking accounting {...} for more modules to load
Module: Linked to module rlm_exec
Module: Instantiating module "exec" from file /jffs/etc/freeradius/modules/exec
exec {
wait = no
input_pairs = "request"
shell_escape = yes
timeout = 10
}
Module: Checking session {...} for more modules to load
Module: Linked to module rlm_radutmp
Module: Instantiating module "radutmp" from file /jffs/etc/freeradius/modules/radutmp
radutmp {
filename = "/var/db/radacct/radutmp"
username = "%{User-Name}"
case_sensitive = yes
check_with_nas = yes
perm = 384
callerid = yes
}
} # modules
} # server
server inner-tunnel { # from file /jffs/etc/freeradius/sites-enabled/inner-tunnel
modules {
Module: Checking authenticate {...} for more modules to load
Module: Linked to module rlm_unix
Module: Instantiating module "unix" from file /jffs/etc/freeradius/modules/unix
unix {
radwtmp = "/var/log/radwtmp"
}
Module: Checking authorize {...} for more modules to load
Module: Linked to module rlm_realm
Module: Instantiating module "suffix" from file /jffs/etc/freeradius/modules/realm
realm suffix {
format = "suffix"
delimiter = "@"
ignore_default = no
ignore_null = no
}
Module: Linked to module rlm_logintime
Module: Instantiating module "logintime" from file /jffs/etc/freeradius/modules/logintime
logintime {
reply-message = "You are calling outside your allowed timespan "
minimum-timeout = 60
}
Module: Checking session {...} for more modules to load
Module: Checking post-proxy {...} for more modules to load
Module: Checking post-auth {...} for more modules to load
Module: Linked to module rlm_attr_filter
Module: Instantiating module "attr_filter.access_reject" from file /jffs/etc/freeradius/modules/attr_filter
attr_filter attr_filter.access_reject {
attrsfile = "/jffs/etc/freeradius/attrs.access_reject"
key = "%{User-Name}"
relaxed = no
}
reading pairlist file /jffs/etc/freeradius/attrs.access_reject
} # modules
} # server
radiusd: #### Opening IP addresses and Ports ####
listen {
type = "auth"
ipaddr = *
port = 1812
}
listen {
type = "control"
listen {
socket = "/var/run/radiusd.sock"
}
}
listen {
type = "auth"
ipaddr = 127.0.0.1
port = 18120
}
Listening on authentication address * port 1812
Listening on command file /var/run/radiusd.sock
Listening on authentication address 127.0.0.1 port 18120 as server inner-tunnel
Ready to process requests.
rad_recv: Access-Request packet from host 192.168.50.1 port 60833, id=0, length=119
User-Name = "jay"
NAS-IP-Address = 192.168.50.1
Called-Station-Id = "e4f4c610507f"
Calling-Station-Id = "784b87e7db65"
NAS-Identifier = "e4f4c610507f"
NAS-Port = 25
Framed-MTU = 1400
NAS-Port-Type = Wireless-802.11
EAP-Message = 0x02000008016a6179
Message-Authenticator = 0xfdaa220729669d1ff20769db899d8c5d
# Executing section authorize from file /jffs/etc/freeradius/sites-enabled/default
+group authorize {
++[mschap] = noop
[eap] EAP packet type response id 0 length 8
[eap] No EAP Start, assuming it's an on-going EAP conversation
++[eap] = updated
++[reject] = reject
+} # group authorize = reject
Invalid user: [jay/<via Auth-Type = EAP>] (from client DD-WRT-RADIUS port 25 cli 784b87e7db65)
Using Post-Auth-Type Reject
WARNING: Unknown value specified for Post-Auth-Type. Cannot perform requested action.
Delaying reject of request 0 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
Sending delayed reject for request 0
Sending Access-Reject of id 0 to 192.168.50.1 port 60833
Waking up in 4.9 seconds.
Cleaning up request 0 ID 0 with timestamp +9
Ready to process requests.
rad_recv: Access-Request packet from host 192.168.50.1 port 60833, id=0, length=119
User-Name = "jay"
NAS-IP-Address = 192.168.50.1
Called-Station-Id = "e4f4c610507f"
Calling-Station-Id = "784b87e7db65"
NAS-Identifier = "e4f4c610507f"
NAS-Port = 25
Framed-MTU = 1400
NAS-Port-Type = Wireless-802.11
EAP-Message = 0x02000008016a6179
Message-Authenticator = 0xe4501672599b175eb5a4dd896e7c02bb
# Executing section authorize from file /jffs/etc/freeradius/sites-enabled/default
+group authorize {
++[mschap] = noop
[eap] EAP packet type response id 0 length 8
[eap] No EAP Start, assuming it's an on-going EAP conversation
++[eap] = updated
++[reject] = reject
+} # group authorize = reject
Invalid user: [jay/<via Auth-Type = EAP>] (from client DD-WRT-RADIUS port 25 cli 784b87e7db65)
Using Post-Auth-Type Reject
WARNING: Unknown value specified for Post-Auth-Type. Cannot perform requested action.
Delaying reject of request 2 for 1 seconds
Going to the next request
Waking up in 0.9 seconds.
Sending delayed reject for request 2
Sending Access-Reject of id 0 to 192.168.50.1 port 60833
Waking up in 4.9 seconds.
Cleaning up request 2 ID 0 with timestamp +218
Ready to process requests.
I've updated the ticket reference the free radius issue. I rolled back to r26653, since it was the last version that freeradius worked in for me. I compared the config outputs, and found multiple differences in configuration options between the working and non-working versions. (Just updating everyone on this issue.) Thanks Brainslayer and KrypteX for your patience with me on this. I do hope that my comparison of the differences will be helpful to fix the problem. _________________ Netgear R7000 w/r31780M <KONG> build
Netgear R6700 (Un-opened with stock. My backup/emergency router if the R7000 takes a dump...)
2x Buffalo WHR-HP-GN 28493 (Used for 2.4 Ghz bridge when needed.)
Asus WL-500g Premium (1x v1 & 1x v2) (Still have, but retired for now.)
1x Linksys WRT54G v8 >>DD-WRT v24SP1 (The other routers needed something to point at and make fun of.)
Joined: 09 Nov 2014 Posts: 314 Location: Bakersfield, CA
Posted: Sat May 23, 2015 22:27 Post subject:
This build is seeming to have far less, almost none, WiFi speed drops as compared to the previous build. It stays connected much better as a client bridge to my access point(s) in a super crowded apartment area. _________________ Deployed Routers:
Netgear R7800 - 1x build 46979
- Gateway (USB /w Entware, CAKE QoS)
Netgear R7000 - 3x build 46979
