I've been playing for hours and I can't get port forwarding to work on my
Conexant (Dabs value) 4 port adsl modem/router.

The documentation I've read implies it works and with the latest firmware
version from Amigo's web site (CA6XR-GN.0924.00T)
the gui has all the right controls to set it up. I've mapped the ports on
the Virtual Server page to the local IP address.

I'm trying to enable web and telnet traffic into a local Unix server. From
the LAN I'm able to access both services OK, but if I use the public WAN
address it appears that the router is not forwarding the traffic onto the
LAN.

Has anyone with this router managed to get port forwarding to work?

Thanks,

Graham.



-------------------------------------
Graham Russell Photography
www.grahamrussell.info

Graham Russell wrote:

You know you won't be able to access your lan via the internet from
behind your router unless you use a proxy server , or alternatively use
a dial-up modem.

Does SGI and REX mean anything?

"Bat Guano" <bat.guano@talk21dotcom> wrote in message
news:vouaem7thac49c@corp.supernews.com...
Wow, they certainly do. I've left the router with virtual server turned off
and dmz pointing at the internal server.

I'm a bit new to this advanced networking stuff. Any pointers to setting up
the proxy server you mentioned? You've obviously managed to get into my
router externally - how did you do this? telnet? ftp?

Graham.

On Fri, 17 Oct 2003 06:59:04 +0100, "Graham Russell"
<graham-russell@dsl.pipex.com> wrote:

settings. Change your admin passwords as well.
--
Andrew. To email unscramble nrc@gurjevgrzrboivbhf.pbz & remove spamtrap.
Help make Usenet a better place: English is read downwards,
please don't top post. Trim messages to quote only relevent text.
Check groups.google.com before asking a question.

"Graham Russell" <graham-russell@dsl.pipex.com> wrote in message news:<3f8f252f$0$6621$cc9e4d1f@news.dial.pipex.com >...
Hi Graham

If its the same as the origo you will need to do a power down /up
after saving/rebooting, to check it use http://www.guardster.com/ to
check its working. I had a similar trouble till I did the above.

Ian Plain

www.bathford-broadband.co.uk

Graham Russell wrote:
I just typed http://nnn.nnn.nnn.nnn into my browser bar - I got the
address from the headers on your post. I think you've got the port
forwarding working ok, but you need to use a proxy to be able to test it
from your network - to be able to go out on the internet and back again.
Someone else mentioned http://www.guardster.com/ or you could use a
different account (like I did).

I have!

See this site for setup info if you haven't already:
http://www.cazart.plus.com/conexant/

Having done the setup, I got the port forwarding to work via the Virtual
Server page of the config. The only thing I need port forwarding for is so
that DCC will work on IRC. And it does, after I put the correct ports onto
the Virtual Server page.

Hope that helps......

--
Buffy : I told you. I said end of the world and you¹re like 'poo-poo southern
California, poo-poo!'
Giles : I¹m so very sorry. My contrition completely dwarfs the impending
apocalypse.

So...
How is port forwarding set on the Virtual Server page?

Here is my guess, (but I'd appreciate confirmation before I destroy my
connection!).

ID Public Port Private Port Port Type Host IP Address
1 6881 6881 TCP 10.0.0.8
2 6882 6882 TCP 10.0.0.8
etc.

Is this anywhere close to being right?

Any help most gratefully received.

Nemo


Jocelyn Lavin wrote:

On Mon, 20 Oct 2003 00:34:10 +0100, Nemo <here@there.everywhere>
wrote:

remember that you have to save the changes which reboots the router so
they take effect.
--
Andrew. To email unscramble nrc@gurjevgrzrboivbhf.pbz & remove spamtrap.
Help make Usenet a better place: English is read downwards,
please don't top post. Trim messages to quote only relevent text.
Check groups.google.com before asking a question.

Andrew wrote:
To satisfy your curiosity (spelling??), I've started using BitTorrent
and port forwarding has been recommended if you're behind a router.

