I think my ISP is blocking Magicjack
Moderators: Bill Smith, Pilot
I think my ISP is blocking Magicjack
I'm in the military stationed in Korea. I bought a Magicjack just before coming here and have used it for about 3 months now without a problem. Our ISP here is LG Dacom. Just before I got here they shut down access to Vonage, stating that they have a VOIP service that in comparable. Now I believe they are going after my beloved Magicjack (while not offering a comparable service). There has been talk on base of many people all of a sudden getting the error 3. I just started getting this error this morning and have been all day long.
Does anyone know how to find out if in fact our ISP is blocking the port(s) for Magicjack? And if they are, is there a workaround for it. I use this to stay in touch with my family and would like to continue using this. Any help would be appreciated.
SSgt Clifton Helpingstine
80 AMU Juvats
Kunsan AB, Korea
Does anyone know how to find out if in fact our ISP is blocking the port(s) for Magicjack? And if they are, is there a workaround for it. I use this to stay in touch with my family and would like to continue using this. Any help would be appreciated.
SSgt Clifton Helpingstine
80 AMU Juvats
Kunsan AB, Korea
- KatLuvr500
- MagicJack Newbie
- Posts: 6
- Joined: Wed Aug 13, 2008 7:58 pm
That's a very likely possibility. I read an article on clarkhoward.com about some of the ISP's activities with competitors, so you might take a look and see what's been going on. I won't mention VOIP competitor names, but you can read about it if you search VOIP. Good luck...I hope you'll be able to use your MagicJack! 
isp blocking Magic Jack
i to am in korea using magic jack and on friday i tried to use it and it gave me the same error 3 message im hoping to find a way to change ports or something to use so i can get around lg daecom if i get anything i will let you know and pls do the same for me
-
badkittykkr
- MagicJack Newbie
- Posts: 1
- Joined: Fri Aug 29, 2008 3:53 pm
how weird...im in california , i have comcast internet , and just this morning (after 3months of working fine) im getting the same error 3 code myself. tech support chat is a joke...they just read from the same troubleshooting faq... even if you tell them I DID ALL THIS ****** a few mintues ago with someone else, please dont tell me to do it again, but they do.
Run the test on this site to see if VoIP will work
http://www.testyourvoip.com/
http://www.testyourvoip.com/
-
stillsticky
- magicJack Apprentice
- Posts: 10
- Joined: Fri Mar 28, 2008 7:00 pm
- Location: Wilhoit,AZ
restarting over n over n over
Mines doing the same thing it worked good for a couple months , now it restarts itself over n over n over. I can't talk a minute before it drops my call.Tech support has told me so many different things to do all never worked.I think maybe Qwest is messing with me or the magicjack network needs help.This SUCKS!!

