magicJack and magicJack Plus Support, Reviews, FAQs and Tricks

Hi 985ach
Glad you're O.K.
I thought you had the 'ear-dizzy' thing again when not hearing from you for awhile.

I see you found another old toy..

I'm sure there's a way to flash the stock firmware to it...
either with a separate programmer, or maybe someone on the OpenWRT forum may have a fix...

Anyway... if you'd like to 'take-a-break' from the HooToo... I understand


Nice having you here...bye.

Hey everyone... One of the original members at the OpenWRT forum, who made an OpenVPN installation Tutorial Post, came back, and posted how to do it specifically for the HooToo TM02. . How cool is that...?
I haven't tested this yet...
...hahaha...but I've put it here for those who'd want to try.

One extra bit I'm adding now are the two actual files associated with the TM02
in the directory the Original Poster mentions at the thread below.

*** RECENT ADDITIONAL IMPORTANT INFO ***

-------
There are more posts dealing with this VPN install and my below concerns, ...also mentioned in the original posters thread starting at...
https://forum.openwrt.org/viewtopic.php ... 05#p316605

Many of the issues mentioned below, here, are addressed by the original poster (600cc) ...so be sure to view that post often to see any changes or additions to the thread regarding all this.
He assures he has not had any of the issues with the TM02.
-------

His post links to the folder that is from the 15.05.1 folder, but that folder is said to have defective builds that had issues with old kernel versions being added to newer builds, creating kernel hangs during boot, and package mis-matches when installing additions.

See this thread mentioning it...
https://forum.openwrt.org/viewtopic.php?id=63426

The known original stable build from September 14th 2015 is at

https://downloads.openwrt.org/chaos_cal ... ps/rt305x/

https://downloads.openwrt.org/chaos_cal ... /packages/

But, within that above link'd 'Packages' folder, I see the 'Base' folder dated March 2nd 2016,
and the 'packages' folder dated March 1st 2016 , so I don't know if those folders are also affected being the others are dated from Sept 2015.

I think it may be best to wait until this all gets straightened out at the OpenWRT forum... I wish I could try this now, but I'm still waiting to test another developers iOS App update, with the DLNA / Samba file server, and need my last 3rd TM02 with the factory firmware on it to do this.

If any of you still want to try... I'm sure the configuration for the OpenVPN is still valid that the original poster mentions...
...this other kernel issue happened when the servers were down at the OpenWRT site, and the build-BOTs created firmware files with mixed kernels by accident...

the original 15.05 files are as follows

I think the ...
https://downloads.openwrt.org/chaos_cal ... pgrade.bin
... is the main sysupgrade file if you've already replaced the HooToo factory firmware.

There's another one...
https://downloads.openwrt.org/chaos_cal ... uImage.bin
... called initramfs-uImage ... I don't know what that one is, ...
... but the larger file size one is the sysupgrade file...and seems more complete.

--------

@985ach
I hope you'll see this..!
If anyone deserves to see the final solution...IT'S YOU ..!

You worked so hard to get it going, and burned yer little brain out...poor thing...!

--------

OpenVPN on HooToo TM02 TripMate nano router

In original thread... From the original poster Tutorial ...
https://forum.openwrt.org/viewtopic.php?id=57090

At new post specifically for TM02 VPN Config and Setup ...
https://forum.openwrt.org/viewtopic.php ... 63#p316563

The complete copied text of post, and full configs in 'code' boxes...
...all I did was format it better for text reading here or copied to a NotePad style App...



