OpenWrt Forum Archive

Topic: Support for Marvell 88F5xx81 based routers

The content of this topic has been archived between 18 Jan 2014 and 6 May 2018. Unfortunately there are posts – most likely complete pages – missing.

slxar,

once you've installed a new openwrt image, here is what you have to do:
login to your router via telnet, then issue the following commands:
opkg update
opkg remove hostapd-mini
opkg install crda iw
opkg install iptables-mod-extra iptables-mod-nat-extra iptables-mod-conntrack-extra iptables-utils
opkg install kmod-sched kmod-ipt-filter kmod-textsearch kmod-ipt-ipopt kmod-ipt-imq iptables-mod-ipopt iptables-mod-imq
opkg install ntpclient qos-scripts tc iptables-mod-filter miniupnpd

After that, edit /etc/opkg.conf and comment the line
src/gz Maddes ftp://ftp.maddes.net/openwrt/kamikaze/o … -0.9.30.1/
and uncomment this one
src/gz snapshots http://downloads.openwrt.org/snapshots/ … n/packages
save the file and then issue these commands
opkg update
opkg install hostapd
opkg install luci-admin-full luci-theme-openwrtlight luci-app-firewall luci-app-ntpc luci-app-qos luci-app-upnp

You should now have a working web interface on your router.

For the port forwarding, please check openwrt docs;

thank you and i get the web interface work
and i followed the openwrt docs and set up few rules but it seem not work, as following

file:firewall.user

iptables -F input_rule
iptables -F output_rule
iptables -F forwarding_rule
iptables -t nat -F prerouting_rule
iptables -t nat -F postrouting_rule
iptables -F input_wan
iptables -F forwarding_wan
iptables -t nat -F prerouting_wan
iptables -A INPUT -i lo -j ACCEPT
iptables -A INPUT -i wan -j ACCEPT
iptables -A INPUT -i lan1 -j ACCEPT
iptables -A INPUT -i lan2 -j ACCEPT
iptables -A OUTPUT -i lo -j ACCEPT
iptables -A OUTPUT -i wan -j ACCEPT
iptables -A OUTPUT -i lan1 -j ACCEPT
iptables -A OUTPUT -i lan2 -j ACCEPT
#iptables -t nat -A prerouting_wan -p tcp --dport 22 -d 192.168.2.5 -j ACCEPT
#iptables        -A input_wan      -p tcp --dport 22 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -p tcp --dport 80 -d 192.168.2.5 -j ACCEPT
iptables        -A input_wan      -p tcp --dport 80 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -p tcp --dport 25 -d 192.168.2.5 -j ACCEPT
iptables        -A input_wan      -p tcp --dport 25 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -p tcp --dport 110 -d 192.168.2.5 -j ACCEPT
iptables        -A input_wan      -p tcp --dport 110 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -p tcp --dport 143 -d 192.168.2.5 -j ACCEPT
iptables        -A input_wan      -p tcp --dport 143 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -p tcp --dport 20 -d 192.168.2.5 -j ACCEPT
iptables        -A input_wan      -p tcp --dport 20 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -p tcp --dport 21 -d 192.168.2.5 -j ACCEPT
iptables        -A input_wan      -p tcp --dport 21 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -j DNAT --to 192.168.2.5
iptables        -A forwarding_wan -d 192.168.2.5 -j ACCEPT

192.168.2.5 is my server which want to have forwarding
192.168.2.2 is the computer I am using

now i can just use DMZ to make it work
how can i get it work by not using the DMZ and access to the server via the external IP?

(Last edited by slxar on 10 Dec 2009, 14:22)

slxar wrote:

thank you and i get the web interface work
and i followed the openwrt docs and set up few rules but it seem not work, as following

file:firewall.user

