Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - dj0qn

Pages: 1 ... 109 110 [111] 112 113 ... 123
1651
Alexander,

I am not sure if you have a bad problem somewhere, but make sure that the internal
IP number was not changed by the router's DHCP server to something else. That happens
from time to time if you have a power outage or similar, and didn't bind the MAC address
in the router to a fixed internal IP number. Use the Setup Manager to call up the IP number
to make sure.

73,
Mitch DJ0QN / K7DX

1652
General discussion forum / Re: New Hum Problem with 2.41
« on: 2011-07-20, 11:36:52 »
I have managed to replicate the problem myself.

I am on vacation and set-up a portable RRC with TS-480 head that uses the USB COM port for CAT control.
When I connect to the same station that my other user does, after about 2 minutes I get a loud buzz (not
really a hum). When I pull the USB cable out, it goes away. Strangely, this problem does not occur with the
other station that I also use, only with this particular one, which has otherwise identical settings and hardware.

73,
Mitch DJ0QN / K7DX

1653
Hi Felix,

No, the RRC boxes have never accepted anything other than DynDNS addresses from
DynDNS.org.

73,
Mitch DJ0QN / K7DX

1654
Hi John,

The short answer is NO.

The solution is to buy the PC Client dongle. It is very small, will give you a PTT button
and the virtual COM ports.

73,
Mitch DJ0QN / K7DX

1655
Hi John,

To bridge the two, you mark them with the control key and the right mouse click to
get the menu to bridge them. I have have very bad experience using XP in
this manner and have given up, since I get too many blue screens. Maybe you will
have better luck.

If you send me the type of bridge you are using, I can download the manual and see
if it is possible to switch to router mode.

That is why I always carry two different kinds of routers and bridges with me:

1) A Netgear WNCE2001: this is a pure bridge, like what you are describing. I use this
in the following manner:
  a) Access wireless networks with encryption, i.e. WPA or WEP. These networks generally
      are private and do not use a Radius server behind them.
  b) Access wireless networks with neither encryption, nor use a Radius server. This is somewhat
      rare here and usually is at private homes where the owner doesn't use encryption.

2) A Linksys WTR54GS: This is a router with ethernet and wireless "outputs", I use it for:
   a) Access wireless networks with no encryption, but do use a radius server. This covers
      most hot spots in the part of Europe I live in or in the case where you must "sign" an agreement.
      It allows you to pay once for the wireless connectivity, but use it among several users or devices.
   b) Access same as 1b above, but only when I want to offer my independent wireless network.

73,
Mitch DJ0QN / K7DX

1656
John,

The problem is likely that the bridge is allowing the device it connects with to use DHCP
to receive an IP number from the wireless router (Radius server). This device's MAC
address is entered into the Radius server. Switching to the RRC, which has a different MAC
address, causes it not to work.

You need to see if you can change the bridge to work in a different (router) mode that in
turn has its own DHCP server and only shows pulls one IP address from the Radius server.

73,
Mitch DJ0QN / K7DX

1657
John,

Did you first log on onto the service before you disconnected the bridge? Wireless networks
virtually always require you to confirm the terms and conditions on a web page, only after
that point are you given internet access. Connected it to the router alone doesn't work. The
reason is that your WLAN hardware's (in this case the bridge) MAC address is entered into a
table on the Radius server and is authorized access at that point.

73,
Mitch DJ0QN / K7DX

1658
John,

Did you first log on onto the service before you disconnected the bridge? Wireless networks
virtually always require you to confirm the terms and conditions on a web page, only after
that point are you given internet access. Connected it to the router alone doesn't work. The
reason is that your WLAN hardware's (in this case the bridge) MAC address is entered into a
table on the Radius server and is authorized access at that point.

73,
Mitch DJ0QN / K7DX

1659
General discussion forum / Re: New Hum Problem with 2.41
« on: 2011-07-15, 18:00:37 »
I received a more complete description from the user: When the USB cable is removed from the RRC,
the hum problem disappears and the head works as it should.

This appears to be very similar or identical to the problem introduced in firmware 2.35 and fixed in 2.36.
So much so, that I assume that the developers have made the same error they made with 2.35 when
USB CAT was first introduced.

73,
Mitch DJ0QN / K7DX






1660
Thanks, John, it was received this time and responded to. Must have got
caught by the spam gods the last time around.

73,
Mitch DJ0QN / K7DX

1661
John,

The 192.168.1.228 address is an internal address, and can not be reported by DynDNS.

Indeed, the DynDNS must report one single external IP address for ALL devices in your network.
These are separated within your network by using the port numbers. DynDNS doesn't know or care
about these numbers.

Again my offer; drop me a mail directly and I will send you a check list that will help you out.

73,
Mitch DJ0QN / K7DX

1662
Hi John,

It looks like you placed your router's IP address in the DMZ, but you need to put the RRC's address
in there.

Your router likely does not have SIP ALG if you can't turn it off. Otherwise, if you need some help,
let me know. I can send you a checklist I wrote for setting these up if you drop me a mail directly
(your e-mail address is unlisted) to dj0qn (at) arrl.net.

73,
Mitch DJ0QN / K7DX

1663
General discussion forum / Re: FSK
« on: 2011-07-13, 10:31:35 »
Now that the RemoteRig developers have done a great job of adding an FSK virtual serial
port to firmware 2.41, can someone please try it out and provide feedback on how it is working?

I am not a RTTY guy, but I am implementing the use of RemoteRig for an operation where RTTY
will be critical, so I need to know how well it works and any other tips that one can provide.

Thanks & 73,
Mitch DJ0QN / K7DX

1664
General discussion forum / New Hum Problem with 2.41
« on: 2011-07-13, 10:28:21 »
Just a heads-up: there is apparently a problem with firmware 2.41 that causes hum when the USB CAT is used.
This is the same or similar to the problem that occurred in firmware 2.35 and was fixed right away. See
http://www.remoterig.com/forum/index.php?topic=701.0 for that thread.

It is the same user that is having the problem. He is away today, but I will try to get more tests and details
from him before I leave on vacation this weekend. It appears so far to be identical to what he experienced
in 2.35, so he has downgraded to 2.39 for now until this is clarified or resolved.

73,
Mitch DJ0QN / K7DX

1665
Just change the DynDNS check interval to off, and that's it.

Actually, it is also completely harmless to let it continue to run, since it will never
make a change, anyway. So there is no rush to change it.

Do NOT enter anything in the external IP/host field! You don't need to enter your
external IP number on the radio side at all, but do so on the control side RRC in the
"SIP contact" field under the radio settings.

73,
Mitch DJ0QN / K7DX

Pages: 1 ... 109 110 [111] 112 113 ... 123