No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search


To have a better experience, please upgrade your IE browser.


It cannot pass Eudemon 100E firewall to visit the public network address port of 1111

Publication Date:  2019-07-18 Views:  545 Downloads:  0

Issue Description

The users network structure:

Intranet the ----- Eudemon (X.X.8.86/28) public network ----X.X.8.18/27
     The Eudemon public network interface address X.X.8.86/28,  X.X.8.18 ban ping
     Intranet users access X.X.8.18 1111 port through nat, it can not connect successfully. The intranet users nat Internet normal
     Telnet X.X.8.18 1111 in Eudemon device directly, it can not connect
   Configure Public network address on pc, it can visit X.X.8.18 1111 port.
    other firewall customers previously used is no problem, it can connect successfully.

Alarm Information


Handling Process

1. The public network address X.X.8.86/28 all mapped to an address of the internal network, but it can not successfully access X.X.8.18 1111 port.

2. Try to modify X.X.8.86 mask to 27 bit which is same with X.X.8.18, connection is successful after a short period of time the, but then interrupted, it can no longer connect successfully

3. View on the firewall session, there was session visiting X.X.8.18

4. View debugg information on the firewall:

It can see that X.X.8.18 request directly for ARP, the device think it is in the same network segments, our mask is 28 bit, that is in the different network segments with this IP, it will not response ARP request. The peer side can not learn ARP requests, causing barrier. In normal circumstances, the peer device should request the gateway arp information.

   27 mask instead, our equipment will send gratuitous ARP, so the peer side appear a short pass, the ARP aging, etc., once again appear unreasonable.

5. Eudemon 100E X.X.8.86 mask changed to 24 that solve the problem, it doubts that X.X.8.18 mask setting is probloematic, it is recommended that the user to confirm the peer side address mask setting.

Root Cause

1. Peer device configuration issues
2.  E100E firewall policy issues