Well, that took less time than I thought it might.
My HooToo TripMate Nano TM02 (or whatever it's called) now has Chaos Calmer 15.05.1 installed from...

https://downloads.openwrt.org/chaos_cal ... ps/rt305x/

...and OpenVPN is running and routing successfully.

Here's how I did it. All of the following steps were carried out on the TM02's command line, either via Telnet or SSH. I didn't bother using the web GUI for anything apart from setting a new IP address.


** Assumptions: **

- You know how to use Telnet and/or SSH, and have a suitable Telnet/SSH client on your computer.

-You know your way around the Linux command line, the hierarchical file system, and know how to edit text files with vi or nano.

-You know what IP address scheme is used for your own network, and how to allocate appropriate IP addresses for new devices on your network.

-You know how to install and configure OpenVPN as a server on a device/computer with multiple NICs - this is not an OpenVPN tutorial, but rather a recipe for getting OpenVPN to work on a device with a single NIC.

-You know how to install and configure OpenWRT - this is not an OpenWRT tutorial.


1. Install Chaos Calmer 15.05.1. Reset the device to factory defaults. Connect to the device at 192.168.1.1. You can use either the web GUI or Telnet (or SSH after you set a root password).
I connected a laptop directly to the TM02's ethernet port and made the necessary IP address changes in the next step before connecting the TM02 to the rest of my network.

2. Give the device a new hostname, unbridge the LAN interface so that it's wired-only, and give the LAN interface a valid static IP address configuration for your network (192.168.1.1 could possibly conflict with your edge router, if you're not careful). Finally, disable the DHCP server on the LAN interface.
It's probably not necessary to unbridge the LAN network, but if you're not using the wireless radio then why include it in the configuration?

3. Connect the TM02 to your network.
If you don't disable the DHCP server on the LAN interface in step 2, there could be a conflict between the TM02 and your real DHCP server.

4. Install the packages openvpn-openssl and openvpn-easy-rsa (and, optionally, luci-app-openvpn)
luci-app-openvpn is only needed if you want to manage the VPN from the web GUI. I don't bother; the command line is fine for my needs.

5. Edit /etc/easy-rsa/vars to contain the details you want. Keep KEY_SIZE at 2048 or higher for security.
Near the bottom of /etc/easy-rsa/vars are some lines you can personalise (KEY_COUNTRY, KEY_PROVINCE, etc.) As long as they're not blank, they can contain pretty much anything you choose.

6. Create the necessary CA, keys, and certificates. I also elected to create a TLS key and a CRL, for added security.
6.1 build-ca
6.2 build-key-server server
6.3 build-key-pkcs12 dummy
6.4 revoke-full dummy
6.5 build-key-pkcs12 client1
6.6 build-key-pkcs12 client2
6.7 build-dh
6.8 openvpn --genkey --secret /etc/easy-rsa/keys/ta.key
6.3 creates a dummy certificate, 6.4 creates the CRL by revoking the dummy certificate, and 6.8 creates the TLS key. All three are optional. If you elect to include them, you must also ensure that appropriate lines are included in /etc/config/openvpn

6. Copy the required certificates and keys from /etc/easy-rsa/keys to /etc/openvpn.
At a minimum, this should be ca.crt, server.crt, server.key, and dhXXXX.pem, where XXXX is your key size from step 5. You should also copy ta.key and crl.pem if you've decided to include them.

7. Edit (or create) the file /etc/config/openvpn to contain values suitable for your network and certificate/key files created in step 5.
This file controls how the OpenVPN server will behave. If there are any mistakes, the OpenVPN process will fail to start.

8. Start the OpenVPN service by issuing the command /etc/init.d/openvpn start. Check the output of the ps command to verify that there is an openvpn process running. If there isn't, check the contents of /tmp/openvpn.log for more information.
The most likely cause of any failure is a spelling mistake in the configuration file, or a missing certificate/key file. Once you get the openvpn process running successfully, it will create a new virtual network interface called 'tun0', which will be used in the next few steps.

9. Create a new WAN interface, bound to the physical interface eth0 and without any protocol assigned.
This is necessary for a later step involving the firewall. For this to work properly, you must have a WAN and LAN interface defined. This is where I slipped up the first time around at the top of this thread.

10. Create a new VPN interface, bound to the virtual interface tun0 and also without any protocol assigned.
This is also necessary for the firewall. Later in this process you will configure the firewall to allow traffic between the WAN, LAN, and VPN.

11. Configure the firewall zone settings to allow traffic from the LAN Zone to the WAN and VPN Zones.

12. Configure the firewall zone settings to allow traffic from the VPN Zone to the LAN and WAN Zones.
It is not necessary to allow any traffic from the WAN Zone; that should remain unchanged from the standard default configuration.

