Firmware v1.9.2.7 CR7 now 7g [Oleg]

[daav]

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.

[WlanMan]

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?

It says there is no driver loaded that claims support for this device.
Namely, the usb mass storage driver is not loaded.
To save memory they get loaded when ftp (or samba) is enabled.

What should I change to make sure USB drives can always be mounted without setting the built in FTP server to active?

Load the required kernel modules manual in post-boot.
Should be usb-core usb-storage and a filesystem driver.
Start with disk and ftp on, look with lsmod what´s loaded, disable ftp, load the now missing modules with insmod and see with dmesg if all works fine .

Greets
Wlanman

[Saturn49]

PPPoE connections are now forced to be nomppe nomppc

I need mppe and mppc support for my project. Is that support built into this firmware version?

I saw it was added to the official Asus 1.9.4 firmware, but it seems telnet isn't in there, so I can't do anything with it either.

Edit: Nevermind - I see MPPE support was added a long time ago in Oleg's version.

[Saturn49]

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.

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.

[ankn99]

Hi Oleg,

are the source at your HP up to date, I tried to compile nbut getting problems (for example: nat.diff patch tells me already applied, and a few other, got problems with config to compile too, it complains about missing ncurses )

any Idea, what I'm doing wrong ??

sincerly

ankn99

[Oleg]

Hi Oleg,

are the source at your HP up to date, I tried to compile nbut getting problems (for example: nat.diff patch tells me already applied, and a few other, got problems with config to compile too, it complains about missing ncurses )

any Idea, what I'm doing wrong ??

sincerly

ankn99

The sources are up2date. Check your environment, etc.

[Oleg]

Updated to -7c. Check first post.