OpenWrt Forum Archive

Topic: sam's firmware collections for TP-Link WR703N

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

Lennong wrote:

I've finally got some time for testing your config. It should be doable to rip out OpenVPN and throw in PPP instead. When you say downgrade the mac80211 package, how do I do that?

In the current root directory of your openwrt do

svn update -r 28294 package/mac80211
s7mx1 wrote:
Lennong wrote:

I've finally got some time for testing your config. It should be doable to rip out OpenVPN and throw in PPP instead. When you say downgrade the mac80211 package, how do I do that?

In the current root directory of your openwrt do

svn update -r 28294 package/mac80211

Sweet! Thanks! I assume that applying the patches is simply run "patch -p00.wr703n.patch" from your pulled down openwrt-nas directory?

Generalenthu wrote:

Really nice to see you dotting the i's and crossing the t's. I ordered my unit mid last week and is yet to be shipped. On a related note, is there enough flash memory to include mpd in the firmware. All my music is on a nas which could be mounted on boot along with a remote mpd database. This may be impractical though.

To me the obvious alternative is to just run pulseaudio making it discoverable. I guess it could be connected to mpd running elsewhere. Anyways, I am a linux n00b; pardon me if it sounds ignorant.

I am planning to use a USB soundcard plugged into wr703n and connect it to aux in an ipod dock. Ideally would like to be able to draw power for wr703n from ipod male connector, but am not finding suitable cables.

Anyways, this setup should give Sonos a serious run for its money!

@Generalenthu

Unfortunately there is no space left for me to squeeze mpd inside unless you don't want the web gui wink. This can be done but it involves building openwrt from source code.

You have other options apart from squeezing mpd inside WR703N:
1) get/build a mpd with pulseaudio support for your nas. This is probably the best solution if you can get it done.
2) get another WR703N and install mpd on it with nfs/cifs support so you can mount your music collection. Only if you know how to build openwrt from source and patch things if necessary. This the next cheapest solution and the running electricity bill is among the lowest.
3) get raspi when its out next year and install mpd on it and mount your music collection via nfs/cifs. However you need to wait till at least January next year. It costs $13 more than WR703N.
4) Any x86 machines with mpd running on it. Probably the easiest to set up but consumes too much electricity and not good if you want to run 24/7.

We can probably live without auto discovery (takes precious space) as I have setup the dhcp host name and you can use name like openwrt-pulseaudio instead of ip address to access WR703N.

Not sure about the ipod dock as I have never used any apple's products. In theory you can mod a cable for that purpose.

Lennong wrote:
s7mx1 wrote:
Lennong wrote:

I've finally got some time for testing your config. It should be doable to rip out OpenVPN and throw in PPP instead. When you say downgrade the mac80211 package, how do I do that?

In the current root directory of your openwrt do

svn update -r 28294 package/mac80211

Sweet! Thanks! I assume that applying the patches is simply run "patch -p00.wr703n.patch" from your pulled down openwrt-nas directory?

patchs can be done that way (assume you copied them over to the root folder of openwrt first)

for file in 00*.patch ; do 
patch -p0 < $file
done

You can refer to the wiki page here http://code.google.com/p/xbox-remote/wi … V5Firmware. Not exactly the same but you should provide some good information.

(Last edited by s7mx1 on 12 Dec 2011, 14:23)

s7mx1 wrote:
Lennong wrote:
s7mx1 wrote:

In the current root directory of your openwrt do

svn update -r 28294 package/mac80211

Sweet! Thanks! I assume that applying the patches is simply run "patch -p00.wr703n.patch" from your pulled down openwrt-nas directory?

patchs can be done that way (assume you copied them over to the root folder of openwrt first)

for file in 00*.patch ; do 
patch -p0 < $file
done

Excellent! Thanks! smile

Lennong wrote:
s7mx1 wrote:
Lennong wrote:

Sweet! Thanks! I assume that applying the patches is simply run "patch -p00.wr703n.patch" from your pulled down openwrt-nas directory?

patchs can be done that way (assume you copied them over to the root folder of openwrt first)

for file in 00*.patch ; do 
patch -p0 < $file
done

Excellent! Thanks! smile

Just updated the last post regarding a wiki reference. Hope it will help.

s7mx1 wrote:

@Generalenthu

Unfortunately there is no space left for me to squeeze mpd inside unless you don't want the web gui wink. This can be done but it involves building openwrt from source code.