13. Configure the firewall traffic rules to allow inbound UDP traffic from the WAN to port 1194 on the device.
By default, inbound traffic is dropped or rejected. Allowing inbound traffic to UDP 1194 on the WAN interface allows inbound VPN clients to connect.

14. Configure the network's edge (Internet) router to forward (NAT) inbound traffic for UDP port 1194 to the HooToo device.

My edge router also runs OpenWRT, which makes things easier!

Notes:

This can also work if the TM02's LAN interface is set to DHCP, but it requires additional work to get dynamic port forwarding set up on your edge router. For now, stick to static IP until you're comfortable you've got it working.

build-dh takes a very long time to run, especially if you configure a high value for KEY_SIZE in /etc/easy-rsa/vars. The TM02 does not have a fast CPU, so be prepared to wait. And wait. Go and make a cup of tea, or watch a television show.

All of the key-generation commands can be run on the TM02, but I highly recommend running build-dh on a proper computer with a decent CPU and then copying the resulting .PEM file from your computer to the TM02.

I used a KEY_SIZE of 512 strictly for testing, because it's small enough for the TM02 to run build-dh reasonably quickly. However, a key size of 512 is not secure. The default KEY_SIZE is 2048, which should be secure enough for now. If you're feeling paranoid, you can increase KEY_SIZE to 4096. Note: a higher key size increases the client negotiation and connection time.

You can generate all the certificates and keys on a separate computer and just copy the necessary files to the TM02; you don't have to generate any certs or keys directly on the device.

Pay close attention when generating the certificates. You can press Return to skip past many of the prompts, but there are some prompts you must answer with a "y".

You do not have to specify an export password when generating the PKCS12 certificates, but it is highly recommended that you do so. The export password is what keeps the key secure. Without it, anyone can use the certificate if they get hold of it.

Changes you make to the files in /etc/config can be seen in the web GUI and in the console uci command, and vice-versa: any changes you make with uci or the web GUI will be reflected in the contents of /etc/config.

You can monitor the progress of any client connection attempts if you issue the command tail -f /tmp/openvpn.log on the TM02's command line. Press Ctrl-C when you want to stop monitoring.

I have included my TM02's configuration files here:

/etc/config/system

config system
option hostname 'tm02'
option zonename 'UTC'
option timezone 'GMT0'
option conloglevel '8'
option cronloglevel '8'

config timeserver 'ntp'
option enabled '1'
list server 'ntp1.npl.co.uk'
list server 'ntp2.npl.co.uk'
list server '0.uk.pool.ntp.org'
list server '1.uk.pool.ntp.org'
list server '2.uk.pool.ntp.org'
list server '3.uk.pool.ntp.org'

config led 'led_eth'
option name 'Ethernet'
option sysfs 'ht-tm02:green:lan'
option dev 'eth0'
option trigger 'netdev'
option mode 'link tx rx'

config led 'led_wifi_led'
option name 'wifi'
option sysfs 'ht-tm02:blue:wlan'
option dev 'wlan0'
option trigger 'netdev'
option mode 'link tx rx'


/etc/config/network - change the options under "config interface 'lan'" to match your network

config interface 'loopback'
option ifname 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'

config globals 'globals'

config interface 'lan'
option ifname 'eth0'
option proto 'static'
option ipaddr '192.168.20.23'
option netmask '255.255.255.0'
option gateway '192.168.20.1'
option broadcast '192.168.20.255'
option dns '192.168.20.1'

config interface 'vpn'
option ifname 'tun0'
option proto 'none'

config interface 'wan'
option ifname 'eth0'
option proto 'none'

config switch
option name 'switch0'
option reset '1'
option enable_vlan '0'


/etc/config/dhcp

config dnsmasq
option domainneeded '1'
option boguspriv '1'
option filterwin2k '0'
option localise_queries '1'
option rebind_protection '1'
option rebind_localhost '1'
option local '/lan/'
option domain 'lan'
option expandhosts '1'
option nonegcache '0'
option authoritative '1'
option readethers '1'
option leasefile '/tmp/dhcp.leases'
option resolvfile '/tmp/resolv.conf.auto'
option localservice '1'

config dhcp 'lan'
option interface 'lan'
option ignore '1'

config dhcp 'wan'
option interface 'wan'
option ignore '1'

config odhcpd 'odhcpd'
option maindhcp '0'
option leasefile '/tmp/hosts/odhcpd'
option leasetrigger '/usr/sbin/odhcpd-update'


/etc/config/firewall

config defaults
option syn_flood '1'
option input 'ACCEPT'
option output 'ACCEPT'
option drop_invalid '1'
option forward 'DROP'

config zone
option name 'lan'
option input 'ACCEPT'
option output 'ACCEPT'
option forward 'ACCEPT'
option network 'lan'

config zone
option name 'wan'
option output 'ACCEPT'
option masq '1'
option mtu_fix '1'
option network 'wan'
option input 'DROP'
option forward 'DROP'

config forwarding
option src 'lan'
option dest 'wan'

config rule
option name 'Allow-DHCP-Renew'
option src 'wan'
option proto 'udp'
option dest_port '68'
option target 'ACCEPT'
option family 'ipv4'

config rule
option name 'Allow-Ping'
option src 'wan'
option proto 'icmp'
option icmp_type 'echo-request'
option family 'ipv4'
option target 'ACCEPT'

config rule
option name 'Allow-DHCPv6'
option src 'wan'
option proto 'udp'
option src_ip 'fe80::/10'
option src_port '547'
option dest_ip 'fe80::/10'
option dest_port '546'
option family 'ipv6'
option target 'ACCEPT'

config rule
option name 'Allow-ICMPv6-Input'
option src 'wan'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
list icmp_type 'router-solicitation'
list icmp_type 'neighbour-solicitation'
list icmp_type 'router-advertisement'
list icmp_type 'neighbour-advertisement'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'

config rule
option name 'Allow-ICMPv6-Forward'
option src 'wan'
option dest '*'
option proto 'icmp'
list icmp_type 'echo-request'
list icmp_type 'echo-reply'
list icmp_type 'destination-unreachable'
list icmp_type 'packet-too-big'
list icmp_type 'time-exceeded'
list icmp_type 'bad-header'
list icmp_type 'unknown-header-type'
option limit '1000/sec'
option family 'ipv6'
option target 'ACCEPT'

config include
option path '/etc/firewall.user'

config zone
option input 'ACCEPT'
option forward 'DROP'
option output 'ACCEPT'
option name 'vpn'
option network 'vpn'

config forwarding
option dest 'lan'
option src 'vpn'

config forwarding
option dest 'wan'
option src 'vpn'

config forwarding
option dest 'vpn'
option src 'lan'

config rule
option target 'ACCEPT'
option src 'wan'
option proto 'udp'
option dest_port '1194'
option name 'OpenVPN'


/etc/config/openvpn

package openvpn

#################################################
# Sample OpenVPN 2.0 uci config for #
# multi-client server. #
#################################################

config openvpn server

# Set to 1 to enable this instance:
option enabled 1

option port 1194
option proto udp
option dev tun

option ca /etc/openvpn/ca.crt
option cert /etc/openvpn/server.crt
option crl_verify /etc/openvpn/crl.pem
option dh /etc/openvpn/dh512.pem
# These files should be kept secret:
option key /etc/openvpn/server.key
option tls_auth "/etc/openvpn/ta.key 0"

option duplicate_cn 1

option server "192.168.30.0 255.255.255.0"
option topology subnet
list push "topology subnet"
list push "redirect-gateway def1 bypass-dhcp"

list push "route 192.168.20.0 255.255.255.0"
list push "dhcp-option DNS 192.168.20.1"
list push "dhcp-option DOMAIN lan"

option client_to_client 1
option keepalive "10 120"
option comp_lzo yes
option persist_key 1
option persist_tun 1
option user nobody
option group nogroup

option status /tmp/openvpn-status.log
option log /tmp/openvpn.log
option verb 6
option mute 20

Contents of the /etc/openvpn directory:

