Thread Info
  • State Not Answered
  • Locked Locked
  • Replies 5 replies
  • Subscribers 6 subscribers
  • Views 1464 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Initial config - no traffic

Mmm M

Hi guys,

Fresh install.

 here is my topology (Hyper-V).

 Internal (192.168.88.0/24) -----------------------UTM-------------External (router)-----------Internet

 UTM Interfaces:

External (WAN)
[Up]
on eth1
[192.168.7.104/24]

MTU 1500 · DEFAULT GW 192.168.7.1
Added by installation wizard


Internal
[Up]
on eth0
[192.168.88.1/24]
MTU 1500
Auto-created on installation

 There is no traffic going through the UTM. I can ping it and web access it from a LAN PC, however, there is no traffic going through it. The traffic is not hitting the UTM, I even enabled traceroute/icmp on UTM and tried tracert and it times out with *.

When I check the traffic monitor (internal in), I can see pings when I ping 192.168.88.1, however, there is no info when I try to ping the Internet or web access anything (DNS fails stragith away).

 Am I missing something obvious? The DG on the PC points to 192.168.88.1 but no traffic.



This thread was automatically locked due to age.
Parents
  • 0

    please post the output from "route print".

    looks like your traffic try to go other ways...

    are you able to ping 192.168.7.1 from UTM? (support -> tools -> Ping check)

     


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Reply
  • 0

    please post the output from "route print".

    looks like your traffic try to go other ways...

    are you able to ping 192.168.7.1 from UTM? (support -> tools -> Ping check)

     


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

Children
  • 0 in reply to dirkkotte

    I can ping the Internet from the UTM, no problem.

    PING 8.8.8.8 (8.8.8.8) 56(84) bytes of data.

    64 bytes from 8.8.8.8: icmp_seq=1 ttl=121 time=72.1 ms

    64 bytes from 8.8.8.8: icmp_seq=2 ttl=121 time=81.0 ms

    64 bytes from 8.8.8.8: icmp_seq=3 ttl=121 time=55.5 ms

    64 bytes from 8.8.8.8: icmp_seq=4 ttl=121 time=94.0 ms

    64 bytes from 8.8.8.8: icmp_seq=5 ttl=121 time=83.0 ms

     

    The problem is that from a local PC (192.168.88.x) - I can web access the UTM and ping it, but when I try to access antything else, seems that UTM ignores all that traffic. I tried from a physical laptop - the same problem - I can web access the UTM but anything that is supposed to go through the UTM - does not reach it or gets dropped.

     

    it literally behaves like there was an incorrect default gateway on the PC.

     

    I did configure it as 192.168.88.1 on PCs.

  • 0 in reply to Mmm M

    try route print ...

    seen incorrect static routes (or routes learned by ICMP-redirect) already.

    Also a router configured with proxy-arp may by the cause.

    You may use ssh to the UTM an check incomming traffic with tcpdump


    Dirk

    Systema Gesellschaft für angewandte Datentechnik mbH  // Sophos Platinum Partner
    Sophos Solution Partner since 2003
    If a post solves your question, click the 'Verify Answer' link at this post.

  • 0 in reply to dirkkotte

    You mean a routing table on the PC? I did check that, it looks good:

    IPv4 Route Table
    ===========================================================================
    Active Routes:
    Network Destination        Netmask          Gateway       Interface  Metric
              0.0.0.0          0.0.0.0     192.168.88.1    192.168.88.44    281
            127.0.0.0        255.0.0.0         On-link         127.0.0.1    331
            127.0.0.1  255.255.255.255         On-link         127.0.0.1    331
      127.255.255.255  255.255.255.255         On-link         127.0.0.1    331
         192.168.88.0    255.255.255.0         On-link     192.168.88.44    281
        192.168.88.44  255.255.255.255         On-link     192.168.88.44    281
       192.168.88.255  255.255.255.255         On-link     192.168.88.44    281
            224.0.0.0        240.0.0.0         On-link         127.0.0.1    331
            224.0.0.0        240.0.0.0         On-link     192.168.88.44    281
      255.255.255.255  255.255.255.255         On-link         127.0.0.1    331
      255.255.255.255  255.255.255.255         On-link     192.168.88.44    281
    ===========================================================================
    Persistent Routes:
      Network Address          Netmask  Gateway Address  Metric
              0.0.0.0          0.0.0.0     192.168.88.1  Default
    ===========================================================================

     

    Proxy-arp... There is no router on 192.168.88.0, I did that on purpose to make sure this is a unique subnet.

    Whats more - I can https to the UTM from that PC no problems :/

  • 0 in reply to Mmm M

    Looks like a Hyper-V issue... installed with VirtualBox.

Unfiltered HTML