Comments
-
According to the support: If I do a tcpdump on the M200 (-nei eth1 host 10.100.5.10) and use 10.100.5.10 (VLAN 100) to ping 1.1.1.1, I do not see a VLAN ID. If I ping 10.11.0.1 (M200 interface for VLAN 33), I can see the VLAN ID 33. We tested some stuff on a test setup. Here's what we tested: Client 10.100.8.6 connected to…
-
That's probably not the problem. But I'll give it a try. The M290 can reach the internet (via Diagnostics pinging google.com/8.8.8.8) and I've also configured (untagged) vlan 100 on eth3. Plugged my laptop into eth3 and set a static IP with the M290 as my default gateway. It could also reach the internet. It couldn't reach…
-
I haven't tried that yet, I'll try that tonight.
-
Tried that. Unfortunately, it still doesn't work. My support case already got escalated 3 times and they even put the priority to Critical.. I've migrated the config 4 times, even did it once while I was on the phone with support. I don't know anymore, could my M290 be defective? When I switch back to the M200 it just…