I'll wait until the curent downloads are completed before I try it.

To: Jocelyn
Does the above look about right to you (in order to pert forward)?

On Mon, 20 Oct 2003 20:41:21 +0100, Nemo <here@there.everywhere>
wrote:

port forwarding and it seems to be working just fine.
--
Andrew. To email unscramble nrc@gurjevgrzrboivbhf.pbz & remove spamtrap.
Help make Usenet a better place: English is read downwards,
please don't top post. Trim messages to quote only relevent text.
Check groups.google.com before asking a question.

On Mon, 20 Oct 2003 20:41:21 +0100, Nemo wrote
(in message <iUWkb.13571$kA.3456075@wards.force9.net>):
Well, I am not an expert... I had help when I did mine :-)

But I *can* tell you two things.

1. Mine says this:

ID Public Port Private Port Port Type Host IP Address
1 32768 32768 TCP 10.0.0.14

(32768 is the port on which I do DCC via IRC)

(Apparently 10.0.0.14 is the "public WAN IP address" of my airport (wireless)
base station. I put that in the VS settings because I was told to. The only
link I can see with any other part of the router config is on the LAN config
page, where it says IP address (of the router, I think) = 10.0.0.2, DHCP
server is ON (contrary to what that website says), DHCP address pool
selection = user defined, start address = 10.0.0.3, end address = 10.0.0.14)

(Again I can't remember why these numbers are there - I was just following
instructions from someone who knew far more about it than me!)



2. I run BitTorrent through this router (and behind the Mac OS X firewall),
but I have *not* enabled the BitTorrent ports (6881 etc.) on the Virtual
Server config page. This is because BitTorrent worked before it occurred to
me it might not :-)


Hope this helps. If not, ask again and I'll ask my networking guru (who is
helpfully offline right now!)


--
Buffy : I told you. I said end of the world and you¹re like 'poo-poo southern
California, poo-poo!'
Giles : I¹m so very sorry. My contrition completely dwarfs the impending
apocalypse.

Jocelyn Lavin wrote:
For those still interested, at first I wasn't going to port forward, due
to Jocelyn and Andrew's eminently sensible remarks (and my own innate
cowardice).

But then I had a torrent that was sluggish if not entirely dead.
So I did the port forwarding, and lo, it sprang to life!

I can now see why.

I use Azureus as a Bittorrent client, which shows you lots of the inner
workings, which is nice.

One thing is shows is whether you have connected to them, which is
local, or whether they have connected to you, which is remote.

Before port forwarding, all my connections were local, (and were few, if
not entirely, non-existent on this particular torrent).

After port forwarding, most of my connections were remote, as now they
could get through my router. Hurrah!

This is as predicted in the Bittorrent FAQ at
http://www.dessent.net/btfaq/
(tho' currently offline)

Another case of RTFM...

On Fri, 24 Oct 2003 18:50:11 +0100, Nemo <here@there.everywhere>
wrote:

use the normal Bittorent client via NAT and it is currently
downloading the Silent Hill 3 demo just fine at 17K download and 27K
upload. I have had downloads faster than that before now too. Maybe
its an issue with the client that you use.
--
Andrew. To email unscramble nrc@gurjevgrzrboivbhf.pbz & remove spamtrap.
Help make Usenet a better place: English is read downwards,
please don't top post. Trim messages to quote only relevent text.
Check groups.google.com before asking a question.

Well, I read this, and thought "good grief, you mean I could have had faster
connections all this time?!?" So I set up the port forwarding, mentally
composing my "I am SO stupid!" post.

Sadly it has made no difference whatsoever - in fact, if anything, the
transfers are SLOWER. Although that is undoubtedly just down to the
constantly changing BitTorrent environment.

Oh well :-)

--
Neo : So we need machines and they need us, is that your point, Councillor?
Councillor Harmann : No. No point. Old men like me don't bother making
points. There's no point.