I am not sure what I did wrong here, but I had this working, and now it doesn't work. I have setup two VLANs on a WLC that's built-in to my router, the C1111-8PW, VLAN1 and VLAN40. VLAN1 is on the 10.0.0.0 / 24 network, VLAN40 is on the 10.0.40.0 / 24 network. The built-in WLC is connected to Wlan-GigabitEthernet 0/1/8 interface. Here is it's running config.
switchport trunk allowed vlan 1,40
switchport mode trunk
Does that look okay or am I missing something? On the WLC, I cannot ping 10.0.40.1, which is the IP address to VLAN40 on the router. All the examples I see online seem to show something along the lines of this:
Description Connected to the WLC
switchport trunk encapsulation dot1q
switchport trunk allowed vlan 1,20,60
switchport mode trunk
However, when I try configuring the interface Wlan-GigabitEthernet 0/1/8, there is no switchport trunk encapsulation dot1q. From what I've read, I believe that encapsulation is required for what I'm attempting to do. I cannot seem to figure out how to enable it though.
... View more
Another example of the problem, I'm trying to bring the final AP up, WAP3, and I'm updating the backup image to 188.8.131.52. It's connecting to a TFTP server running on a Windows 10 Enterprise laptop, which is connected wirelessly to WAP2. So far, the progress has reached 78% and there's been 38 timeouts. Not exactly sure what I did wrong or how to fix this. The signal strength in Windows shows full bars. My wife's cell phone has now repeatedly received the following message:
Failed to obtain IP address
She's pulling an IP address from the DHCP server running on the actual router, not the WLC or APs. If there's any configuration files or logs that I can share, I will be more than happy to. Here's what show interfaces dot11Radio 0 wlan 1looks like:
WAP2#show interfaces dot11Radio 0 wlan 1 statistics
VAP Level Stats: apr0v0 (under radio wifi0)
Tx Data Packets = 975611
Tx Data Bytes = 488685744
Tx Data Payload Bytes = 451612526
Rx Data Packets = 751367
Rx Data Bytes = 405724949
Rx Data Payload Bytes = 395205811
Tx Unicast Data Packets = 955019
Rx Unicast Data Packets = 751367
Tx Multi/Broadcast Data Packets = 20592
Rx Multi/Broadcast Data Packets = 0
Average Tx Rate (kbps) = 65000
Average Rx Rate (kbps) = 65000
Tx multicast Data Packets = 18765
Tx Broadcast Data Packets = 1827
Rx multicast Data Packets = 18446744073709550565
Rx Broadcast Data Packets = 1051
Packets Dropped = 57
Packets Errored = 23934
Rx errors = 23725
Rx Dropped = 0
Tx failures = 209
Tx Dropped = 57
Host Discard = 0
Rx MIC Errors = 0
Last Tx rate for unicast Packets = 65000
Last Tx rate for unicast Packets(mcs) = 6
Last Tx rate for multicast Packets = 24000
Last Tx rate for multicast Packets(mcs) = 48
Total beacons sent to fw in SWBA intr = 693579
Those RX Errors and TX Dropped's have me concerned. It's not just that AP. Any of them I connect to see to exhibit similar issues. All the APs (three 1832i's, one built-in the C1111-8PW, which is like the 1815i) are hardwired via CAT6+ F/UTP Belden 2412F, so I do not think that's the issue. For neighboring SSIDs, I see 12, but most have little strength, I believe because they're too far away. There's maybe 8 that have decent strength, plus my two. Could this be an interference issue? The old cheap Spectrum wireless router that was built into the cable modem didn't have any issues like this. Here's the output of the Wlan-GigabitEthernet 0/1/8 interface, which is the trunk line on the router that the built-in WLC0 an AP0 uses.
Wlan-GigabitEthernet0/1/8 is up, line protocol is up (connected)
Hardware is WLAN Gigabit Ethernet, address is a093.5188.4f10 (bia a093.5188.4f10)
Description: Internal switch interface connecting to the embedded AP
MTU 1500 bytes, BW 1000000 Kbit/sec, DLY 10 usec,
reliability 255/255, txload 1/255, rxload 1/255
Encapsulation ARPA, loopback not set
Keepalive not supported
Full-duplex, 1000Mb/s, link type is auto, media type is 10/100/1000BaseTX
input flow-control is off, output flow-control is unsupported
ARP type: ARPA, ARP Timeout 04:00:00
Last input never, output 00:00:07, output hang never
Last clearing of "show interface" counters never
Input queue: 0/375/0/0 (size/max/drops/flushes); Total output drops: 0
Queueing strategy: fifo
Output queue: 0/40 (size/max)
5 minute input rate 0 bits/sec, 0 packets/sec
5 minute output rate 4000 bits/sec, 2 packets/sec
3142642 packets input, 600785906 bytes, 0 no buffer
Received 83667 broadcasts (169380 multicasts)
0 runts, 0 giants, 0 throttles
0 input errors, 0 CRC, 0 frame, 0 overrun, 0 ignored
0 watchdog, 169380 multicast, 0 pause input
0 input packets with dribble condition detected
5098414 packets output, 5452088722 bytes, 0 underruns
0 output errors, 0 collisions, 1 interface resets
7195 unknown protocol drops
0 babbles, 0 late collision, 0 deferred
0 lost carrier, 0 no carrier, 0 pause output
0 output buffer failures, 0 output buffers swapped out
To me, that looks good, minus the 7195 unknown protocol drops....I'm going to research that and see what it is. Maybe I should install the NBAR protocol pack now.
... View more
Hello, I noticed since I added a Cisco AP 1832i to my network, we are having some issues connecting to various external sites. For example, I go to google, and about every 4th site I try to go to will time out. I refresh the page, I can go just fine. It's not just with google though. I have a Cisco C1111-8PW as the main router, with a built-in WLC and a built-in WAP. The only other AP on the network right now, besides that is the 1832i. It's hard to tell if the problem exists with the built-in AP, the C1111, or the built-in WLC, because where the built-in AP is currently located, there is a very very weak signal from there to the client machine (hence the reason I have an 1832i installed). I did notice this a few times in the built-in APs logs but I am not certain what to make out of it.
Jan 26 03:50:08 kernel: [*01/26/2019 08:50:08.9525] chatter: client_ip_table :: ClientIPTable no client entry found, dropping packet 1C:4B:D6:F8:90:FD
Jan 26 05:50:56 kernel: [*01/26/2019 10:50:56.2025] chatter: client_ip_table :: ClientIPTable no client entry found, dropping packet 1C:4B:D6:F8:90:FD
Jan 26 08:29:37 kernel: [*01/26/2019 13:29:37.8824] chatter: client_ip_table :: ClientIPTable no client entry found, dropping packet 1C:4B:D6:F8:90:FD
Jan 26 08:32:13 kernel: [*01/26/2019 13:32:13.2724] chatter: client_ip_table :: ClientIPTable no client entry found, dropping packet AC:5F:3E:25:EE:A5
Jan 26 11:19:32 kernel: [*01/26/2019 16:19:32.4824] chatter: client_ip_table :: ClientIPTable no client entry found, dropping packet 1C:4B:D6:F8:90:FD
Jan 26 11:24:45 kernel: [*01/26/2019 16:24:45.9324] chatter: client_ip_table :: ClientIPTable no client entry found, dropping packet 1C:4B:D6:F8:90:FD
Jan 26 15:46:03 kernel: [*01/26/2019 20:46:03.4924] chatter: client_ip_table :: ClientIPTable no client entry found, dropping packet AC:5F:3E:25:EE:A5
Jan 26 17:05:28 kernel: [*01/26/2019 22:05:28.2424] chatter: client_ip_table :: ClientIPTable no client entry found, dropping packet 1C:4B:D6:F8:90:FD
Jan 26 17:44:00 FIPS: *** shell: FIPS Mode = disabled ***
Those MAC addresses do exist. The 1C:4B:D6:F8:90:FD is the wireless MAC address for the laptop that I am using (and the one that just displayed the problem before I displayed the log). My wife's cell phone is the AC:5F:3E:25:EE:A5 MAC address, and she also had some issues. She didn't remember the error message exactly, but said it had something to do about DHCP server and some IP address not existing anymore. She said she also has been having a hard time searching the internet on her cellphone, because of the same issues the laptop is displaying. I would think that perhaps those messages in the built-in WAPs syslog are related, however, these devices show that they're connected to the WAP1, not the built-in WAP0. That makes me wonder if the log error messages are related at all. Any suggestions on how to troubleshoot this or what those messages mean? Even stranger though, show arp on WAP0 does show the laptop's MAC address in it's ARP table, but it does not show my wife's. Thanks!
... View more
Hi! I am reading about private-VLANs and I think they might be the solution to my current issue. I currently have two VLANs, and two wireless SSIDs. VLAN1 (10.0.0.0 / 24) is mapped to the Company SSID, VLAN40 (10.0.40.0 / 24) is mapped to the Company's Guests SSID. I have a need for more networks though and I know I can just create more VLANs and more wireless SSIDs, but I'm trying to do it without creating anymore SSIDs. I see this when I google private-VLANs:
A private VLAN partitions the Layer 2 broadcast domain of a VLAN into subdomains, allowing you to isolate the ports on the switch from each other.
That sounds like something I could use. I was thinking maybe instead of creating multiple VLANs and SSIDs, I could partition the two VLANs I currently have and try to isolate the devices. For example, on the Company VLAN, only company equipment can be on it. We have some residential devices that need to be connected to the internet as well though, such as our car, garage door opener, game consoles, etc. I didn't want to put some of these on the guest network for various reasons.
I do not think access groups are a solution, because the wireless APs for the guests and the company stuff are the same APs. They're not in different buildings or anything. I have a Cisco C1111-8PW router, three Cisco 1832i wireless APs. The C1111 has a built-in WLC and AP.
Would the private-VLANs be the best way to go here? I was reading there was some way to do this with something called 802.1x authentication or something, but I'm having a hard time finding examples of how to configure something like this with the 802.1x authentication. Thanks.
... View more
@Alan Ng'ethe, It seems we think alike! As you was typing that, I posted how I think it's more beneficial to leave it open for testing purposes / troubleshooting later on. I didn't plan on disabling it, I wanted to try and understand why. I think I know though. I have a console connection, and I think that might have something to do with it. I figure when I supply a source address or interface name for ping, the IOS injects that IP address into the packet header there. But maybe it figures if I'm on the router's console port, I probably don't want ACLs to apply. If they did, maybe it could even break some of the IOS features. I'm not sure. So, I still have a VLAN issue and thought it was related enough to keep it in this thread, but maybe it's best to move it to a new thread. Anyways, here goes. So, now I have my two VLANs and two SSIDs properly working. VLAN1 (MyBusiness), which is the default VLAN, and VLAN40 (Guests) which is for guests. There's the two SSIDs, MyBusiness, and MyBusiness Guests. There are devices that will be connecting via wireless and I don't feel like they really belong to either of those two categories. For example, our TV set top boxes use ethernet for their source. I want TV to be segregated from the business stuff and from the guest stuff. There's also what I call IoT devices, like our car, and the garage door opener. Finally, game consoles. I think they should be isolated as well. I am trying to find a way to do this without creating more wireless SSIDs. I think private-VLANs is what I want...would that be correct? I feel I have a much more indepth understanding of VLANs, but the document on reading on Private-VLANs don't clear everything up for me. Are Private-VLANs something that I should use? That way, the gaming consoles can be on a private-VLAN and maybe communicate with each other, and then car and garage door opener will be on another VLAN but they cannot communicate with the gaming consoles, the DC's stuff, like the PDUs management port, and the HPEs management port, I feel they should be on a seperate VLAN all together. But then the previous devices I just talked about could all be on the same network, just in private-VLANs and not communicate with each other at all. Is there a better way to do this or am I thinking the right way? Thanks!
... View more
@Alan Ng'ethe, I came to the same conclusion as you and thought I had posted that, but things where a little hectic around here the other night, and I might had forgotten. Sorry to have you go through all the work there to test what I had tested. I was thinking being able to ping the various VLANs from the router itself is probably a good thing to have, for various testing purposes. I am going to accept the persons solution as the correct answer. I was reading an article on setting something else up on a Cisco device (it was an article on a Cisco site) and in this article, they only used the GUI, not the CLI, however, when they created the VLANs, there was a checkbox to disable inter-VLAN routing. It would be nice if I could find out if disabling it is an option, rather than adding a little overhead blocking it using ACLs. I do have one more issue related to VLANs and feel that this is probably the best place to ask. So I don't want to close the thread yet. Thanks!
... View more
**EDIT: I thought I was doing something wrong, because from the router itself, I could ping the various VLANs from the various VLANs. For example, ping 10.0.0.1 source vlan 40 will succeed. However, once I connect to the actual network and use a host device, I cannot. Is there a way to prevent the pings from working from the Cisco console as well? So ping 10.0.0.1 source vlan 40 will fail?
Here's my current access-lists:
Standard IP access list NAT_TRANSLATIONS
10 permit 10.0.0.0, wildcard bits 0.0.0.255
20 permit 10.0.40.0, wildcard bits 0.0.0.255
Extended IP access list 100
10 permit udp any any eq bootpc
Extended IP access list BLOCK_INTERVLAN_ROUTING
10 deny ip 10.0.0.0 0.0.0.255 10.0.40.0 0.0.0.255 (4 matches)
20 deny icmp 10.0.0.0 0.0.0.255 10.0.40.0 0.0.0.255
100 permit ip any any (2479 matches)
Extended IP access list NO_OUTFACING_SERVICES
10 deny tcp any any eq telnet (3 matches)
20 deny tcp any any eq 22 (342 matches)
30 deny tcp any any eq www (1 match)
40 deny tcp any any eq 443
50 deny tcp any any eq finger
60 deny tcp any any eq cmd
100 permit ip any any (11504 matches)
Extended IP access list NO_WEBCONFIG_SERVICES
10 deny tcp any any eq www (526 matches)
20 deny tcp any any eq 443 (168 matches)
30 permit ip any any (16776015 matches)
Extended IP access list sl_def_acl
10 deny tcp any any eq telnet
20 deny tcp any any eq www
30 deny tcp any any eq 22
40 permit ip any any
In the running-config, I do see a couple things that worry me. These in particular:
ip nat inside source route-map track-primary-if interface GigabitEthernet0/0/1 overload
ip access-list match-local-traffic
route-map track-primary-if permit 1
match ip address 197
set interface GigabitEthernet0/0/1
I am not sure if this was something I did a while back when I was trying to get NAT working, and just forgot to remove it, or where it actually came from and what it exactly does. I think the match ip address is trying to match to rule 197, which doesn't exist, as far as I can tell. Not sure what the match-local-traffic is doing. I'm wondering if it's safe if I remove those entries I just posted there...I'm trying to figure out what they mean but google hasn't been much help with the searching for the 197 thing. Thanks!!!!
... View more
@houtan haddadlarijani wrote:
All you need is an inbound access-list on either vlan 1 or vlan 40 to block the connection between these 2 subnets.
access-list 101 deny ip 10.0.0.0 0.0.0.255 10.0.40.0 0.0.0.255 access-list 101 permit ip any any
Could you help me understand this a little bit more? The way I understand it is: It's a standard access-list, with rule number 101. We are denying access to the 10.0.40.0 / 24 network if the source address is from the 10.0.0.0 / 24 network. I think I understand the 101 part. At first, I was confused how two access lists could share the same rule number. But I think I understand now. 101 is the group-name, and then we have two rules added to that group. Is that correct?
Also, with the permit ip any any access-list...Is there a way to do a deny ip any any access-list but before that, allow those networks to accept incoming / outgoing PATted traffic? The only reason I ask, I have the management port out-of-band, but I am always worried someone might gain access to it by me not setting these access-lists up correctly.
Finally, if I wanted to allow traffic from 10.0.0.5 / 24 host to 10.0.40.7 host, would this be the proper command? access-list 101 permit host 10.0.0.5 host 10.0.40.7 eq ?
access-list 101 deny ip 10.0.0.0 0.0.0.255 10.0.40.0 0.0.0.255
access-list 101 permit ip any any
int vlan 1
ip access-group 101 in
I think once I verify this solves the problem (and I truly believe the commands you shared will solve my issue), I think I am going to try working on setting up the other VLANs. I like the ability to name the access-lists, because it's easier for me to remember what I was trying to do or why they exist. I don't think I can do that with standard access-lists, but I know how with extended. I name the VLANs something that helps me remember as well. I believe there's a few other small things I need to setup. Right now, I can access the management ports on the router and WLC and AP, regradless of what my IP address. I want to lock that down, so only a certain IP can access them. I'll probably look into the DHCP server stuff a bit more, see if I can get the DHCP server to hand out a specific IP based on the devices MAC address.
Thank you for the help! From my internet searches, it originally sounded like I was going to have to use access maps and the examples I saw confused me a little. I didn't fully understand them, and your way is nice and clear. I will have more VLANs that I still need to setup, but I do not expect to have to change anything drastically. I think I can easily modify the 101 access-list you shared and do the same for the other networks / VLANs I will be blocking from the inter-VLAN routing.
... View more
I believe I figured it out now. I have the DHCP server setup on the router with the two pools. I forgot to modify my ACL rules. Now, I just need to figure out how to isolate the VLANs, however, I think that's for a different thread.
... View more
Hi! I have a Cisco C1111-8PW running 16.06.05 and I am trying to setup an extra VLAN for the first time. My current setup is like this:
Static Public IP on GigabitEthernet 0/0/1
VLAN1 on network 10.0.0.0 / 24
VLAN40 on network 10.0.40.0 / 24 The issue that I would like to deal with is that I can ping the 10.0.0.0 network from the 10.0.40.0 network and vice-versa. I want them isolated. I believe inter-VLAN routing is what is currently turned on, and I am not certain how to turn that off. If anyone else sees something wrong or thinks I could do something better with my running-config, please do not hesitate to mention it!
... View more
I've uploaded three files to make the thread a little cleaner. One shows the current running config of the router, one shows the start-up commands of the Wireless LAN Controller, and the final one shows the output of the show flexconnect group detail default-flexgroup.
I am not certain what I am doing wrong. I noticed if I connect to my "guest" network, I do receive an IP address from the WLC, but ipconfig /all in Windows shows the DHCP server is actually running on address 10.0.40.254, not 10.0.40.2. I am almost certain that I have the VLANs configured incorrectly. I can submit a drawing of the network topology with the various hardware if it helps.
It looks a little like this:
C1111-8PW with built-in WLC + AP0
HPE 5900AF-48G-4XG-2QSFP+ |
VLAN1 VLAN20 VLAN40
ENTERPRISE IOT GUESTS
10.0.0.0/24 10.0.20.0/24 10.0.40.0/24
I need the VLANs configured on the WLC and router as well, because my switch does not support POE, however, the router does. I think it would be best if I tried configuring the DHCP server on the router with three pools, one for each VLAN / network, but I am not certain how to configure it so people on the VLAN networks receive the addresses from the proper pool. I think that would be better than having a DHCP server running on the router, and one running on it's built-in WLC. I'd greatly appreciate any help at all! Thanks!!!!!
... View more
Hello! I've been reading a few documents here on setting up multiple SSIDs and networks on Cisco devices but I am having some issues. Currently, I want at least three VLANs, one called IoT, one called Enterprise, and one called Guests. I have a total of four wireless APs that I want setup, so when people move out of range with the first one, it will automatically connect them to the second one. I want all APs to share the same SSIDs, but right now, I've been only concentrating on getting the first AP setup. The first AP and the wireless network controller are built into my router, the Cisco C1111-8PW. I have a static public IP address setup on the router, interface gigabitethernet 0/0/1, and I can ping the outside world. I have setup a DHCP server on the router, which hands out IP addresses on the 10.0.0.x network, with a netmask of 255.255.255.0. The wireless network controller is assigned an IP of 10.0.0.2 and I can access it's web based config from the network or via the CLI. I have two SSIDs setup on the AP, we can pretend the first one is called SSID_1 and the second is called SSID_2. I can successfully connect to SSID_1, I receive an IP address in the 10.0.0.x range, I can ping the outside world, and everything is good there. However, it's the SSID_2 I am having trouble with. I want the SSID_2 on the 10.0.10.0 network, with a netmask of 255.255.255.0. I have created a DHCP pool on the WLC and assigned it to the SSID_2. I have also assigned the SSID_2 to VLAN 40. This is where I think I am having issues. When I connect to the wireless SSID_2, it shows the gateway address is 10.0.0.2, but I cannot ping 10.0.0.2 and I cannot reach the outside internet. I have a DHCP server running on the router which hands out the 10.0.0.x addresses to the wireless LAN controller and any device physically plugged into the router, and on the wireless LAN controller, I have a DHCP server setup to hand out addresses in the 10.0.10.x network. The DHCP server on the WLC is set so it hands out the WLC's IP address as the gateway address. I want to keep these two networks isolated, so people on SSID_2 cannot access stuff on the 10.0.0.x network. Is there any config files I could show and could someone please try help me figuring out what I have done wrong and how to fix it? Thanks!
... View more
I did figure this out a few days back but forgot to update the thread. I am having some issues with another problem I am attempting to solve and will create a new thread for that problem. Thanks and sorry about not updating the thread here!
... View more
I finally figured out where I was going wrong last night. I found a Cisco document that had a little bit different example. I had to uncompress the zip file on the tftp server. At that point, I was able to use the web based management to update it. I would still like to figure out how to get the backup image type on the WLC and AP to the same version as the primary. The backup is now the 184.108.40.206 instead of the 220.127.116.11. I also see, when I log into the AP and run show version:
AP Running Image : 18.104.22.168
Primary Boot Image : 22.214.171.124
Backup Boot Image : 126.96.36.199
Primary Boot Image Hash:
Backup Boot Image Hash:
AP Image type : MOBILITY EXPRESS IMAGE
AP Configuration : MOBILITY EXPRESS CAPABLE
1 Gigabit Ethernet interfaces
2 802.11 Radios
Radio FW version : ce271f0c3bd6087f274af2d1d72e15b7
NSS FW version : not available
I have had little luck searching the internet for what exactly that NSS Firmware stuff is. I cannot find anything on it. Can someone point me to a link describing what it is or explain it please? Finally, one final question, but perhaps I should create a new thread for it. When I boot up, near the end, before the SSIDs show, I'm presented on the console port with a prompt for the AP (NOT!!! the WLC), until a few minutes go by and then the boot process finishes. Almost like the boot process is trying to search for something, doesn't find it, and times out eventually. Here's a snippet of the boot log:
[*01/20/2019 18:05:36.0999] Failed to send msg to wcp/wcp_db.set_vlan_name_map
[*01/20/2019 18:05:36.1099] chatter: store_policy : NO action list not adding policy MyCompany
User Access Verification
Username: [*01/20/2019 18:05:37.1399] AP IPv4 Address updated from 0.0.0.0 to 10.0.0.3
[*01/20/2019 18:05:37.1499] send CAPWAP ctrl msg to the socket: Socket operation on non-socket
[*01/20/2019 18:05:37.1499] send_msg_to_capwap_sm: Capwap SM restart message send failed for message: 9
[*01/20/2019 18:05:46.1699] DOT11_CFG Radio Mode is changed from FlexConnect to FlexConnect
[*01/20/2019 18:05:46.1799] DOT11_CFG Radio Mode is changed from FlexConnect to FlexConnect
[*01/20/2019 18:08:39.4699] chatter: tohost_virtual :: ToHost: device 'virtual' went down
[*01/20/2019 18:08:39.5199] chatter: tohost_vlan0 :: ToHost: device 'vlan0' went down
[*01/20/2019 18:08:39.5599] chatter: tohost_vlan1 :: ToHost: device 'vlan1' went down
[*01/20/2019 18:08:39.6299] chatter: tohost_vlan2 :: ToHost: device 'vlan2' went down
[*01/20/2019 18:08:39.6799] chatter: tohost_vlan3 :: ToHost: device 'vlan3' went down
[*01/20/2019 18:08:39.7199] chatter: tohost_vlan4 :: ToHost: device 'vlan4' went down
[*01/20/2019 18:08:39.7699] chatter: tohost_vlan5 :: ToHost: device 'vlan5' went down
[*01/20/2019 18:08:39.8399] chatter: tohost_vlan6 :: ToHost: device 'vlan6' went down
[*01/20/2019 18:08:39.8999] chatter: tohost_vlan7 :: ToHost: device 'vlan7' went down
[*01/20/2019 18:08:39.9399] chatter: tohost_vlan8 :: ToHost: device 'vlan8' went down
[*01/20/2019 18:08:39.9899] chatter: tohost_vlan9 :: ToHost: device 'vlan9' went down
[*01/20/2019 18:08:40.0399] chatter: tohost_vlan10 :: ToHost: device 'vlan10' went down
[*01/20/2019 18:08:40.0899] chatter: tohost_vlan11 :: ToHost: device 'vlan11' went down
[*01/20/2019 18:08:40.1399] chatter: tohost_vlan12 :: ToHost: device 'vlan12' went down
[*01/20/2019 18:08:40.2199] chatter: tohost_vlan13 :Starting the Switchdriver...
After it shows the vlan's going down (I am not sure why there's so many VLANs, I only have the default and then one I'm trying to create myself). It's been like this even with the old firmware. Any ideas what's going wrong or how to fix it? Thanks!
... View more