root@tm02:/etc/openvpn# ls -al
drwxr-xr-x 2 root root 0 Mar 24 21:43 .
drwxr-xr-x 1 root root 0 Jan 27 20:34 ..
-rw-r--r-- 1 root root 1184 Mar 24 21:42 ca.crt
-rw-r--r-- 1 root root 479 Mar 24 21:42 crl.pem
-rw-r--r-- 1 root root 156 Mar 24 21:42 dh512.pem
-rw-r--r-- 1 root root 3395 Mar 24 21:42 server.crt
-rw------- 1 root root 522 Mar 24 21:42 server.key
-rw------- 1 root root 636 Mar 24 21:43 ta.key

OK... It's that time again ... to have another public talk about recent events..

Is it really ME, that seems to make people visiting here angry for some reason,
that they just don't want to come back?

It seems our latest visitor 985ach has decided to abandon this thread.

I've sent a PM to him mentioning the OpenWRT members post about the VPN settings that worked,
but even though I saw he read the PM, he hasn't replied to it, or here in the thread.

I truly have NO IDEA what I apparently did to deserve his hatred of me,
to the point he's not even replying anymore, to any of my communications,
when seemingly, just a few days earlier, everything seemed fine.

I never forced him to test the router, and even stated to him it's no rush to work on it, but ...
I'm getting the blame for something that I have no idea what he's mad at.

Well...I'm telling you all...I'm fed-UP with all this internet crap,
and everyone's mental hissy-fits against me..!

It's gotten to no longer be fun to stay here, ... and so...I'm leaving.

Maybe for a short while, but maybe forever...I don't know yet.
Because I'm sure, eventually...there will be another internet 'lunatic' with issues that get blamed on me.

I may even delete this entire thread...
so gather-up any info you like here, and save it to your own hard drives
or flash drives, or write it on your ass.
Because it may not be here for much longer.

I'm done...!!!

If anyone wants to make a comment about it...go ahead...maybe I'll read it.
If I even come back here at all.

Waaaaaaaaaaaaaaahoooooooooooooo! XD

[next day update]

Just doing some network cable runs this morning / today but I do have my HooToo here with me, I've also got my dd-wrt router here too (hopefully I'll have a power supply for it here too)

play times!

managed to finish copying all the configs over onto the hootoo today and changing the required to sui tmy network

I found somewhere in this part: cuase a problem loading pages in the LuCI GUI

but I removed these two enteries reboots and everything appears to be decent - doesn't appear to be a log file generated by openvpn (it was while the above two likes were still added)

now it just needs hooking up to the home network (hopefully it won't act as the gateway / dhcp server for eveything on the home network, it doesn't look like it would) then try connecting to it from an external source

still no reply on my chosen port, I know with another program that I've recently set up that another port I have gotten to work (but that was to my windows PC) so it could be my isp still blocking my original chosen port..

I may also give installing the luci open vpn app gui see if that gives me any addational options or visual indicators

So, I've now just installed luci-app-openvpn, logged onto the HooToo via web browser and LuCI GUI.

I now get a "Services" menu and OpenVPN under that - turns out I can't start the OpenVPN service and the service isn't starting so that's why my chosen port isn't open / responding boo

well, another update from me - still no luck getting the service to start :/
but I'm changing ISP's in a couple of weeks and as far as I can tell they don't block the default VPN ports.

So I'll put the configs as "default" from previous posts

some how...
no idea how
but

I've apparently completely ommitted the installation of openvpn and easy-rsa packages..

no idea how I've managed to do thsi but there we go...

I've got got my hootoo with me today so not able to do any package installs at the moment (damn proxy server) but I'll be correcting that tonight, then I'll set off building new keys too while i'm there (I kept them from my previous attempts)

right, so on my new ISP now - I do still have the windows VPN client setup and did the portforwarding but the default 1194 port still appears to be closed :/

At the moment I rebuilding all the keys as per the solution post, Once done I'll re-configure the my firewall and add my custom service port.

the BT HomeHub 5 already had some pre-configured VPN stuff so they must surely allow VPN's to be run.. I guess I could of screwed the windows VPN up in someway but hey - a full pc is a bit heavy power wise for the VPN compared to the HooToo..