iptables -F input_rule
iptables -F output_rule
iptables -F forwarding_rule
iptables -t nat -F prerouting_rule
iptables -t nat -F postrouting_rule
iptables -F input_wan
iptables -F forwarding_wan
iptables -t nat -F prerouting_wan
iptables -A INPUT -i lo -j ACCEPT
iptables -A INPUT -i wan -j ACCEPT
iptables -A INPUT -i lan1 -j ACCEPT
iptables -A INPUT -i lan2 -j ACCEPT
iptables -A OUTPUT -i lo -j ACCEPT
iptables -A OUTPUT -i wan -j ACCEPT
iptables -A OUTPUT -i lan1 -j ACCEPT
iptables -A OUTPUT -i lan2 -j ACCEPT
#iptables -t nat -A prerouting_wan -p tcp --dport 22 -d 192.168.2.5 -j ACCEPT
#iptables        -A input_wan      -p tcp --dport 22 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -p tcp --dport 80 -d 192.168.2.5 -j ACCEPT
iptables        -A input_wan      -p tcp --dport 80 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -p tcp --dport 25 -d 192.168.2.5 -j ACCEPT
iptables        -A input_wan      -p tcp --dport 25 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -p tcp --dport 110 -d 192.168.2.5 -j ACCEPT
iptables        -A input_wan      -p tcp --dport 110 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -p tcp --dport 143 -d 192.168.2.5 -j ACCEPT
iptables        -A input_wan      -p tcp --dport 143 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -p tcp --dport 20 -d 192.168.2.5 -j ACCEPT
iptables        -A input_wan      -p tcp --dport 20 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -p tcp --dport 21 -d 192.168.2.5 -j ACCEPT
iptables        -A input_wan      -p tcp --dport 21 -d 192.168.2.5 -j ACCEPT
iptables -t nat -A prerouting_wan -j DNAT --to 192.168.2.5
iptables        -A forwarding_wan -d 192.168.2.5 -j ACCEPT

192.168.2.5 is my server which want to have forwarding
192.168.2.2 is the computer I am using

now i can just use DMZ to make it work
how can i get it work by not using the DMZ and access to the server via the external IP?

Can you try to install luci-app-firewall and manage it from there?
I mean, if you are having issues with the cli you can just add the firewall app in luci and do it from there.


@ opperon, which smartphone do you have, if I may ask? Is it WM 6.1 OS on it?

Does anyone know what endianess and ABI the Orion 1 platform is configured to use?  I have some pre compiled binaries that I am unfortunate not to have the source code. 

I have loaded the 17264 build onto my WRT350n v2, so far so good.  I plan to do some more testing tonight.

Thanks?

@bourne: my smartphone is a HTC Hero with Android.
I have not yet updated my post regarding wifi settings and performances issues however after some days of observing what's happening I now strongly suspect the [HT40-][SHORT-GI-40][DSSS_CCK-40] settings to be THE cause of my stability issues (my 2 laptops get disconnected and reconnected several times in a row from time to time).

I would tend to say now that 17264 and 18148 should be equal with regards to wifi stability as long as you do not enable the fancy 802.11n options. However I did not switch back once again to 17264 to check this assumption.

I still think that the hostapd version build by maddes in his new 17264 build is not the best one (will not allow to set wme parameters) and that the one in the trunk should be used instead.

Coming back to the smartphone, setting ap_max_inactivity to 1800 has greatly enhanced the situation.

@slxar: I do not encourage to use the firewall.user facility for setting port forwarding: either use the luci web interface for this, or directly use uci commands or edit the /etc/config/firewall file. (I will add some examples later today).

On top of that, with what you've put in your firewall.user file, you are conflicting with the predefined rules of openwrt.

Here are the sample (adapt to your case and add them in the /etc/config/firewall file):

These 2 blocks open port 80 on the wan side and forward the request on port 80 of 192.168.2.5

config 'rule'
        option 'src' 'wan'
        option 'proto' 'tcp'
        option 'dest_port' '80'
        option 'target' 'ACCEPT'

config 'redirect'
        option src              wan
        option src_dport       80
        option dest             lan
        option dest_ip          192.168.2.5
        option dest_port        80
        option proto            tcp

Just duplicate these 2 blocks for your other ports (22, 25, 143, etc...)

(Last edited by operron on 10 Dec 2009, 21:44)

thank you very much and now it work
but still have another question
I still can't access to my server form lan while i type my external ip address

@slxar:
This is offtopic and answered several times in the forum. Please use the search function or create another thread. Thanks.

(Last edited by maddes.b on 10 Dec 2009, 23:37)

sorry for that, thank you very much for helping me to solve the problem

nbd of the OpenWrt team received a WRT350Nv2 yesterday, which I donated to him.
Webupgrade is now in the trunk, only sysupgrade is not committed due to the problems with the sanity check with http/ftp sources.
He already started checking out the hardware.
So there's a good chance that we get a working wifi/wlan with the latest mac80211 package in some weeks. Just give him time to get into it, he's doing this in his leisure time.

Btw this means that soon you can get the latest builds (right now without sysupgrade support) directly from the OpenWrt snapshots at http://downloads.openwrt.org/snapshots/trunk/orion/

