VPN (PPTP) doesn't work with 1.9.2.7b
Hi,
First of all, many thanks to Oleg for his continuing work.
I'd like to report a problem with the new firmware on my WL500g. PPTP VPN stopped from working. I rolled back to 1.9.2.6 and it works again. I didn't clear nvram between flashing. The config is:
ISP WAN: private static 192.168.1.112
ISP Gateway: 192.168.1.1
Subnet mask: 255.255.255.0
PPTP:
Heartbeat: public 195.a.b.c.H
Assigned IP: public 195.a.b.c.I
Subnet mask: 255.255.255.255
Gateway: 195.a.b.c.G
LAN: 192.168.2.0/24.
Routing stopped working. The routing tables before and after the upgrade look absolutely the same:
Код:
Destination Gateway Genmask Flags Metric Ref Use Iface
195.a.b.G 192.168.1.112 255.255.255.255 UGH 0 0 0 eth1
195.a.b.G * 255.255.255.255 UH 0 0 0 ppp0
192.168.1.0 * 255.255.255.0 U 0 0 0 eth1
192.168.2.0 * 255.255.255.0 U 0 0 0 br0
127.0.0.0 * 255.0.0.0 U 0 0 0 lo
default 195.a.b.H 0.0.0.0 UG 0 0 0 ppp0
Downgrading the firmware fixes the problem.
Thanks for looking into this.
Cheers,
Andrew.
Unable to access USB drives without activating built in FTP server (stupidftp)
Hi,
I can't seem to get the USB drives to mount without activating the built in FTP server. Not with this firmware, or previous 1.9.2.7 CR6 firmware.
What I want to do is use VSFTP as an FTP replacement for the built in FTP server: http://www.sprayfly.com/wiki/VSFTP_Guides
The messages in the system log show:
USB device 3 (vend/prod 0x1058/0x400) is not claimed by any active driver.
To me, this sounds that there is no request by any existing process for a USB drive to function and therefore it is not loaded. Is this true?
What should I change to make sure USB drives can always be mounted without setting the built in FTP server to active?
Steps how to reproduce?
1. Log in to the router: http://192.168.1.1/index.asp
2. Click USB Application
3. Select FTP server
4. Select the "No" radio button for the "Enable FTP server" field
5. Finish, and does reboot
PS. I'm doing this on the WL500g Deluxe.
System Setup - Operation Mode - Access Point no longer functions
I upgraded from the initial firmware OOB to this firmware. I then want to use the router as an Access Point so I open System Setup - Operation Mode and select Access Point.
I do not have a Finish button to save and reboot the router and when I click Apply the screen flashed but nothing happens. Going to another screen where I can choose finish results in a no longer functioning router meaning that it does not come back up again on 192.168.1.1, the default ip adress.
Anyone else had this experience and if so what do I need to do to get Access Point mode functioning again. Can I change a setting using Telnet to test that?
Thanks in advance!
VPN with MPPE/MPPC working
After two nights of messing with it, I finally got my WL-500g (actually an MN-700) to connect reliably to a Windows 2000 VPN server, WITH mppe/mppc.
I pretty much followed this:
http://pptpclient.sourceforge.net/ho...figure_by_hand
and then this:
http://pptpclient.sourceforge.net/ro...tml#lan-to-lan
A few changes, of course, since pppd on the wl-500 is configured to have its config files in /tmp/ppp, not /etc/ppp
I had to wipe out the existing /tmp/ppp/ip-up and /tmp/ppp/ip-down links.
instead, my ip-up has only two lines:
Код:
route add -net 192.168.0.0 netmask 255.255.0.0 dev ppp0
ifconfig ppp0 mtu 1400
The other big change was to use the following pppd options in addition to those in the link above.
Код:
nomppe-128 (instead of require-mppe-128)
require-mppe-40
mppe-stateless
128 bit might work, but I saw in the troubleshooting guide (http://pptpclient.sourceforge.net/howto-diagnosis.phtml) that it sometimes causes problems, so I force it to 40-bit instead. The kicker was forcing a stateless encryption though. Without that I was getting protocol rejects while trying to transfer data of any fairly large size, or at least CCP resets.
I also used the following pppd options to make the connection restore itself in the event it fails:
Код:
lcp-echo-interval 10
lcp-echo-failure 3
maxfail 0
persist
Before launching pppd, I modify the iptables a bit:
Код:
iptables --table nat --append POSTROUTING --out-interface ppp0 --jump MASQUERADE
iptables -A FORWARD -p tcp --tcp-flags SYN,RST SYN -j TCPMSS --clamp-mss-to-pmtu
I didn't have to do any of the other iptables stuff recommended by the link because all the proper allow(s) are already in there.
finally, since there's no "pon" utility, I launch pppd with the following:
Код:
pppd call (my config file name)
I automated the file deletions and copies and such with /usr/local/sbin/post-firewall
Setup like this, any packets destined for 192.168.*.* get NAT'd through the VPN connection. Anything else gets NAT'd through the normal WAN port.
So, uh, yea, just like the link above, except everything is different. :D
I won't know how stable it really is until I use it for a while, but for now I can run remote desktop and outlook through it just fine.
