10-16-2020 11:34 AM
I have a SG350-10MP, and want to know if this is possible without a external router (this is all based on everything living on one switch).
I have VLAN1 set up with a IP of 192.168.1.1/24 and DHCP with some addresses in that range
I have VLAN2 set up with a IP of 172.22.254.254/16 - no dhcp range
I have one device that needs to live in VLAN2 and have a IP in that range, but needs to communicate with another device in VLAN1. Is it possible to set up the IPv4 routing to make the 2 talk? And if it is, how would I go about it?
10-16-2020 12:07 PM
Without the use of ACLs restricting Inter-VLAN routing, these two subnets will be able to communicate with each other by default once the VLANs are properly configured.
10-16-2020 12:41 PM
10-16-2020 12:54 PM
i do not see any issue in the config, it is just a simple config.
thinks me that it is an end device issue with windows FW, how are you testing reachability Ping ?
can you also post the outcome of the test here?
also from switch
show ip interface brief
show ip route
10-16-2020 01:09 PM
That's why I've been confused - there's not much to this config.
I am testing via ping so guess it could be Windows related:
Pinging 192.168.1.202 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.202:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
From switch:
switch7feacb#show ip interface
IP Address I/F I/F Status Type Directed Prec Redirect Status
admin/oper Broadcast
------------------ --------- ---------- ------- --------- ---- -------- ------
172.22.254.254/16 vlan 10 UP/UP Static disable No enable Valid
192.168.1.1/24 vlan 20 UP/UP Static disable No enable Valid
switch7feacb#sh ip route
Maximum Parallel Paths: 1 (1 after reset)
IP Forwarding: enabled
Codes: > - best, C - connected, S - static
C 172.22.0.0/16 is directly connected, vlan 10
C 192.168.1.0/24 is directly connected, vlan 20
10-16-2020 01:36 PM - edited 10-16-2020 01:37 PM
@MikeWerner0426 wrote:I have VLAN 10 set up with a IP of 172.22.0.0/16 - no dhcp range
I have VLAN 20 set up with a IP of 192.168.1.1/24 and DHCP with some addresses in that range
I have one device that needs to live in VLAN 10 and have a IP in that range, but needs to communicate with another device in VLAN 20.
So your VLAN 10 host is a Windows PC statically-assigned 172.22.254.250. And your VLAN 20 unknown host is assigned 192.168.1.202 via the switch's DHCP server.
I.e.:
VLAN 10 host: 172.22.254.250/172.22.254.254
VLAN 20 host: 192.168.1.202/192.168.1.1
Can you confirm IP addressing on VLAN 20 host by posting relevant output?
What type of device is the VLAN 20 host?
10-16-2020 02:38 PM
Yes - IP address for the VLAN 20 device is 192.168.1.202/255.255.255.0/192.168.1.1
It is a touch panel - manufacturer unnamed. And it does accept pings, can ping directly from the switch without any issue. But I have tried with another PC as well to see if I could ping one way or the other but it is the same result.
10-16-2020 01:12 PM
from PC you should able to ping
gateway of VLAN 10 and 20 ? then most windows FW here.
10-16-2020 01:15 PM
Can ping GW of VLAN 10:
Pinging 172.22.254.254 with 32 bytes of data:
Reply from 172.22.254.254: bytes=32 time=1ms TTL=64
Reply from 172.22.254.254: bytes=32 time=1ms TTL=64
Reply from 172.22.254.254: bytes=32 time=1ms TTL=64
Reply from 172.22.254.254: bytes=32 time=1ms TTL=64
Ping statistics for 172.22.254.254:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 1ms, Average = 1ms
Can't ping GW of VLAN 20:
Pinging 192.168.1.1 with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 192.168.1.1:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
10-16-2020 01:17 PM - edited 10-16-2020 01:20 PM
what is the device IP ? can you post ipconfig /all ?
from VLAN 20 device can able to ping 192.168.1.1 ?
go to the video : ( make sure you have tick box ipv4 routing enabled)
https://www.youtube.com/watch?v=NLMKwYSlQDY
Layer 3 enabled?
10-16-2020 01:26 PM
Yes to being able to ping 192.168.1.1 from the VLAN 20 device.
Device IP is 172.22.254.250
ipconfig:
Ethernet adapter Ethernet 3:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Realtek USB GbE Family Controller
Physical Address. . . . . . . . . : 00-E0-4C-01-4B-E0
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::5529:ca24:a033:362%22(Preferred)
IPv4 Address. . . . . . . . . . . : 172.22.254.250(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . : 172.22.254.254
DHCPv6 IAID . . . . . . . . . . . : 872472652
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-75-76-24-B8-31-B5-3F-13-0A
DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1
fec0:0:0:ffff::2%1
fec0:0:0:ffff::3%1
NetBIOS over Tcpip. . . . . . . . : Enabled
10-16-2020 01:28 PM
Do check the above setting as advised in other posts.
10-16-2020 01:40 PM
Yeah, I've been through those already and have the settings per the recommendations.
10-17-2020 12:19 AM
If you have done all, Kindly share the screenshot for us to verify why this was not working as expected.
Since this is new i would suggest to reset to Factory and start over fresh and post the outcome.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide