BGW320-500.  Has anyone gotten Port Forwarding to work?

?seriously?

you said--->Did humans design this thing?

Unfortunately, most times the SW/Firmware was written by someone living in China, who speaks English as a second language.

-------------------> And the above statement was modified several times to make it safe for all, and as non-derogatory as possible, believe it or not

> I finally get my devices to be allocated to the desired ipaddr via the BGW320, by using the IP Allocate, after dhcp assigns it to some wayout address, all addresses are above 192.168.100. 

The RG is purposely designed to assign addresses above a certain number so that users with manually configured (statically addressed) LAN devices are instructed to use addresses below that number. This is information not often communicated well. You can easily change this by assigning a different range for the RG's DHCP server.

@markbnj   And yet you still failed at that task.  🙄

I wholeheartedly agree tonydi

My pent-up frustration of cable/fiber modems as contracted with large companies, whose engineers do NOT take the end-users into consideration goes back as far as docsis 1.0 in 1995! 

So call me a long time Q##@ user of these required devices.

> The I go to the stupid NAT/Gaming menu Custom Service; enter service name XVR, Global Port Range 60377, Base host port 80  - Here it gets weird, it implies it wants the Base Host Port to be 60377,

The RG has noo way of knowing what Base Port you want. By default, it uses the same value as the Global Port range start number.

> a XVR/DVR for video cams.

I tried to do that once for a video system (exacqVision) only to find out that video system had smart logic which detected the external request was off LAN and rejected the setup (a pain to debug).

I had to use the vendor's external software to access the system, setting up the multiple pinholes it required.

I apologize for the messed up look of this post.&n(Edited per community guidelines)p; This forum is rather bad for posting.&n(Edited per community guidelines)p; Doesn't like images (they just clean the screen.&n(Edited per community guidelines)p; And all the other mess OMG how horrible.bbb

Have spent another half day on this port forward (Edited per community guidelines).

I guess I will see if maybe IP passthru will work - will put my FreshTomato previous router to catch and manage the traffic.

Now FreshTomato is a 1000 to 1 better that this ATT thingbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb

Below if the device listing of my XVR/DVR.&n(Edited per community guidelines)p; It was allocated with DHCP after I had added to a list of macaddr/ipaddr adresses.&n(Edited per community guidelines)p; I don't know how it became static, or maybe that's how it works.

I got 1 port forward to work; 4 more to go.  Anybody else have the secret?

For anybody struggling with port forwarding on the BGW320-500 router: this feature is broken on the device. It will only successfully forward a single packet for inbound connections, then will timeout for the next 30 seconds.

You can test this out yourself: set up a simple HTTP server on a computer, forward port 80 to it and use curl to connect to it twice in a row - the first connection will succeed whereas the second will timeout. Now wait 30 seconds and try again, same thing will happen.

The only solution I found was to IP passthrough to a better router and only use the BGW320-500 to convert the fiber optics connection to ethernet.