I've still not worked out why the service isn't starting, I'm sort of hoping it's something to do with the keys...

but equally it could be todo with me clicking the "keep configs" curing upgrade but 600cc wrote

Yes. Force of habit; I couldn't be bothered with a factory restore and reconfiguring afterwards. Don't know if I should have done, but it doesn't appear to have broken anything.

so who knows there..

anyway the HomeHub 5 is so much better than the Sky Hub - I've un-synced the 5GHz and 2.4GHz radios - it makes more sence to me then you know which one you're on - the 2.4GHz has a much better range than the 5GHz all be it a bit slower - but both still reach further than the Sky Hub ever did

Anyway once I've built these key I can at least then move onto seeing if the service starts ^__^

o//

SUCCESS!

I've got the process started - regened all my key but in the end I think the service refused to start due to the following line in etc/config/openvpn I left it as dh512.pem but built a 2048 key ^_^

so - just need to set up my port forwarding then test

soo HooToo is plugged back into my network, IP config set and talking...
Portforwardign setup but chosen port still isn't listening but I did read that it won't do unless it receives the correct packet to activate it.

I'm getting a TLS key negotion failure on my OPVN windows client, Now I don't know if thats to do with client side, my works internet filtering or the VPNServer...
any way plodding on

I want to know if the T5740 PCI (32 bit) riser card can be used on the T5730 ?

I can't locate detailed pictures to compare both risers...

Thanks.

Dear!

I've made some upgrades in my HP T5735 terminal.

Bought a WiFi card and connect a pigtail and external antenna


Processor replacement 2x2.4GHz on board.


New cooling system was needed...


...with temperature controll


And additional holes for airflow.


Still too hot in enclosure.


And 64GB SSD in mSATA to IDE adapter.

985ach wrote:
...

Bad News 2, it looks like my BIOS battery has died on my original unit (still waiting for the second one to come) resulting in no display output or any response to the power button.. Grrr a quick Google too me to a HP forum where this was a resolution:

Yes, I found a solution after a lot of trial and error.

The reason these devices do not boot (which was true for all the ones I had to fix) is that the CMOS battery is drained. Unlike other computers, these thin clients don't simply boot up with a bad system date and show an error. They just don't run.

I bought new CR2032 batteries, opened the thin client, popped out the old battery and installed the new one and closed it back up.
The first time you power up, you'll see solid green lights again, but hold the power button for 10 seconds and make it shutdown.
Press the power button again and let it boot and it will give you a display, and show an error related to the BIOS settings having been reset. Hit f10? to get into the BIOS, set the correct date, arrange it to use the boot order you like, save and exit.

Your thin client should now be functional.

I've done that and changed my BIOS battery still no response from the power button for me and not LEDs light up on my USB keyboard, looks like it's died in some way unless I'm possibly missing something?

-ash

an old thread, I know, but maybe someone is still looking for the solution:

Check for 3.3 volts at L25 near power switch ( SW1 ), if not voltage available, replace U17 ( APW7120 ).

http://www.anpec.com.tw/ashx_prod_file. ... PW7120.pdf

For reference please see the picture at:

http://notebook1.ru/forma1/download/fil ... &mode=view

http://notebook1.ru/forma1/viewtopic.ph ... 04#p797904

Lex- wrote:

985ach wrote:
...

Bad News 2, it looks like my BIOS battery has died on my original unit (still waiting for the second one to come) resulting in no display output or any response to the power button.. Grrr a quick Google too me to a HP forum where this was a resolution:

Yes, I found a solution after a lot of trial and error.

The reason these devices do not boot (which was true for all the ones I had to fix) is that the CMOS battery is drained. Unlike other computers, these thin clients don't simply boot up with a bad system date and show an error. They just don't run.

I bought new CR2032 batteries, opened the thin client, popped out the old battery and installed the new one and closed it back up.
The first time you power up, you'll see solid green lights again, but hold the power button for 10 seconds and make it shutdown.
Press the power button again and let it boot and it will give you a display, and show an error related to the BIOS settings having been reset. Hit f10? to get into the BIOS, set the correct date, arrange it to use the boot order you like, save and exit.