You have other options apart from squeezing mpd inside WR703N:
1) get/build a mpd with pulseaudio support for your nas. This is probably the best solution if you can get it done.
2) get another WR703N and install mpd on it with nfs/cifs support so you can mount your music collection. Only if you know how to build openwrt from source and patch things if necessary. This the next cheapest solution and the running electricity bill is among the lowest.
3) get raspi when its out next year and install mpd on it and mount your music collection via nfs/cifs. However you need to wait till at least January next year. It costs $13 more than WR703N.
4) Any x86 machines with mpd running on it. Probably the easiest to set up but consumes too much electricity and not good if you want to run 24/7.

We can probably live without auto discovery (takes precious space) as I have setup the dhcp host name and you can use name like openwrt-pulseaudio instead of ip address to access WR703N.

Not sure about the ipod dock as I have never used any apple's products. In theory you can mod a cable for that purpose.

I am now setup like #4 with an old laptop and hate it.

I am pretty much assuming your pulseaudio firmware supports wifi. Tell me if I am way off base there. I don’t have a lot of confidence on the WR703N wifi chipset and have a feeling pulseaudio streaming would be glitchy as I have a weak signal where I need the speakers. Also there is the issue of network saturation with raw audio streaming.

So it looks like a choice between mpd + alsa (if it is small enough) where it would be a stand alone wifi player _or_ a pulseaudio player with probably choppy music, but networked and in sync with my main wired speakers. 

Am a little worried about tinkering with my nas (raid) as it is my main repository for all the important docs and backups.

The other alternative is running mpd + pulseaudio on 2 Raspberries pi, one replacing my current x86 setup and another with wifi card and remote speakers. So raspi vs WR703N, raspi is more expensive by $13 +  wificard, but looks like it will give me the ability to switch between standalone mode and synchronized mode. I am raring to try pulseaudio on WR703N first in any case.

Finally my speaker cabling and WR703N powering plan is best expained by this product. Not splurging 30 bucks for a cable though.

http://www.cablejive.com/products/dockBossplus.html

Generalenthu wrote:

I am now setup like #4 with an old laptop and hate it.

I am pretty much assuming your pulseaudio firmware supports wifi. Tell me if I am way off base there. I don’t have a lot of confidence on the WR703N wifi chipset and have a feeling pulseaudio streaming would be glitchy as I have a weak signal where I need the speakers. Also there is the issue of network saturation with raw audio streaming.

So it looks like a choice between mpd + alsa (if it is small enough) where it would be a stand alone wifi player _or_ a pulseaudio player with probably choppy music, but networked and in sync with my main wired speakers. 

Am a little worried about tinkering with my nas (raid) as it is my main repository for all the important docs and backups.

The other alternative is running mpd + pulseaudio on 2 Raspberries pi, one replacing my current x86 setup and another with wifi card and remote speakers. So raspi vs WR703N, raspi is more expensive by $13 +  wificard, but looks like it will give me the ability to switch between standalone mode and synchronized mode. I am raring to try pulseaudio on WR703N first in any case.

Finally my speaker cabling and WR703N powering plan is best expained by this product. Not splurging 30 bucks for a cable though.

http://www.cablejive.com/products/dockBossplus.html

The main application of the pulseaudio firmware will be streaming over wifi otherwise what's the fun wink

The wifi chip inside WR703N is quite good and it's only being let down by the wifi antenna printed on the PCB. You need to adjust the position of WR703N to get the best reception. If you have some old wifi router lying around you can rip the antenna and solder it on WR703N which should give a boot to the wifi performance. I have seen other people installed SMA  (detachable) antenna on WR703N.

If you have a weak wifi coverage I would suggest investing a bit on the external wifi antenna on either WR703N or the usb wifi dongle that goes with pi. I believe you should expect similar wifi performance between WR703N and any usb wifi dongle without external antenna. If that doesn't help you can always get a wifi range extender or even powerline.

Streaming raw stereo audio actually does not require a lot bandwidth. It will need around 180KB/s for stereo 48KHz raw audio streaming ( airplay or pulseaudio). What's more important is latency. The playback may become choppy when you have latency pikes on your wifi network.

With a strong wifi network I can get constant smooth streaming playback out of the usb speakers attached to WR703N. When watching TV shows I don't notice any out of sync between video and audio which is remarkable (the audio is being streamed from another wifi client on the same network).

