1.92 stable doesn't exist yet, only nightly=+

The funny thing is that I unbridged them yesterday and then I could not access them neither via the wireless nor the ethernet interface, quite weird!!!

I'm trying to clarify what's going on there....
http://www.macsat.com/macsat/component/option,com_smf/Itemid,50/topic,923.45/

Yeah, I just installed/unpacked the transmission-daemon tar archive on top of the old one and that was it, but I'm using the -g option and not going to the default $HOME/.config directory.

I think that should not be touch whatever the case, you can always list what the tar is going to do just to double check, or create a copy of your .config just in case.

I've just noticed that the last 2 versions crash after a few minutes though...

When upgrading to a newer Transmission version I usually rebuild the whole C: drive. (Note that I am running Transmission as root, so my case may be less complicated than spanish_biker's.) From what I understand, I just need to install/unpack the transmission-daemon tar archive on top of the old one, and that'll preserve all my settings and all, is that so Joker?

Alright, so if you unbridge the two, and suppose you set up the GUI so as to give the box a static address, which one of the two interfaces (eth1 or wl0) gets the static address specified in the Airlive GUI?

Hi Joker, just in case you happen to read this, I think Transmission people released Transmission 1.92+, though I am more interested in 1.92 without the "+". Would you happen to be able to tell which one's 1.92, and build it please?

Many thanks!

Both of my WMU-6500FS boxes have been giving me a hard time: most of the times after cleanly rebooting them I am having trouble accessing them via the Ethernet port. It is only when I give them a hard shutdown (meaning press the button in the back!) and then restart them that I can connect. Any ideas why this is happening?

ah, I thought the bridge could be making things worse...

When I assigned that IP through the web interface, everything works fine, but if I put a different network in the web and then I change it through the command line, I cannot reach that network, although the IP seems to have been picked up :S

Then the PC's got a 192.168.123.111/24 without a gateway (as that's being used by the wireless card in the other network)

Do you see something weird in the airlive config?

eth1      Link encap:Ethernet  HWaddr 00:4F:67:02:D9:68
          inet addr:192.168.123.123  Bcast:0.0.0.0  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:632 errors:0 dropped:0 overruns:0 frame:0
          TX packets:2796 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:58287 (56.9 KiB)  TX bytes:571080 (557.6 KiB)
          Interrupt:11 Base address:0xe900


3: eth1: <BROADCAST,MULTICAST,UP,100> mtu 1500 qdisc pfifo_fast qlen 1000
    link/ether 00:4f:67:02:d9:68 brd ff:ff:ff:ff:ff:ff
    inet 192.168.123.123/24 scope global eth1

bridge is not a problem. "ip addr add X/Y dev eth1" it has to work. check your firewall/whatever/network. and airlive config (ifconfig/ip addr show/etc...)

Do you need to do something with the bridge that's created by default? (br0=eth1+wl0)

I created a different network with "ip addr add <NEW_IP>/24 dev eth1" and even though I've got an IP within the same range in my PC, I cannot see the Airlive through that interface.

I tried putting the bridge down, but then I could not reach it via the wireless (as expected) but neither via the eth1 with its new IP :S

Any idea what I could be doing wrong?