Your thin client should now be functional.

I've done that and changed my BIOS battery still no response from the power button for me and not LEDs light up on my USB keyboard, looks like it's died in some way unless I'm possibly missing something?

-ash

an old thread, I know, but maybe someone is still looking for the solution:

Check for 3.3 volts at L25 near power switch ( SW1 ), if not voltage available, replace U17 ( APW7120 ).

http://www.anpec.com.tw/ashx_prod_file. ... PW7120.pdf

For reference please see the picture at:

http://notebook1.ru/forma1/download/fil ... &mode=view

http://notebook1.ru/forma1/viewtopic.ph ... 04#p797904

Very Userful to know! My original unit evded up scrapped since I figured is was dead dead my new unit is still going, just ordered myself a AMD TURION 64 X2 TL-60 TMDTL60HAX5DM (574) to replace my sempron ^_^ should be wiht me today

Lex- wrote:I want to know if the T5740 PCI (32 bit) riser card can be used on the T5730 ?

I can't locate detailed pictures to compare both risers...

Thanks.

I too am still looking out for that elusive pci-e riser card, I've a standard pci riser but decent pci (non express) graphics cards (at a decent price) are proving difficult to find too

This is just occured to me PCI to PCI-e adapter all being it more than what i'd like to spend at the moment: https://www.box.co.uk/StarTech.com_PCI_ ... oCMjXw_wcB

985ach wrote:soo HooToo is plugged back into my network, IP config set and talking...
Portforwardign setup but chosen port still isn't listening but I did read that it won't do unless it receives the correct packet to activate it.

I'm getting a TLS key negotion failure on my OPVN windows client, Now I don't know if thats to do with client side, my works internet filtering or the VPNServer...
any way plodding on

I've somewhat completely given up on getting my VPN working, I've still got my little hootoo device, it's just unplugged at present - maybe i'll look one day maybe not who knows!

Got my Turion 64 x2 TL-60 2GHz installed and running, stuck a small fan onto the cooler powering it from USB (I'm too lazy to solder ) Processor seems to idle at 32.3 Degrees C

I can now stream youtube videos without stuttering Quake Live won't run though so I just need to find me a PCI graphics card or a cheap PCI to PCI-E adapter, I've numerous PCI-E graphics cards I could use...

Desktop screenshot!
https://drive.google.com/open?id=0BwN0Z ... 2dURmo5cXM

This seems to the only place that isn't claiming they're out of stock for the HP PCI-E riser (GZ286AA) (on their website anyway)
http://shop.mcidiventi.co.uk/HP-GZ286AA ... nsion.html

Australia too apparently no international shipping
http://www.lmc.com.au/products/Notebook ... ion_Module

I'm with you on that one more rare than hen's teeth. By the way did you manage to get hold of an HP T5730 expansion module from LMC the company in your 4th April 2017 link.

wardy wrote:I'm with you on that one more rare than hen's teeth. By the way did you manage to get hold of an HP T5730 expansion module from LMC the company in your 4th April 2017 link.

I've not made any enquiries in all honesty, Wanted to see performance after CPU upgrade before taking the next step, I'm still toying with attempting to find a PCI graphics card and go that way.
http://www.ebay.co.uk/itm/zotac-fx5200- ... 2403751014


At the moment i'm getting random shutdowns when using a visualiser / youtube videos for a prolonged period which is a worry - nothing seems overly hot graphics / processor wise, I may need to up my Power supply which is rated at 12V 2A 24W

EDIT
I think this answer the Australian LMC question (though it is from 2015) don't know if the second poster is still selling http://www.phoneservicesupport.com/hp-t ... 13580.html

Also within this post http://www.phoneservicesupport.com/post85172.html#85172

Well higher (5.2a) amped power supply has stopped my random cut out which is a win, not trying to find the best bang for buck pci based graphics card, found a GeForce 8400gs 512mb card at a decent price, need to keep hunting though, the better card for cheaper the better xD

[edit 08-05-2017]
still havn't bothered witha graphics adapter yet been busy playing the beta of Quake Champions