@Generalenthu - where can you buy raspberry pi?
703n is already here smile

Hello. Sorry if I missed the information somewhere. Is it true that the nas build can only function as AP? If so, would it be possible to trade the openvpn module for a router/gateway?
Thanks.

@s7mx1

Nice release. The re-sampling discussion and the relay usage was cool. Looks like My 703n is not shipped yet. Damn you volumerates.

maurer wrote:

@Generalenthu - where can you buy raspberry pi?
703n is already here smile

@maurer
True. Its become Ras-Pie-in-the-sky

The pulseaudio looks really nice! Dang, I can't even reproduce your NAS build even with patches and .config from you. I get tons of errors or builds that miss packages, very strange. Still, nice builds and fun to try out. smile

umggc wrote:

Hello. Sorry if I missed the information somewhere. Is it true that the nas build can only function as AP? If so, would it be possible to trade the openvpn module for a router/gateway?
Thanks.

@umggc
What exactly do you want to achieve with router/gateway?

The current nas firmware will use the ethernet port on WR730N as the wan port and any wifi clients can access internet via the wan port if it's connected upstream (i.e. connected to your home gateway).

Lennong wrote:

The pulseaudio looks really nice! Dang, I can't even reproduce your NAS build even with patches and .config from you. I get tons of errors or builds that miss packages, very strange. Still, nice builds and fun to try out. smile

@Lennong
If all patches are applied fine. You should clean the openwrt root directory by

make -j2 clean

then build it again by

make -j2

If you encountered any errors then compile it in verbose mode

make V=99

and post the output to pastebin and send me the link.

s7mx1 wrote:
umggc wrote:

Hello. Sorry if I missed the information somewhere. Is it true that the nas build can only function as AP? If so, would it be possible to trade the openvpn module for a router/gateway?
Thanks.

@umggc
What exactly do you want to achieve with router/gateway?

The current nas firmware will use the ethernet port on WR730N as the wan port and any wifi clients can access internet via the wan port if it's connected upstream (i.e. connected to your home gateway).

@umggc

Just noticed that the firewall script does not have execution permission. I will fix it in the next release. Meanwhile you can fix it by running the following command

chmod +x /etc/init.d/firewall
/etc/init.d/firewall start
s7mx1 wrote:
Lennong wrote:

The pulseaudio looks really nice! Dang, I can't even reproduce your NAS build even with patches and .config from you. I get tons of errors or builds that miss packages, very strange. Still, nice builds and fun to try out. smile

@Lennong
If all patches are applied fine. You should clean the openwrt root directory by

make -j2 clean

then build it again by

make -j2

If you encountered any errors then compile it in verbose mode

make V=99

and post the output to pastebin and send me the link.

Output from patching:
http://pastebin.com/7QEhV4iK

Output from build:
http://pastebin.com/FQiT81ps

First build I did resulted in a image that was bootable but with a few packages and functions missing..could not change password and not login via SSH. Second build as shown in pastebin went through in web UI for upgrade, but resulted in a non-reachable router. It boots and goes via flashing state to steady light, so I assume it gets through uboot properly. Will solder the UART today anyway and see whats going on.

s7mx1 wrote:

Unfortunately there is no space left for me to squeeze mpd inside unless you don't want the web gui wink. This can be done but it involves building openwrt from source code.

I've heard that the U-Boot (128 Kbytes) within TP-LINK routers only supports gzip compression. That's why the size of kernel is much bigger than the lzma compressed one. If you want to squeeze 300-400 Kbytes from kernel, you can copy the source code of lzma compression routine from Linksys/D-Link GPL code and merge it with TP-LINK's code and compile U-Boot. There's a great chance that you can still keep U-Boot within 128 KBytes. The next step is to adjust the mtd partitions in OpenWrt and there you have at least extra 300 KBytes for the application.

Good luck.

GPL Code Center - Welcome to TP-LINK - TL-MR3020v1 or TL-WR740Nv4

Lennong wrote:
s7mx1 wrote:
Lennong wrote:

The pulseaudio looks really nice! Dang, I can't even reproduce your NAS build even with patches and .config from you. I get tons of errors or builds that miss packages, very strange. Still, nice builds and fun to try out. smile

@Lennong
If all patches are applied fine. You should clean the openwrt root directory by

make -j2 clean

then build it again by

make -j2

If you encountered any errors then compile it in verbose mode

make V=99

and post the output to pastebin and send me the link.