-
mozarthill
- MagicJack Newbie
- Posts: 3
- Joined: Sun Aug 31, 2008 9:29 am
MJ in Korea
I am at Humphreys and my MJ did not work all day yesterday (31 Aug) I was told that they were doing some upgrades, try back later. After midnight I gave up, went to bed. It is now early Monday morning, I rebooted everything and the MJ is working just fine. Give it another try. I have LG Dacom as my ISP too. Good luck.
LG daecom thieves
yeah i tried the VOIP test and i got really good scores but my magic jack still wont work im still getting the same error code 3 connect to the internet. i know there has to be a way around it and if someone knows please let me know
-
mozarthill
- MagicJack Newbie
- Posts: 3
- Joined: Sun Aug 31, 2008 9:29 am
ISP/LG Dacom
We just received a letter in the mail saying that LGDacom blocks the MJ as well as other VOIP connections. I have been trying to use mine again today (4 Sept.) and I can call stateside numbers but not any international (I call Italy and Germany). The customer service chat says the server is down (again!) and that I should try back in a couple of hours.
Does anyone in Korea know why LG Dacom can block MJ users on base, but if you live in the ville you can use MJ with no problems. It blocks anything that isn't provided by the LG concession on post. This is sanctioned by the USFK. I didn't live here when this ruling went through, anyone have any background?
Does anyone in Korea know why LG Dacom can block MJ users on base, but if you live in the ville you can use MJ with no problems. It blocks anything that isn't provided by the LG concession on post. This is sanctioned by the USFK. I didn't live here when this ruling went through, anyone have any background?
LG daecom
they are definately blocking the ports out to use magic jack it uses ports 520-583 somewhere in there and all those ports are closed so we cant use it i think there is a way around it but i havent figured it out yet
Re: LG daecom
I read somewhere you could create a Tunneling Network using IP6 protocol to some friends to act as a "forwarding" server between you and who you want to transfer data between.gomerusaf wrote:they are definately blocking the ports out to use magic jack it uses ports 520-583 somewhere in there and all those ports are closed so we cant use it i think there is a way around it but i havent figured it out yet
I'll have to look for the saved text file about it, but it works by the forwarding computer getting the command to send a file, and it forwards the command to the actual machine, and the data is sent to, or downloaded from the actual computer.
Data is Data, so it should also work , or have a way to make it, for the phone packet data to be forwarded.
a IP6 proxy server is used, as the "go-between" and it's free to join one, all the info is in that saved text file, if you're interested I'll look for it.
of course, the friends forwarding server would also have to be on, all the time... sounds like a good use for a Thin Client.
==EDIT==
I think the correct term for it is IPv6 ... I'm still looking for the text file regarding it.
yeah
i searched up a little bit on port tunneling and IPv6 and its all a little above my knowledge im sure its not that difficult i just dont understand the lingo exactly but if you could kinda dumb it down for me it sounds like it would work great and i would be much appreciateive
I'm still looking for the text file ... it's also over my tech-head ... and I thought I was a tech-geek too!
I know you had to start an account at one of the free IPv6 servers to get a IPv6 address, then the forwarders, or Bouncer server, as it's called, create a virtual connection to themselves but are really forwarding the commands to you, and the data is really going to the person you want to send the data-stream to, by connecting to the bouncer first, and it gets routed to you and you send and receive to them, not the bouncer.
but if the bouncer server goes down, so is the link to you.
I know you had to start an account at one of the free IPv6 servers to get a IPv6 address, then the forwarders, or Bouncer server, as it's called, create a virtual connection to themselves but are really forwarding the commands to you, and the data is really going to the person you want to send the data-stream to, by connecting to the bouncer first, and it gets routed to you and you send and receive to them, not the bouncer.
but if the bouncer server goes down, so is the link to you.
OK, I found something regarding someones FTP site, and how to do it with that, so maybe you or someone else on here can figure out how to do it for the magicjack data stream ... here's the text ... sit down, it's a long read .. 
you may be able to make the phone data look like an FTP file transfer
==========================================
--------------------------------------------------------------------------------
1) What is IPv6?
----------------
IPv6 is the new generation internet (Internet Protocol version 6).
A good starting point is:
http://www.ipv6.org/
Regular internet is called IPv4 (Internet Protocol version 4).
IPv4 to IPv6 transition is going on, sooner or later you'll face
this new internet
2) Why IPv6
-----------
IPv6, if properly used, allow to drill the wall built by a router NAT
(NAT = Network Address Translator) and let people access from regular internet to PCs with private IPs behind a router, usually invisible.
It will be possible to install servers where you cannot.
Examples are users like me ( I have a particular provider called fastweb), but this could apply in some cases to PC behind a router in some office,
depends on router configuration.
If you own a router and have troubles running a server, you'll need to
configure it - IPv6 would be only a further complication.
As a general rule, NAT must support protocol IP 41 to allow installation
of a server via IPv6.
Other common use of IPv6 is related to iRC, to access with many IPs
and similar things
3) Getting IPV6
---------------
IPv6 ed IPv4 (that's usual internet) are two separate worlds, but
they can live together on same PC.
Servers are running around to connect the two worlds, waiting IPv6
is directly supported by ISP.
IPv6 packets can be embedded in regular IPv4 packets, we'll have
a IPv6 tunnel in that case.
You need to register to a service translating IPv4 in IPv6 (this is a
Tunnel Broker server o TB).
Some cool people installed a couple of them inside my provider
network, allowing me to do the trick:
http://fast6.fastwebnet.org/index.php
http://www.sideralis.net/
of course there are many public free services around, few examples:
http://tb.ngnet.it/ (Italy - only telecom italy users)
http://www.ipv6.edisontel.it/ (Italy)
http://tunnelbroker.as8758.net/ (Switzerland)
http://tunnelbroker.net/ (USA - California)
http://www.join.uni-muenster.de/welcome-e.html (Germany)
https://tb.ipv6.btexact.com/ (England - info http://www.uk6x.com/TB_Howto/index.html)
http://www.v6.eu.ntt.net/ (England)
http://www.freenet6.net/ (Canada)
http://www.ipng.nl/ (Holland)
http://www.6b0ne.hu/ (Hungary)
http://tbroker.manis.net.my/ (Malaysia)
http://tb.ipv6.ascc.net/ (Taiwan)
Registration to a TB is required for BOTH client and server.
You'll be provided with a group of IPv6 addresses wich can be used
on your machine for any purpose.
4) Keep your data updated on TB
-------------------------------
If your IP (IPv4) changes, you must update your info on TB service,
informing it the packets IPv6 will change destination IP.
Usually you can do that on TB maintenance page and update
your IPv4 there.
Users with dynamic IP need to update data each time they change IP,
unless the TB provide some service to solve the problem.
5) Setting up your PC
---------------------
The protocol TCP/IP is worldwide installed on any PC, you must put
beside IPv6 protocol too:
- Windows XP
using command Prompt:
ipv6 Install (THIS COMMAND MUST BE USED ONLY ONE TIME)
- Windows 2000
download the IPv6 Technology Preview W2K SP4 IE6 (or the preview
related to another SP) and install
(http://www.sixxs.net/archive/windows/)
No matter wich windows version you own, go to Network and Dial-up
connections, select Local Area Connection properties, and install the
new Microsoft IPv6 protocol available.
- linux
You should check if your distribution is IPv6 ready. All modern
distributions bring IPv6 support, you can easily load it when in root:
modprobe ipv6
you can check if the IPv6 installation module is good checking the
loaded module list:
example root # lsmod | grep ipv6
ipv6 159892 -1
It that shows you are OK. Eventually, if you need a kernel
recompilation to implement the IPv6 support you must check
the kernel howto.
6) Setting up IPv6
------------------
After TB registration is done, a couple of configuration script lines
will be provided, you can execute them from DOS command prompt
or write them in a .bat file. The same lines could be used
directly by a bouncer like talpa6, wich allows IPv6 configuring too.
Usually, for W2K e XP using command prompt you'll see something like:
ipv6 rtu ::/0 2/::xxx.xxx.xxx.xxx pub
notice in the string a IPv4 is used (xxx.xxx.xxx.xxx) , this is the TB IPv4.
ipv6 adu 2/xxxxxxxxxxxxxxxxx
in place of xxxxxxxxxxxx your IPv6 should be used.
Linux users will see instead a script like this (IP are same above):
#!/bin/sh -e
TN=myname
REMOTE=xxx.xxx.xxx.xxx
LOCAL6=xxxxxxxxxxxxxxxxxx
ip tunnel add $TN mode sit remote $REMOTE
ip link set $TN up
ip route add 2000::/3 via fe80::$REMOTE dev $TN
ip addr add $LOCAL6 dev eth0
Important: the .bat file or the script must run while every PC boot.
7) Setting up a firewall for IPv6
--------------------------------
Waiting to find a firewall IPv6 compatible, we must live with present
firewalls with IPv6.
WinXP and SP1 owners:
shut down the IPv6 firewall, otherwise you can try to configure it. Info:
http://www.microsoft.com/technet/treevi ... fgv601.asp
Windows and ZoneAlarm 3, setting up:
Go to Firewall-Main and choose Advanced; in General settings, check
option "Allow uncommon protocols at high security".
This will allow to IPv6 protocol IPv6 to pass the firewall (not a great
setup must admit).
Windows and ZoneAlarm 4 setting up:
In the Firewall page there is a Expert tab. Click Add and you'll see a form.
setup Rank -> 1, State -> enabled, Action -> allow, Name and Description
anything you like; in Source click Modify-Add Location-IP Address;
description anything you like and in IP write the Tunnel Broker address
used; again, Modify-Add Location-My Computer.
Go to Protocol Modify-Add Protocol-Add Protocol; in the form choose
Protocol -> custom, Description anything you like, Name -> other and in
Protocol Number type 41. All other setting being left default.
This way in Firewall-Main-Advanced the option "Allow uncommon protocols
at high security" is not necessary.
Test
-------
Using command prompt:
ping6 http://www.kame.net/
must see positive answers.
Connect to site:
http://www.ipv6.org/
and check your IP looks like this:
xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
9) Using FTP protocol and IPv6
------------------------------
If both the FTP server and FTP client are IPv6 compatible, no problems
and no settings are necessary, the protocol FTP6 will be used (this is a
evolution of usual FTP for IPv4).
Looking for a client FTP, SmartFTP supports IPv6 from version 1.0
Build 978 (www.smartftp.com), while a FTP server available is Pure-FTPd
(http://www.pureftpd.org).
The BIG problem about FTP6 is the fact that both FTP control connection
and data connection pass through the TB of client user and the TB of
server user, and the speed will be low in 99% of cases.
To solve this problem
, it's better to use IPv6 tunnel ONLY with the
FTP control connection, letting data and downloads/uploads follow the
normal path IPv4. If the FTP server is used ONLY in active mode
(command PORT to open transfers), all data connections will be
outgoing for the server, so they'll reach the client through every NAT
without problems.
Of course passive mode could be used, but only the low bandwidth
of TB will be used.
At this point we can use the normal IPv4 applications we use all days
(flash, raiden, etc), only we must pipe the FTP IPv4 commands in
the IPv6 tunnel. We can do that using a bouncer IPv4/IPv6:
for Windows: relay6 (http://www.sideralis.net/programmi/relay6.zip)
for linux: 6tunnel (http://www.sideralis.net/download/6tunnel-0.09.tar.gz)
for win/linux: talpa6 (http://unboffable.hn.org/unboffable.talpa6/)
Many others around of course. Good for windows to use talpa6, it can
run as a windows service and allow to use the configuration lines provided
by TB for IPv6 (see point 6).
This way you need to configure only one application.
I don't know at moment of a unique application doing the same in linux.
The bouncer must be installed both on client side (tunnel entrance) and
server side (tunnel exit), only the configuration will differ.
To avoid ALL client FTP users installing IPV6, registering a Tunnel Broker
and running a bouncer, a third PC could be used, well IPv6 configured,
with a regular IPv4 and even a slow connection, and use it as the only
bouncer PC for the server.
To this bouncer bouncer PC will connect all clients FTP IPv4, and they
won't need to configure anything. If the client is allowed to connect to
the bouncer through port 21, even the users behind a router will connect
without problems. This is the main reason I'd like to see at least
one. A important fact must be understood: every client user running
IPv6/bouncer could be used as a bouncer machine for other client users,
if they are allowed to connect.
Some examples with relay6 (others programs are similar):
relay6 to execute on FTP server PC command prompt:
relay6 nnnnn xxx.xxx.xxx.xxx mmmmm /b:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
nnnnn is the listening port IPv6 (tunnel port)
xxx.xxx.xxx.xxx is the IPv4 internal address of PC server FTP
mmmmm is the listening port of FTP server
xxxx:xxxx:xxxx:xxxx:xxx:xxxx:xxxx:xxxx is the IPv6 address of PC
server FTP
relay6 to execute on PC client FTP / third PC bouncer (command prompt):
relay6 ppppp xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx nnnnn /b:yyy.yyy.yyy.yyy
ppppp is the port the client must use to connect to a server FTP
xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx is the IPV6 address of PC
server FTP, SAME AS ABOVE
nnnnn is the port IPv6 (tunnel port), SAME AS ABOVE
yyy.yyy.yyy.yyy is the IPv4 of client / bouncer PC
To connect to the server client should use: yyy.yyy.yyy.yyy:ppppp
If a dedicated PC bouncer is not used, actually the FTP client will connect
to himself, to its IP (yyy.yyy.yyy.yyy) using the port ppppp. In this case
instead of yyy.yyy.yyy.yyy the lookup address 127.0.0.1 could be used.
10) Bouncer configuration for my server
---------------------------------------
(for example ... if ...)
The address IPv6 of my server is: 3021
9:1e8::1
server port (tunnel): 50121
the setup for a client / bouncer PC are:
relay6:
relay6 21 3021
9:1e8::1 50121 /b:yyy.yyy.yyy.yyy
yyy.yyy.yyy.yyy is the IPv4 of client / bouncer PC
in this case I used port 21, you can choose the port you like to avoid
conflicts.
The user can conenct to my site using:
yyy.yyy.yyy.yyy:21
it's important to use port 21 if you want to use your PC as bouncer
for other users.
talpa6 (file unboffable.talpa6.conf):
yyy.yyy.yyy.yyy 21 3021
9:1e8::1 50121
same considerations as above.
--------------------------------------------------------------------------------
=============================================
you may be able to make the phone data look like an FTP file transfer
==========================================
--------------------------------------------------------------------------------
1) What is IPv6?
----------------
IPv6 is the new generation internet (Internet Protocol version 6).
A good starting point is:
http://www.ipv6.org/
Regular internet is called IPv4 (Internet Protocol version 4).
IPv4 to IPv6 transition is going on, sooner or later you'll face
this new internet
2) Why IPv6
-----------
IPv6, if properly used, allow to drill the wall built by a router NAT
(NAT = Network Address Translator) and let people access from regular internet to PCs with private IPs behind a router, usually invisible.
It will be possible to install servers where you cannot.
Examples are users like me ( I have a particular provider called fastweb), but this could apply in some cases to PC behind a router in some office,
depends on router configuration.
If you own a router and have troubles running a server, you'll need to
configure it - IPv6 would be only a further complication.
As a general rule, NAT must support protocol IP 41 to allow installation
of a server via IPv6.
Other common use of IPv6 is related to iRC, to access with many IPs
and similar things
3) Getting IPV6
---------------
IPv6 ed IPv4 (that's usual internet) are two separate worlds, but
they can live together on same PC.
Servers are running around to connect the two worlds, waiting IPv6
is directly supported by ISP.
IPv6 packets can be embedded in regular IPv4 packets, we'll have
a IPv6 tunnel in that case.
You need to register to a service translating IPv4 in IPv6 (this is a
Tunnel Broker server o TB).
Some cool people installed a couple of them inside my provider
network, allowing me to do the trick:
http://fast6.fastwebnet.org/index.php
http://www.sideralis.net/
of course there are many public free services around, few examples:
http://tb.ngnet.it/ (Italy - only telecom italy users)
http://www.ipv6.edisontel.it/ (Italy)
http://tunnelbroker.as8758.net/ (Switzerland)
http://tunnelbroker.net/ (USA - California)
http://www.join.uni-muenster.de/welcome-e.html (Germany)
https://tb.ipv6.btexact.com/ (England - info http://www.uk6x.com/TB_Howto/index.html)
http://www.v6.eu.ntt.net/ (England)
http://www.freenet6.net/ (Canada)
http://www.ipng.nl/ (Holland)
http://www.6b0ne.hu/ (Hungary)
http://tbroker.manis.net.my/ (Malaysia)
http://tb.ipv6.ascc.net/ (Taiwan)
Registration to a TB is required for BOTH client and server.
You'll be provided with a group of IPv6 addresses wich can be used
on your machine for any purpose.
4) Keep your data updated on TB
-------------------------------
If your IP (IPv4) changes, you must update your info on TB service,
informing it the packets IPv6 will change destination IP.
Usually you can do that on TB maintenance page and update
your IPv4 there.
Users with dynamic IP need to update data each time they change IP,
unless the TB provide some service to solve the problem.
5) Setting up your PC
---------------------
The protocol TCP/IP is worldwide installed on any PC, you must put
beside IPv6 protocol too:
- Windows XP
using command Prompt:
ipv6 Install (THIS COMMAND MUST BE USED ONLY ONE TIME)
- Windows 2000
download the IPv6 Technology Preview W2K SP4 IE6 (or the preview
related to another SP) and install
(http://www.sixxs.net/archive/windows/)
No matter wich windows version you own, go to Network and Dial-up
connections, select Local Area Connection properties, and install the
new Microsoft IPv6 protocol available.
- linux
You should check if your distribution is IPv6 ready. All modern
distributions bring IPv6 support, you can easily load it when in root:
modprobe ipv6
you can check if the IPv6 installation module is good checking the
loaded module list:
example root # lsmod | grep ipv6
ipv6 159892 -1
It that shows you are OK. Eventually, if you need a kernel
recompilation to implement the IPv6 support you must check
the kernel howto.
6) Setting up IPv6
------------------
After TB registration is done, a couple of configuration script lines
will be provided, you can execute them from DOS command prompt
or write them in a .bat file. The same lines could be used
directly by a bouncer like talpa6, wich allows IPv6 configuring too.
Usually, for W2K e XP using command prompt you'll see something like:
ipv6 rtu ::/0 2/::xxx.xxx.xxx.xxx pub
notice in the string a IPv4 is used (xxx.xxx.xxx.xxx) , this is the TB IPv4.
ipv6 adu 2/xxxxxxxxxxxxxxxxx
in place of xxxxxxxxxxxx your IPv6 should be used.
Linux users will see instead a script like this (IP are same above):
#!/bin/sh -e
TN=myname
REMOTE=xxx.xxx.xxx.xxx
LOCAL6=xxxxxxxxxxxxxxxxxx
ip tunnel add $TN mode sit remote $REMOTE
ip link set $TN up
ip route add 2000::/3 via fe80::$REMOTE dev $TN
ip addr add $LOCAL6 dev eth0
Important: the .bat file or the script must run while every PC boot.
7) Setting up a firewall for IPv6
--------------------------------
Waiting to find a firewall IPv6 compatible, we must live with present
firewalls with IPv6.
WinXP and SP1 owners:
shut down the IPv6 firewall, otherwise you can try to configure it. Info:
http://www.microsoft.com/technet/treevi ... fgv601.asp
Windows and ZoneAlarm 3, setting up:
Go to Firewall-Main and choose Advanced; in General settings, check
option "Allow uncommon protocols at high security".
This will allow to IPv6 protocol IPv6 to pass the firewall (not a great
setup must admit).
Windows and ZoneAlarm 4 setting up:
In the Firewall page there is a Expert tab. Click Add and you'll see a form.
setup Rank -> 1, State -> enabled, Action -> allow, Name and Description
anything you like; in Source click Modify-Add Location-IP Address;
description anything you like and in IP write the Tunnel Broker address
used; again, Modify-Add Location-My Computer.
Go to Protocol Modify-Add Protocol-Add Protocol; in the form choose
Protocol -> custom, Description anything you like, Name -> other and in
Protocol Number type 41. All other setting being left default.
This way in Firewall-Main-Advanced the option "Allow uncommon protocols
at high security" is not necessary.
-------
Using command prompt:
ping6 http://www.kame.net/
must see positive answers.
Connect to site:
http://www.ipv6.org/
and check your IP looks like this:
xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
9) Using FTP protocol and IPv6
------------------------------
If both the FTP server and FTP client are IPv6 compatible, no problems
and no settings are necessary, the protocol FTP6 will be used (this is a
evolution of usual FTP for IPv4).
Looking for a client FTP, SmartFTP supports IPv6 from version 1.0
Build 978 (www.smartftp.com), while a FTP server available is Pure-FTPd
(http://www.pureftpd.org).
The BIG problem about FTP6 is the fact that both FTP control connection
and data connection pass through the TB of client user and the TB of
server user, and the speed will be low in 99% of cases.
To solve this problem
FTP control connection, letting data and downloads/uploads follow the
normal path IPv4. If the FTP server is used ONLY in active mode
(command PORT to open transfers), all data connections will be
outgoing for the server, so they'll reach the client through every NAT
without problems.
Of course passive mode could be used, but only the low bandwidth
of TB will be used.
At this point we can use the normal IPv4 applications we use all days
(flash, raiden, etc), only we must pipe the FTP IPv4 commands in
the IPv6 tunnel. We can do that using a bouncer IPv4/IPv6:
for Windows: relay6 (http://www.sideralis.net/programmi/relay6.zip)
for linux: 6tunnel (http://www.sideralis.net/download/6tunnel-0.09.tar.gz)
for win/linux: talpa6 (http://unboffable.hn.org/unboffable.talpa6/)
Many others around of course. Good for windows to use talpa6, it can
run as a windows service and allow to use the configuration lines provided
by TB for IPv6 (see point 6).
This way you need to configure only one application.
I don't know at moment of a unique application doing the same in linux.
The bouncer must be installed both on client side (tunnel entrance) and
server side (tunnel exit), only the configuration will differ.
To avoid ALL client FTP users installing IPV6, registering a Tunnel Broker
and running a bouncer, a third PC could be used, well IPv6 configured,
with a regular IPv4 and even a slow connection, and use it as the only
bouncer PC for the server.
To this bouncer bouncer PC will connect all clients FTP IPv4, and they
won't need to configure anything. If the client is allowed to connect to
the bouncer through port 21, even the users behind a router will connect
without problems. This is the main reason I'd like to see at least
one. A important fact must be understood: every client user running
IPv6/bouncer could be used as a bouncer machine for other client users,
if they are allowed to connect.
Some examples with relay6 (others programs are similar):
relay6 to execute on FTP server PC command prompt:
relay6 nnnnn xxx.xxx.xxx.xxx mmmmm /b:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx
nnnnn is the listening port IPv6 (tunnel port)
xxx.xxx.xxx.xxx is the IPv4 internal address of PC server FTP
mmmmm is the listening port of FTP server
xxxx:xxxx:xxxx:xxxx:xxx:xxxx:xxxx:xxxx is the IPv6 address of PC
server FTP
relay6 to execute on PC client FTP / third PC bouncer (command prompt):
relay6 ppppp xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx nnnnn /b:yyy.yyy.yyy.yyy
ppppp is the port the client must use to connect to a server FTP
xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx:xxxx is the IPV6 address of PC
server FTP, SAME AS ABOVE
nnnnn is the port IPv6 (tunnel port), SAME AS ABOVE
yyy.yyy.yyy.yyy is the IPv4 of client / bouncer PC
To connect to the server client should use: yyy.yyy.yyy.yyy:ppppp
If a dedicated PC bouncer is not used, actually the FTP client will connect
to himself, to its IP (yyy.yyy.yyy.yyy) using the port ppppp. In this case
instead of yyy.yyy.yyy.yyy the lookup address 127.0.0.1 could be used.
10) Bouncer configuration for my server
---------------------------------------
(for example ... if ...)
The address IPv6 of my server is: 3021
server port (tunnel): 50121
the setup for a client / bouncer PC are:
relay6:
relay6 21 3021
yyy.yyy.yyy.yyy is the IPv4 of client / bouncer PC
in this case I used port 21, you can choose the port you like to avoid
conflicts.
The user can conenct to my site using:
yyy.yyy.yyy.yyy:21
it's important to use port 21 if you want to use your PC as bouncer
for other users.
talpa6 (file unboffable.talpa6.conf):
yyy.yyy.yyy.yyy 21 3021
same considerations as above.
--------------------------------------------------------------------------------
=============================================
gomerusaf wrote:lol there has to be a way to dumb that down like hey download this install it and then go to this website for an ip adress lol i just wanna make phone calls
this WAS the dumb'd down version.
It's possible that by now a simple install and setup is out, this was made 2003 ... try google, and see what comes up... or find a geek in your area, and pick his, or her, brains.
This is the link to the docs page of Putty .... http://the.earth.li/~sgtatham/putty/0.60/htmldoc/
just looking at the LONG "Table of Contents" made me fart hot gas out my wazzoo ...
you have to be kidding me, that the IPv6 post I put, of the text explaining it, is too much to understand or read.
Good luck with Putty!

just looking at the LONG "Table of Contents" made me fart hot gas out my wazzoo ...
you have to be kidding me, that the IPv6 post I put, of the text explaining it, is too much to understand or read.
Good luck with Putty!
Last edited by momo on Sun Sep 07, 2008 11:52 pm, edited 1 time in total.
lol
yeah im not that computer savy i tried to read it and figure it out but i didnt understand half of the stuff it was telling me so when trying to research it more putty seemd to be easy if you can find out the information for magicjack like the ip it tries to connect to and everything all you do is insert that into putty and it just re routes it for you to the port you specify i just dont know how to get the information for magic jack
Re: lol
If Putty IS as easy as all that, then it does seem like the better route, but if it was so easy to setup, why such a large Table of Contents?gomerusaf wrote:yeah im not that computer savy i tried to read it and figure it out but i didnt understand half of the stuff it was telling me so when trying to research it more putty seemd to be easy if you can find out the information for magicjack like the ip it tries to connect to and everything all you do is insert that into putty and it just re routes it for you to the port you specify i just dont know how to get the information for magic jack
is there a Wizard that comes up to do it all for you, if not, you'll still need that skinny - pimple faced - pencil neck geek around your area to help with either one... but I DO KNOW the IPv6 works well for routers that aren't under your control to "Tunnel" through their blocks.
IPv6
yeah i wish i could figure out how to use the IPv6 stuff i just dont understand what it is is ipv6 a program that you use? do you download it and then just connect to those random servers ? i mean it has to be really dummied down i just want to use whatever will work to allow me to use my magic jack
Re: IPv6
if you use XP it's already built-in (as the beginning of the text shows) you enter the command prompt , and type the command IPv6 installgomerusaf wrote:yeah i wish i could figure out how to use the IPv6 stuff i just dont understand what it is is ipv6 a program that you use? do you download it and then just connect to those random servers ? i mean it has to be really dummied down i just want to use whatever will work to allow me to use my magic jack
BUT, if you don't know how to get to the command prompt ... I'd say ... make friends with a computer geek... they're out there, you've probably passed them in the street, but being YOU're cooler than they are, you may have not noticed them.
also, DON'T do anything to your OS until you've made an IMAGE backup of the "C" drive... so you can restore the OS from where you left off BEFORE the changes.
(OS is Operating System) in case you're REALLY a newbie to all this.
Re: lol
me thinks you looked at the IPv6 text post and farted hot gas out YOUR wazzoo too!gomerusaf wrote:im not that new i didnt think it was as easy as just going to command prompt and doing that once thats done do i just connect to the other free servers
and maybe didn't even start to read it .. yes?
yeah, it's not that complicated once you have all the info straight in your mind...
and YES it is that easy... you setup an account on the free IPv6 proxy server, then you get that info to put into the IPv6 setup on your, and the bouncers systems, and then others, or even the bouncers, can talk to you, via the bouncer servers, and you can have multi servers to bounce, like having other phone card numbers to dial out from.
from what I understand about it ... the connection is directed to the bouncer server which forwards the request to get or send data to you, then the data starts to flow to YOU and the party connecting to the bouncers server, but NO data goes through the bouncer, just the commands to send/receive to/from you. ... so... even when YOU want to call someone, YOU also go through the bouncer to place the request, *I think*
that's why I suggested to make an Image of your "C" drivegomerusaf wrote:yeah i read it i think i kind of have a little bit of a grasp on it but im to scared of f-ing something up
(making an Image is backing it up in case you make a mistake with something it can be restored to it's original pre-screwup state)
I use an old program called, Drive Image 2002 (version 6) before Symantec took over the company...
it makes an exact copy of any partition, or entire drive with multi partitions, to another drive, or other media, for safety.
when it's restored, it puts back the drives original partition state, with all the partitions special info, and can also copy one drive to another in one step if needed.
There's also partition magic, and boot magic, that let you manipulate partitions as easy as files... and create multi bootable partitions, along with the boot magic program to choose which partition to boot into, allowing you to create several OS bootable partitions on one drive, to work on the same computer.
very nice program, but it you have a RAID setup, you'll need the newer Drive Image v9 at least... and the other updates, I think it's at v13 now, maybe higher, ... the newer ones work with network connected drives, and the newer controllers and HD types.