Best Of
Re: NR7101
Hi Tony,
Thanks for your reply.
I have already tested with everything on auto. It did not make a real difference.
Is it possible that the router has a hardware problem? I think it has several antennas inside. What if one or more are not working properly? Is there a way to test that? The router arrived in a box that was slightly damaged. I guess it got dropped during transport. The major speed difference compared to my mobile phone could be explained by an antenna not receiving a proper signal.
Do you know a way to see which bands are used on an android phone? This ways I can compare the bands used by the router vs those on the phone.
Another thing that I can try is to downgrade the LTE module firmware to the previous version. Apparently there are some users that said that the latest version actually caused connection and speed problems.
Thanks,
Peter
Thanks for your reply.
I have already tested with everything on auto. It did not make a real difference.
Is it possible that the router has a hardware problem? I think it has several antennas inside. What if one or more are not working properly? Is there a way to test that? The router arrived in a box that was slightly damaged. I guess it got dropped during transport. The major speed difference compared to my mobile phone could be explained by an antenna not receiving a proper signal.
Do you know a way to see which bands are used on an android phone? This ways I can compare the bands used by the router vs those on the phone.
Another thing that I can try is to downgrade the LTE module firmware to the previous version. Apparently there are some users that said that the latest version actually caused connection and speed problems.
Thanks,
Peter
Re: NR2101 IP Pass-through
Good morning @martiko
Yes, I have some good news. I got an update from the Zyxel support that solved the issue for me.
The way NR2101 works is that it will bind the first device that connects after setting IP Pass-through in the settings UI. The binding seems permanent, even if you disable pass-through and enable it.
What solved the issue for me was to factory reset the device. Connect the client I wanted pass-through to work for, and with that client enable pass-through in the UI.
I hope this helps!
/A
Yes, I have some good news. I got an update from the Zyxel support that solved the issue for me.
The way NR2101 works is that it will bind the first device that connects after setting IP Pass-through in the settings UI. The binding seems permanent, even if you disable pass-through and enable it.
What solved the issue for me was to factory reset the device. Connect the client I wanted pass-through to work for, and with that client enable pass-through in the UI.
I hope this helps!
/A
Brackan
1
USG FLEX 50W Not Following Allow Policy
I have a USG FLEX 50W (USG20W-VPN) running V5.32(ABAR.0) that was just installed in front of a PBX. Initially all went well. After installation, we could make calls in and out. Now, for some reason, it is dropping packets due to the default rule when it should not.
I pulled a packet capture and see the packets for a new call coming in to the WAN port, but not making it out the LAN port to the phone system. Upon searching the log, I see the packets are being dropped due to security policy. The original configuration has not changed, so why is it now deciding to drop these legitimate packets?
I even tried moving the policy rule for the inbound VoIP packets up to the top priority to see if that changed anything and it did not. The packets are still being dropped.
The policy rule enabled allowing the VoIP packets through is set from WAN to LAN1 with a source of the originating servers (our VoIP servers), the destination is the LAN1 card IP of the PBX, and the service is set to a service of 5060 (SIP). Everything else for the policy is default except for the name and description.
I ran the diagnostics in case the file is needed by ZyXEL to look deeper into this.
If someone has any bright ideas to kick it into gear, I'd like to hear them.
I pulled a packet capture and see the packets for a new call coming in to the WAN port, but not making it out the LAN port to the phone system. Upon searching the log, I see the packets are being dropped due to security policy. The original configuration has not changed, so why is it now deciding to drop these legitimate packets?
I even tried moving the policy rule for the inbound VoIP packets up to the top priority to see if that changed anything and it did not. The packets are still being dropped.
The policy rule enabled allowing the VoIP packets through is set from WAN to LAN1 with a source of the originating servers (our VoIP servers), the destination is the LAN1 card IP of the PBX, and the service is set to a service of 5060 (SIP). Everything else for the policy is default except for the name and description.
I ran the diagnostics in case the file is needed by ZyXEL to look deeper into this.
If someone has any bright ideas to kick it into gear, I'd like to hear them.
DeanH
1
Re: USG FLEX 50W Not Following Allow Policy
I have also rebooted it to see if that works, but no. Still blocking for some unknown reason. It is like the original rule is not being seen in the table and the default rule is catching the packets.
DeanH
1
Re: USG FLEX 50W Not Following Allow Policy
I ended up removing the rule completely and rebuilding it again. It is now working.
However, I found another rule that is for management access to the PBX that is also blocking the packets. On this one, I changed the service object from a specific port on the external side to match with the same port on the LAN1 side (device) and it works. This required changing both the policy and the NAT rule. So, there appears to be a problem with this particular static NAT rule for some reason.
I put the original external port back in to both the security policy and the NAT rule and it is blocking me once again. ?????!!!!
However, I found another rule that is for management access to the PBX that is also blocking the packets. On this one, I changed the service object from a specific port on the external side to match with the same port on the LAN1 side (device) and it works. This required changing both the policy and the NAT rule. So, there appears to be a problem with this particular static NAT rule for some reason.
I put the original external port back in to both the security policy and the NAT rule and it is blocking me once again. ?????!!!!
DeanH
1
Re: USG FLEX 50W Not Following Allow Policy
Finally figured it out. I forgot that on the security policy, it wants to see the LAN1 port, not the WAN port as the Service. That is so confusing since I am used to a WAN rule utilizing WAN components (IP/ports), not LAN components (IP/ports).
DeanH
1
Re: USG FLEX 50W Not Following Allow Policy
Rule of thumb about security policy rules.
98% of the times the author write it wrong. I did that too, so many times 
mMontana
1
Re: Which Wan IP ? Lete7490-M904
Currently none. Ask your ISP/Provider for more info about direct access to your device or your "own" public IP.JMB_74 said:So now, which ip using to access the router from internet ?
mMontana
1
Re: 1920-8HPv2 - SYS LED flashing rapidly. System does not boot
Dear @Moritz_M , The stable/latest firmware of GS1920-8HPv2 had already released for some time, but there is no similar feedback from other users recently, so we hope you may help us to confirm the points below: The SYS LED flashing means the device is booting up, could you let us know how long have you waited? Over 1 minute?There is a Reset button which will reboot Switch with cold start and also a Restore button to reset the Switch to factory default setting when holding for over 7 seconds.On the right-hand side of the Switch, there is a 4-pin port can be connected with a 4-pin-to-USB console cable, do you have the cable?If you have "waited for a long time", "tried to reset or restore", "don't have such console cable on your hand", we recommend you contacting your reseller for the RMA process.