Output from patching:
http://pastebin.com/7QEhV4iK

Output from build:
http://pastebin.com/FQiT81ps

First build I did resulted in a image that was bootable but with a few packages and functions missing..could not change password and not login via SSH. Second build as shown in pastebin went through in web UI for upgrade, but resulted in a non-reachable router. It boots and goes via flashing state to steady light, so I assume it gets through uboot properly. Will solder the UART today anyway and see whats going on.

@Lennong

I did mention that my patches have only been  tested for revision 28854. I would suggest start from fresh. To check out revision 28854 of openwrt do

svn co -r 28854 svn://svn.openwrt.org/openwrt/trunk openwrt-trunk
cd openwrt-trunk
./scripts/feeds update -a
./scripts/feeds install -a
svn update -r 28294 package/mac80211
svn update -r 28602 feeds/packages
svn update -r 4986 feeds/xwrt
svn co https://xbox-remote.googlecode.com/svn/trunk/embeded-system/openwrt/nas/trunk-28854 trunk-28854
cp trunk-28854/config-nas .config
for file in trunk-28854/patches/00.*.patch ; do patch -p0 < $file ; done
grep /etc/init.d/ trunk-28854/patches/00*.patch | grep Index | awk '{print $2}' | xargs chmod +x
grep "\.sh" trunk-28854/patches/00.*.patch | grep Index | awk '{print $2}' | xargs chmod +x
make -j2

which should sort everything out for you. Please make sure the image produced by the above build works fine for you before carry on your own modifications.

(Last edited by s7mx1 on 14 Dec 2011, 15:23)

fyi wrote:
s7mx1 wrote:

Unfortunately there is no space left for me to squeeze mpd inside unless you don't want the web gui wink. This can be done but it involves building openwrt from source code.

I've heard that the U-Boot (128 Kbytes) within TP-LINK routers only supports gzip compression. That's why the size of kernel is much bigger than the lzma compressed one. If you want to squeeze 300-400 Kbytes from kernel, you can copy the source code of lzma compression routine from Linksys/D-Link GPL code and merge it with TP-LINK's code and compile U-Boot. There's a great chance that you can still keep U-Boot within 128 KBytes. The next step is to adjust the mtd partitions in OpenWrt and there you have at least extra 300 KBytes for the application.

Good luck.

GPL Code Center - Welcome to TP-LINK - TL-MR3020v1 or TL-WR740Nv4

I would rather remove gui in order to gain more than 1MB space which is less risky. There are other options available like usb disk or network file system to dramatically increase the available disk space.

s7mx1 wrote:
umggc wrote:

Hello. Sorry if I missed the information somewhere. Is it true that the nas build can only function as AP? If so, would it be possible to trade the openvpn module for a router/gateway?
Thanks.

@umggc
What exactly do you want to achieve with router/gateway?

The current nas firmware will use the ethernet port on WR730N as the wan port and any wifi clients can access internet via the wan port if it's connected upstream (i.e. connected to your home gateway).

@s7mx1,

I guess I misunderstood your description of the build. I thought it was stripped off stuff like DHCP server and can only be used as purely an AP in conjunction with another router/gateway (inferred from your photo).

Thanks for the good work!

umggc wrote:
s7mx1 wrote:
umggc wrote:

Hello. Sorry if I missed the information somewhere. Is it true that the nas build can only function as AP? If so, would it be possible to trade the openvpn module for a router/gateway?
Thanks.

@umggc
What exactly do you want to achieve with router/gateway?

The current nas firmware will use the ethernet port on WR730N as the wan port and any wifi clients can access internet via the wan port if it's connected upstream (i.e. connected to your home gateway).

@s7mx1,

I guess I misunderstood your description of the build. I thought it was stripped off stuff like DHCP server and can only be used as purely an AP in conjunction with another router/gateway (inferred from your photo).

Thanks for the good work!

DHCP and iptables are critical parts and I will never remove them smile. I am working on a more easy network setup via web gui so you don't have to mess around with various configuration files which is prone to problems by un-experienced openwrt users. In fact this is probably the no.1 reason for unreachable WR703N.

I will try to release them this weekends. Stay tuned.

@s7mx1
I flashed your PulseAudio firmware on 703n,but I have some problems.
When I pulg my Logitech sound card,the 703n cannot identify my sound card.
On your firmware I cannot find /dev/dsp and /dev/audio.
But on another trunk firmware after I okpg install kmod-usb-audio I can find that,and the madplay also can play mp3 file.
here is my error message.Could you help me with that?

