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

Routing issue - clients unable to access internet

Hi all,

I have a problem configuring the routing on the XG firewall.

My ISP delivers access through VLAN trunks and requires the following:

VLAN 10 - Internet
VLAN 20 - IPTV

For the IPTV portion, in addition to VLAN 20, the packets has to be marked with PCP value of 4 in order to be delivered.

Referencing to a custom router which was built off Arch Linux which I have tested and worked (refer to attachment: ArchLinux_cfg.zip), I have configured the following in XG which did not work when I plugged my notebook to port 2 of the UTM. It did receive IP and and address but was unable to route beyond the local network. The XG on the other hand have no issue running ping and traceroute to internet addresses.

From what I can tell, it seems the clients can't find a route out of the XG but this should have been dealt with when the policies are defined.

Maybe I have missed out something?

Interface:

DHCP:

Clientless users:

Policies:

Policy ID 1:

Policy ID 2:

Ping and traceroute from XG:

Ping and traceroute from PC connected to Port 4:

Pinging 192.168.1.16 with 32 bytes of data:
Reply from 192.168.1.16: bytes=32 time=1ms TTL=64
Reply from 192.168.1.16: bytes=32 time=2ms TTL=64
Reply from 192.168.1.16: bytes=32 time=1ms TTL=64
Reply from 192.168.1.16: bytes=32 time=1ms TTL=64

Ping statistics for 192.168.1.16:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 1ms, Maximum = 2ms, Average = 1ms

Pinging 192.168.2.33 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 192.168.2.33:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Pinging 8.8.8.8 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.

Ping statistics for 8.8.8.8:
    Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),

Tracing route to 8.8.8.8 over a maximum of 30 hops

  1     1 ms     1 ms     1 ms  192.168.1.16 
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *        *        *     Request timed out.
 17     *        *        *     Request timed out.
 18     *        *        *     Request timed out.
 19     *        *        *     Request timed out.
 20     *        *        *     Request timed out.
 21     *        *        *     Request timed out.
 22     *        *        *     Request timed out.
 23     *        *        *     Request timed out.
 24     *        *        *     Request timed out.
 25     *        *        *     Request timed out.
 26     *        *        *     Request timed out.
 27     *        *        *     Request timed out.
 28     *        *        *     Request timed out.
 29     *        *        *     Request timed out.
 30     *        *        *     Request timed out.

Trace complete.

Edited: Replace config text with screenshots of config and included ping and traceroute logs from PC.



This thread was automatically locked due to age.
Parents
  • Vlystria,

    what message do you receive when you try to traceroute from a PC running on VLAN 10 or 20 to another network?

    For XG as you said, the ping and traceroute are fine, right?

    Thanks.

  • Hi lferrara,

    I should clarify that VLAN 10 and 20 is defined on the WAN interface as my ISP delivers access through them.

    Running a ping and traceroute from a PC connected to port 2 or 3 of the XG to an internet address (for e.g 8.8.8.8) only gives a Request Timed Out error

  • Can you successfully ping or traceroute from the XG to a PC connected to port 2 or 3?

    Will

    --------------------
    Sophos UTM / Sophos XG Firewall home user

    Private: Virtual UTM 9.3, ESXi 6.0: 2 vCPUs, 8GB RAM, 120GB vHDD, 3 vNICs

    Private: Virtual Sophos XG Firewall, ESXi 6.0: 1 vCPU, 4vCores, 6GB RAM, 80/4 GB vHDD, 3 vNICs

    ESXi 6.0 Host: SuperMicro C7Z97-OCE, Core I5-4690 3.5 GHz, 32GB RAM, NICS: I217-V, I210, I340-T4

  • Hi Will,

    Pinging to the XG from a PC connected to port 2 and 3 works.

    Pinging to a PC connected to port 2 and 3 from the XG works as well.

  • Just a shot in the dark, but I was thinking that it may be a routing issue where you would need to add static routes to your internal networks. e.g.

    Destination: 192.168.0.0 /255.255.255.0

    Gateway:      192.168.0.1

    Interface:      Port2

     

    Destination: 192.168.1.0 /255.255.255.0

    Gateway:      192.168.1.1

    Interface:      Port3

     

    Since you can ping from the XG to internal devices, this is probably not the issue.

     

    Will

    --------------------
    Sophos UTM / Sophos XG Firewall home user

    Private: Virtual UTM 9.3, ESXi 6.0: 2 vCPUs, 8GB RAM, 120GB vHDD, 3 vNICs

    Private: Virtual Sophos XG Firewall, ESXi 6.0: 1 vCPU, 4vCores, 6GB RAM, 80/4 GB vHDD, 3 vNICs

    ESXi 6.0 Host: SuperMicro C7Z97-OCE, Core I5-4690 3.5 GHz, 32GB RAM, NICS: I217-V, I210, I340-T4

Reply
  • Just a shot in the dark, but I was thinking that it may be a routing issue where you would need to add static routes to your internal networks. e.g.

    Destination: 192.168.0.0 /255.255.255.0

    Gateway:      192.168.0.1

    Interface:      Port2

     

    Destination: 192.168.1.0 /255.255.255.0

    Gateway:      192.168.1.1

    Interface:      Port3

     

    Since you can ping from the XG to internal devices, this is probably not the issue.

     

    Will

    --------------------
    Sophos UTM / Sophos XG Firewall home user

    Private: Virtual UTM 9.3, ESXi 6.0: 2 vCPUs, 8GB RAM, 120GB vHDD, 3 vNICs

    Private: Virtual Sophos XG Firewall, ESXi 6.0: 1 vCPU, 4vCores, 6GB RAM, 80/4 GB vHDD, 3 vNICs

    ESXi 6.0 Host: SuperMicro C7Z97-OCE, Core I5-4690 3.5 GHz, 32GB RAM, NICS: I217-V, I210, I340-T4

Children
No Data