SG-1000 and Apple Airport Extreme
-
Is the other "different" cable you tried a cross over cable, I only ask as your connecting a router to a router ?
https://upload.wikimedia.org/wikipedia/en/thumb/9/96/Vergleich_2von2_Crossoverkabel.jpg/1920px-Vergleich_2von2_Crossoverkabel.jpg
If you set up the LAN port as a simple LAN port on the SG-1000 can you ping the Airport Extreme ?
Both are straight. I'm connecting the netgate to the airport directly. Simple LAN works. AE gets DHCP and I have working internet via wireless.
But I don't see how the cable can be at fault here, since sg-2440 works just fine, and normal LAN works.
-
Yup I was trying to verify if the SG-1000 auto mdix'd or not, if you just set it up as a normal port and it works that tells me it does.
-
Is it possible that the issue has something to do with this?
I've got 99 problems, but a switch ain't one
Maybe the VLAN needs to be set up in the SG-1000 switch settings as well as on the interface?
-
@virgiliomi:
Is it possible that the issue has something to do with this?
I've got 99 problems, but a switch ain't one
Maybe the VLAN needs to be set up in the SG-1000 switch settings as well as on the interface?
I've tried creating a VLAN from there and it didn't work.
-
Tried doing a packet capture, are packets tagged with vlan1003 leaving the firewall ?
If you do a packet capture in promiscuous mode from the lan interface and then open it up in Wireshark you should be able to see if the tagged packets are leaving the SG-1000.
If you type vlan in the filter field you should see packets that are tagged, the attached screenshot shows packets tagged with vlan2, ignore the vlan column thats something I set up.
-
Don't pull your hair out. There might be an issue there with the higher VLAN IDs.
-
Don't pull your hair out. There might be an issue there with the higher VLAN IDs.
It might be so, I just saw this error in the log. ( i hope I attached it)
Tried doing a packet capture, are packets tagged with vlan1003 leaving the firewall ?
I tried setting a static IP and pinging the LAN from the VLAN interface and it threw a "no route to host".
Unfortunately I don't have enough time to troubleshoot this in depth. I've already lost a lot of time with this. Honestly, this product should be advertised more clearly as a beta, because I'm a networking noob and I've purchased this based on the "out of the box" way the other 2 worked. I've seen some other random errors in the logs.
Thanks for taking your time though!
 -
Fixed in latest snapshots.
-
I've noticed. I managed to setup the VLAN and assign an interface but I can't test it yet because it's at a remote location.
-
Problem solved with update.
