Subnet bug I think

PeterUK
PeterUK Posts: 3,124  Guru Member
Community MVP 2500 Comments Sixth Anniversary 100 Answers
USG60W V4.65(AAKZ.1) 

I made a VLAN4091 on base port LAN1
192.168.254.9 
255.255.255.248
DHCP  192.168.254.10 pool size 5

Other subnets 
LAN1 192.168.254.129  / 255.255.255.128
WAN2 192.168.254.2 / 255.255.255.252

When make a device with IP of 192.168.254.10 it fails to have internet but  192.168.254.11 is fine

I have a subnet calculate that shows I'm subneting correctly?

Accepted Solution

  • Zyxel_Cooldia
    Zyxel_Cooldia Posts: 1,510  Zyxel Employee
    100 Answers Sixth Anniversary 1000 Comments Zyxel Certified Sales Associate
    Answer ✓

    By following your interface setting in lab device, Host 192.168.254.10 can get Internet access.
    Can you see host 192.168.254.10 packets send out to wan2 interface in routing trace if you ping to 8.8.8.8?

    Go to MAINTENANCE > Diagnostics > Routing Traces and set 192.168.254.10 to source

    Don't miss this great chance to upgrade your Nebula org. for free!

All Replies

  • Zyxel_Cooldia
    Zyxel_Cooldia Posts: 1,510  Zyxel Employee
    100 Answers Sixth Anniversary 1000 Comments Zyxel Certified Sales Associate
    Answer ✓

    By following your interface setting in lab device, Host 192.168.254.10 can get Internet access.
    Can you see host 192.168.254.10 packets send out to wan2 interface in routing trace if you ping to 8.8.8.8?

    Go to MAINTENANCE > Diagnostics > Routing Traces and set 192.168.254.10 to source

    Don't miss this great chance to upgrade your Nebula org. for free!

  • PeterUK
    PeterUK Posts: 3,124  Guru Member
    Community MVP 2500 Comments Sixth Anniversary 100 Answers
    edited September 2021

    So this was odd as I did the Routing Traces for 192.168.254.10 to 8.8.8.8 with 60 second capture when pinging the whole USG rebooted! And when it was back on line 192.168.254.10 can now ping the internet.

    I have done a debug info collector ask if you need it.

    ….But I think I know why the problem happened but can't think how it caused a problem. I needed for the client to NTP from VLAN4091 to 192.168.254.9 NAT to 192.168.255.250 then SNAT from 192.168.255.240 I made the mistake of putting in the NAT rule for external IP as 192.168.254.10 not 192.168.254.9.

    All seems to be working now B)


Security Highlight