root@OpenWrt-PulseAudio:~# pulseaudio -vv
W: [pulseaudio] main.c: This program is not intended to be run as root (unless --system is specified).
D: [pulseaudio] core-rtclock.c: Timer slack is set to 50 us.
D: [pulseaudio] core-util.c: setpriority() worked.
I: [pulseaudio] core-util.c: Successfully gained nice level -11.
I: [pulseaudio] main.c: This is PulseAudio 1.1
D: [pulseaudio] main.c: Compilation host: mips-openwrt-linux-gnu
D: [pulseaudio] main.c: Compilation CFLAGS: -Os -pipe -mips32r2 -mtune=mips32r2 -fno-caller-saves -fhonour-copts -msoft-float -I/media/HardDisk3/openwrt-trunk-staging-pulseaudio/staging_dir/target-mips_r2_uClibc-0.9.32/usr/lib/libiconv-stub/include -I/media/HardDisk3/openwrt-trunk-staging-pulseaudio/staging_dir/target-mips_r2_uClibc-0.9.32/usr/lib/libintl-stub/include -std=gnu99  -Wall -W -Wextra -Wno-long-long -Wvla -Wno-overlength-strings -Wunsafe-loop-optimizations -Wundef -Wformat=2 -Wlogical-op -Wsign-compare -Wformat-security -Wmissing-include-dirs -Wformat-nonliteral -Wpointer-arith -Winit-self -Wdeclaration-after-statement -Wfloat-equal -Wmissing-prototypes -Wredundant-decls -Wmissing-declarations -Wmissing-noreturn -Wshadow -Wendif-labels -Wcast-align -Wstrict-aliasing -Wwrite-strings -Wno-unused-parameter -ffast-math -Wp,-D_FORTIFY_SOURCE=2 -fno-common -fdiagnostics-show-option
D: [pulseaudio] main.c: Running on host: Linux mips 2.6.39.4 #34 Mon Dec 12 15:04:51 GMT 2011
D: [pulseaudio] main.c: Found 1 CPUs.
I: [pulseaudio] main.c: Page size is 4096 bytes
D: [pulseaudio] main.c: Compiled with Valgrind support: no
D: [pulseaudio] main.c: Running in valgrind mode: no
D: [pulseaudio] main.c: Running in VM: no
D: [pulseaudio] main.c: Optimized build: yes
D: [pulseaudio] main.c: All asserts enabled.
I: [pulseaudio] main.c: Machine ID is OpenWrt-PulseAudio.
I: [pulseaudio] main.c: Using runtime directory /tmp/.pulse/OpenWrt-PulseAudio-runtime.
I: [pulseaudio] main.c: Using state directory /tmp/.pulse.
I: [pulseaudio] main.c: Using modules directory /usr/lib/pulse-1.1/modules.
I: [pulseaudio] main.c: Running in system mode: no
I: [pulseaudio] main.c: Fresh high-resolution timers available! Bon appetit!
D: [pulseaudio] memblock.c: Using shared memory pool with 1024 slots of size 4.0 KiB each, total size is 4.0 MiB, maximum usable slot size is 4056
I: [pulseaudio] module-device-restore.c: Successfully opened database file '/tmp/.pulse/OpenWrt-PulseAudio-device-volumes'.
I: [pulseaudio] module.c: Loaded "module-device-restore" (index: #0; argument: "").
I: [pulseaudio] module-stream-restore.c: Successfully opened database file '/tmp/.pulse/OpenWrt-PulseAudio-stream-volumes'.
I: [pulseaudio] module.c: Loaded "module-stream-restore" (index: #1; argument: "").
E: [pulseaudio] module.c: Failed to open module "module-card-restore": file not found
E: [pulseaudio] main.c: Module load failed.
E: [pulseaudio] main.c: Failed to initialize daemon.
I: [pulseaudio] module.c: Unloading "module-device-restore" (index: #0).
I: [pulseaudio] module.c: Unloaded "module-device-restore" (index: #0).
D: [pulseaudio] core-subscribe.c: Dropped redundant event due to remove event.
I: [pulseaudio] module.c: Unloading "module-stream-restore" (index: #1).
I: [pulseaudio] module.c: Unloaded "module-stream-restore" (index: #1).
D: [pulseaudio] core-subscribe.c: Dropped redundant event due to remove event.
I: [pulseaudio] main.c: Daemon terminated.


BTW I am not good at English,sorry for my bad English...

@tosslee

What's the model number of the Logitech sound card?


I will need the result of the dmesg on both devices. If the 703N recognises the sound card you can find it in

/proc/asound/cards

You can also found out what usb devices are attached from the web gui here http://openwrt-pulseaudio/cgi-bin/webif/status-usb.sh

By the way the alsa module is not loaded by pulseaudio directly. This is handled by the pulse-monitor script to support plug & play. Therefore you need to make sure its running. In the new firmware (hopefully to be released soon) it will be handled by hotplug event which is more efficient.


tosslee wrote:

@s7mx1
I flashed your PulseAudio firmware on 703n,but I have some problems.
When I pulg my Logitech sound card,the 703n cannot identify my sound card.
On your firmware I cannot find /dev/dsp and /dev/audio.
But on another trunk firmware after I okpg install kmod-usb-audio I can find that,and the madplay also can play mp3 file.
here is my error message.Could you help me with that?

(Last edited by s7mx1 on 20 Dec 2011, 17:55)

@s7mx1
uh,actually I can find my sound card in

/proc/asound/cards

.

And from the web gui I can got the usb msg.

Bus    Device    Product                                                    Manufacturer                    VendorID:ProdID    USB version    Speed
01    1            Atheros  AR91xx built-in EHCI controller    Linux 2.6.39.4 ehci_hcd    1d6b:0002            2.00                    480 Mbps
01    2            Logitech USB Headset                            SCEA Inc.                     046d:0a0b            1.10                    12 Mbps

I could not understand how the pulse-monitor scirpt work.It seems not running under 703n.
Unfortunately I am a linux newer,I only have a fedora15 Live on VMware.
I follow the http://wiki.openwrt.org/doc/howto/pulseaudio   When I entered "pacmd load-module module-tunnel-sink server=openwrt-pulseaudio",there is no response- -

What I need to do is stream audio from Win7 to wr703n.From now on I can config the pulseaudio(win32 version) correctly ,use mpd&mpc play mp3 file.
But stream audio I haven't got a clue yet...

(Last edited by tosslee on 21 Dec 2011, 11:59)

tosslee wrote:

@s7mx1
uh,actually I can find my sound card in

/proc/asound/cards

.

And from the web gui I can got the usb msg.

Bus    Device    Product                                                    Manufacturer                    VendorID:ProdID    USB version    Speed
01    1            Atheros  AR91xx built-in EHCI controller    Linux 2.6.39.4 ehci_hcd    1d6b:0002            2.00                    480 Mbps
01    2            Logitech USB Headset                            SCEA Inc.                     046d:0a0b            1.10                    12 Mbps

I could not understand how the pulse-monitor scirpt work.It seems not running under 703n.
Unfortunately I am a linux newer,I only have a fedora15 Live on VMware.
I follow the http://wiki.openwrt.org/doc/howto/pulseaudio   When I entered "pacmd load-module module-tunnel-sink server=openwrt-pulseaudio",there is no response- -

What I need to do is stream audio from Win7 to wr703n.From now on I can config the pulseaudio(win32 version) correctly ,use mpd&mpc play mp3 file.
But stream audio I haven't got a clue yet...

@tosslee

Sorry to inform you incorrectly. Having been messing my head with multi wan support, aka multipath routing, I was not looking the release properly.

If you flashed my latest firmware openwrt-pulseaudio-28854-1212-tl-wr703n-v1-squashfs-factory.bin then the loading/unloading pulseaudio alsa module is handled by hotplug script already. The pulse-monitor is obsoleted in that release.

You should not run pulseaudio by hand as it will start automatically on boot or when the usb soundcard is plugged in.

What I would suggest is flash the latest firmware if you have not done so. Reboot WR703N with usb sound card attached and paste the output of logread from console. Run the  pacmd on your windows box again and check the output of logread from WR703N and you should notice more entries from pulseaudio. Otherwise it could be something to do with your windows firewall or windows pulseaudio server.

I promise in the next release that you will have a special pulseaudio status page on web gui like this
http://xbox-remote.googlecode.com/files/pulse-status-01.png
and this
http://xbox-remote.googlecode.com/files/pulse-status-02.png
which will make life a lot easier.

(Last edited by s7mx1 on 21 Dec 2011, 14:08)