Update 2009-12-16:
nbd was able to reproduce the kernel panics.

(Last edited by maddes.b on 17 Dec 2009, 22:29)

This a very very good news indeed! Thanks to you maddes !!!

Hi,

Is it possible to compile a firmware for a CH3SNAS or DNS-323 as both are ORION based?

I believe that the CH3SNAS and DNS-323 are 88F5xx82 based.

sumersetpt wrote:

Hi,

Is it possible to compile a firmware for a CH3SNAS or DNS-323 as both are ORION based?

I believe that the CH3SNAS and DNS-323 are 88F5xx82 based.

There's another project that supports the DNS-323 http://wiki.dns323.info/

@sumersetpt:
Try to find out if your board is already supported by the normal Linux kernel.
Also read the first 13 pages of this thread to see how DirkNL, StrikerNL and Kaloz managed to get WRT350N v2 support into the normal Linux Kernel with help from Marvell.
It will really help if you are a Linux developer, or have a good friend that is, or any other linux developer who is willing to help you.

(Last edited by maddes.b on 13 Dec 2009, 14:41)

Hi all,

since 15.12 you can build working image for Wlan:

OpenWrt Firmware
Kamikaze (r18779)
Load: 0.29 0.29 0.17
Hostname: WRT350nv2

System: armv5tel
Processor:  Feroceon rev 0 (v5l)
Load:  0.23, 0.05, 0.02
Memory: 29.50 MB (21% cached, 7% buffered, 23% free) 
Uptime:  1d 23h 37min 08s

Good work Thx for support!

Best regards

cm

Maybe your config setup is not crashing. Or maybe you did not compile OpenWrt as it is for release builds.
nbd couldn't reproduce the crashes at first, two days ago he compiled as it is done for release and could reproduce the crash, since then he hasn't committed anything yet.

Just started building a mini ramdisk build and a release ramdisk build for testing.

Mini build is uploaded (includes tun support).

Release build is uploaded.

(Last edited by maddes.b on 7 Apr 2010, 19:39)

Hi Guys

Can one of you supply me with a copy of linksys stock firmware 2.00.17. I cant get it anywhere and im in dire need!

Fantatsic mate cheers!!!!!

Oh, such luck !

I simple checkout new release via git made feeds update and build squashfs, with Luci and a few other options. ( some days before I build image for another device (TL- WR941N ->Atheros))
Then I wget the wrtn350-uImage and Root.squashfs into tmp on the router and made dd for uImage and dd for squashfs.
And I only know basics of Linux and learned a lot with playing on this device wink

But if there are still problems I wait until final bugfix  wink

If someone wants I can mail you the 2 files, or upload it somewhere.

Best regards

cm

Could finally test today, and can confirm that a mini build does not crash, while a release build does crash.

Update:
Posted mini+tun builds of r18861 on my ftp space.

(Last edited by maddes.b on 7 Apr 2010, 19:39)

Newbie question, i think router is bricked (maybe) but i m hoping i can revive without a jtag.  I d appreciate any comments on questions below.  Pls advice... 

My wnr854t was running the build I downloaded on 11/19, and I needed to open an incoming port using X-WRT gui.  Once I applied the changes, router was working on LAN side, but no WAN (specifically, no internet access)...  I ran firstboot, and then rebooted the router.  It didnt come back on after that, no ping using static ip (192.168.1.100 for pc, and 192.168.1.1 for router).  I have tried the 30/30/30 reset but no luck. 

Questions:
1.  Anything else I can try? 
2.  Also, if i cut up a serial cable and connect it to the board's serial interface without any other components in the middle, would that work?
3.  I am using a november build.  Is the reset button functional in those builds?


fyi, I ran into this same issue 2 weeks before also i.e. one port (ssh) was already open, and tried to open another port thru web gui.  On applying changes, router cannot get on internet any more.  Last time I ran into this, first boot solved the problem but this time it didnt go so well...  Thanks in advance.

hi nd_100

read this thread carefully and all of your questions are answered.

For serial (+5V VCC) you need levelshifter like ftdi232, or profilic, for 3,3V VCC which you need on your router, otherwise you can destroy it electrical!

look  for Wiki, google,...

br

cm

Thanks cmoegele... I ordered a buffered jtag from ebay, so i ll go that route...   

I have read thru the thread multiple times and bookmarked the relevant posts, but its a little overwhelming for a newbie like me...  Great learning experience... 

Best regards!

Sorry, posts 651 to 650 are missing from our archive.