Wrong behaviour of Port Security feature

Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems

Moderator: Qbik Staff

Wrong behaviour of Port Security feature

Postby korzh » Mar 11 04 6:21 am

Hello,

Can somebody explain me what I am doing wrong or is this known bug:

Image

As you can see on the screenshot I have set "Deny" for 135 port but connections to this port are still allowed (my computer is 195.177.116.190)
--
With the best regards, Serge Korzh
http://www.korzh.com
korzh
 
Posts: 3
Joined: Mar 11 04 6:12 am
Location: Ukraine

Postby genie » Mar 11 04 9:24 am

How are you connected to the internet - dialup, DSL, etc? Also, can you, please, send me your routing tables before and after the external connection is established - we had an issue with some USB connections.
genie
Qbik Staff
 
Posts: 1788
Joined: Sep 30 03 10:29 am

Postby korzh » Mar 11 04 8:25 pm

I have permanent LAN connection to Internet. The building where our office is placed has router (195.177.116.189) which is connected directly to our ISP by wireless link (they called it "Radio ETHERNET"). All hosts in the building are linked to this router through LAN.
In my office there are two other computers which are connected to Internet through my computer (195.177.116.189) using WinGet ENS.

Here is my routing tables:

Code: Select all
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x3000003 ...00 00 1c 81 18 c3 ...... NDIS 5.0 driver                                                                 
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0  195.177.116.189     192.168.0.1     1
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1     1
      192.168.0.0    255.255.255.0      192.168.0.1     192.168.0.1     1
      192.168.0.1  255.255.255.255        127.0.0.1       127.0.0.1     1
    192.168.0.255  255.255.255.255      192.168.0.1     192.168.0.1     1
  195.177.116.188  255.255.255.252  195.177.116.190     192.168.0.1     1
  195.177.116.190  255.255.255.255        127.0.0.1       127.0.0.1     1
  195.177.116.255  255.255.255.255      192.168.0.1     192.168.0.1     1
        224.0.0.0        224.0.0.0      192.168.0.1     192.168.0.1     1
  255.255.255.255  255.255.255.255      192.168.0.1     192.168.0.1     1
Default Gateway:   195.177.116.189
===========================================================================
Persistent Routes:
  None

--
With the best regards, Serge Korzh
http://www.korzh.com
korzh
 
Posts: 3
Joined: Mar 11 04 6:12 am
Location: Ukraine

Postby korzh » Mar 11 04 8:33 pm

I meant "WinGate" of course in the previous message instead "WinGet"
--
With the best regards, Serge Korzh
http://www.korzh.com
korzh
 
Posts: 3
Joined: Mar 11 04 6:12 am
Location: Ukraine

Postby genie » Mar 12 04 9:18 am

From what I can see here you have only one interface which you want to use as both local and external one - it confuses Wingate. If you install another NIC and declare one of them local (private/trusted) and another one as external (public/non-trusted) then your firewall starts behaving as it is supposed to.
genie
Qbik Staff
 
Posts: 1788
Joined: Sep 30 03 10:29 am


Return to WinGate

Who is online

Users browsing this forum: Google [Bot] and 16 guests