psychiclogoboss

1. Edge Router Can't Access Vlan 1 On Pc

Unsolved I can't Connect to My Edgerouter X Web GUI.Help (self.HomeNetworking). I do recommend that you set up another user account with admin access and delete the original admin account. This will make your router just a little bit harder to break into. I am unable to remove a port from my default VLAN. I've tried: Switch(config)#interface FastEthernet 0/1 Switch(config-if)#no switchport access vlan 1 It has no errors but when I check it using: #show vlan brief Then the port I try to remove is still in vlan 1. I'm using a Cisco Catalyst 3550. Is it possible to remove a port from this VLAN?

I've replaced my generic PC running pfSense with a USG 50.With my old firewall I had two VLANS in use on my network: VLAN1 and VLAN2. I have a smart switch that is VLAN aware.

VLAN1 is for the normal network. VLAN2 is my guest network. I want to keep them separate obviously.VLAN2 comes in from my wireless access point (which also has another SSID for VLAN1), through the smart switch and now to the USG 50. The configuration of the smart switch and the wireless access point have not changed and were working with the previous firewall, so those items are not the problem here.I created VLAN1 and VLAN2 in the USG 50.

Edge Router Can't Access Vlan 1 On Pc

Both connect to LAN1 on the USG 50, which is a port on my smart switch. They each have a static IP address on separate networks.

VLAN1 and VLAN2 are assigned to the Private and Guest objects, respectively. LAN1 has a static address on a different network than VLAN1 (192.168.0.0/24) and VLAN2 (192.168.2.0/24).My problem is that VLAN1 and VLAN2 have no internet access at all. VLAN2 can't seem to contact the DHCP server that is enabled on it as well. I created two Policy Routes for VLAN1 and VLAN2 that both have the Next Hop as SYSTEMDEFAULTWANTRUNK with any source and any destination but that doesn't seem to work.I also set up firewall rules that the Guest (VLAN2) and Private (VLAN1) objects are allowed access from any source to any destination.The only thing that does work is being on LAN1's subnet (192.168.1.0/24) through a wired connection.I've been through several of the postings here and haven't been able to resolve it. I hoping that someone will be able to clear this up for me.

Things to consider:o In the USG, the VLAN tags have to be the same as set up in the switch for the respective VLANs. Tags and names are not necessarily the same.o The USG has to be told what address it immediately accesses that is the path to the VLAN's IP block addresses. This would be the address of the switch. Number of hops is probably OK at 2, which I use.o The switch has to configure its port to the USG as a trunk; and the USG has to treat the LAN1 port as a trunk (don't remember whether that required any configuration on the USG).o The USG should be providing DHCP to the separate VLANs and LANs, but this has to be deliberately configured for the VLANs. You can also do MAC binding for each VLAN.I have a default VLAN (tag is 1) in my Cisco SG-200-26 and a printer VLAN (tag is 20).

VLANs by their nature don't know how to route out (I realize that was an anthropomorphic simile). The router knows (with apologies to the Shadow). But once a message with an exterior (WAN) IP destination address gets from the switch to the router, the router shouldn't (and as far as I know can't without a firewall rule) treat it differently than a regular LAN message with an external IP destination address.Are you certain that the messages are getting to the router?If so, are you certain that the messages don't leave the router?It is possible that the messages are routed out to the Internet but the router can't route the responses back to their source devices, so no response is received. The router must be told the next hop IP address for the VLANs. (See 'IP Gateway' in my config listing above.)Your use of the plural 'ports' in your first paragraph immediately above is confusing; are you using two switch ports as two different trunks to two different LAN ports on the router?Last, I would note that some devices such as routers may be more picky about having all the T's crossed and I's dotted in their setup than others; so what worked before may not do so with a new device without all (or more or different) networking rules embedded in the relevant RFCs being met.kirby. Here is a crude diagram of my network layout. I have that Cisco access point that hands out two different SSIDs: one for VLAN1 and one for VLAN2.

I've looked around, and do not see a place in my Xbox One to look at specific files, so I have no clue how to drop maps onto my external drive to play Terraria on.Background info: I bought an Xbox One for myself for Christmas, and it came with a 350gb hard drive and some of the smallest games take like 10gbs to download so I bought a 4tb drive for 100 dollars, much less than they wanted for a much smaller internal Xbox One drive by the way.So how do I get a Terraria map from my PC onto my external drive, to play it on my Xbox? I've seen some kids on YouTube bragging about an all items map, but they don't show how to drop the map (transfer it from PC to Xbox).So what do I do?

It connects to port 6 on my switch. Port 1 connects to the LAN side of the USG 50. Both ports 1 and 6 are tagged for VLAN2. VLAN1 is untagged on all ports.In the USG 50 both the Private and Guest zones have full access in the firewall to any destination including the ZyWall (I thought this might be the reason that DHCP wasn't working). Obviously in the future, I'd like to segregate the Guest and Private zones but for getting this configured I'm trying to remove as many variables as possible.I have a Policy Route for each VLAN for any source and any destination that the next hop is the system default WAN trunk (I saw that elsewhere on here).The wired network works fine at least when I assign a static IP address. It's just the wireless traffic marked for VLAN1 or VLAN2 that isn't getting a DHCP address from the configured VLAN1 and VLAN2 in the USG 50.

Jon: Switch port 1 should be set as a TRUNK, not tagged, as it serves to move both tagged and untagged messages to and from the router. This is doable in my Cisco's port setup.

This may not be your problem though.Jon: Your VLAN2 subnet is the same as the ZyXEL uses for LAN2. It seems to me easier to use VLAN tags in tens region to clearly avoid misconfiguration. If you want to keep your present VLAN addresses, then set LAN2, LAN3 and DMZ port IP blocks to something well away from your VLANsJon: I still haven't seen you respond with respect to hop gateway settings in the router.Brano: The answer is yes as that is my configuration. All traffic to the switch passes through the LAN1 port of the USG.Brano: L3 switches can be set to establish VLANs (I presume, not having one), but L2 switches such as I have can only be set up to properly move data to and from them; the router has to establish the VLANs.With respect to Internet access, I have blocked VLAN 20 from the outside world, and I never performed a test with a PC with the firewall rules off to confirm that VLAN20 could get out.

Doing so at present would be a project that would interfere with house reno activities, so I can't lead by example. I'll have to continue leading from behind.kirby. Let me start over here. Forget the VLANs for the moment. I think my fundamental problem is that DHCP is not functioning for me at all on LAN1. Clients request a DHCP address but never get a response back and then default to the self-assigned IP range, which is not good.

Setting up DHCP is simple enough so I'm not sure how I could have messed that up. I even took a laptop up and plugged it right in to the USG LAN1 port to take the switch and any VLANs out of the equation and it still didn't pull an IP address from DHCP. I think this is the root of all of my problems.

The only thing I did was go up to the router with a laptop an plugged it in to P4 to see if it could pull a DHCP address right from the source, no switches, wireless access points or VLANs in between. It didn't work the first time. Then I brought the laptop back downstairs and plugged it back in to the switch I had it plugged in to when I was troubleshooting and it suddenly worked.

I turned on the wireless radios and also got a DHCP address on both the private and guest networks (VLAN1 and VLAN2).