Couldn't see this posted here even though it's 8 days old.
Has anybody used dNOS? Is it Vyatta like syntax? Where does this put VyOS in the open source networking world?
Wednesday, February 7, 2018
Tuesday, February 6, 2018
Anyone plan on getting the EVE-NG pro version coming out soon?
https://www.youtube.com/watch?v=aLZJXwZN0fk&t=1s
Trailer looks wicked, the dev's been putting some serious work into this thing. Worlds beyond VIRL and GNS3.
I heard from a source itll be like $100.
SD-WAN packet fixing & Optimisation,.. does it really work
Hi All, So I've been going back and forth with some people in my team over SD-WAN & Optimisation tech and wearing my Admin type hat,.. well tbh, I don't believe that it actually works as described. Far too many times I've been told about product bla that will do this amazing thing and make my life amazing & simple only for management of my workplace to fall for it, we put it in and then it does a mediocre job at best. Essentially we have one guy in our team who is pushing Silver-Peak massively (to the point where I think he must be getting a kick back) saying that it will make our Office 365 run so much better bla bla bla, however this guy has questionable knowledge on how the inner working of tech works and generally just know what current buzz works to say.
So mini rant over, does this stuff actually work? If i put in a silver peak router & server in azure will it somehow magically use less bandwidth when downloading files from SharePoint? Will it somehow make all of my emails smaller and allow us to de-dupe email traffic,.. even though said traffic is encrypted? Also the whole SD-WAN premise looks to be geared towards businesses with multiple offices that want links in-between them, however everything of ours is in the cloud so I don't really see any benefit with that. The only thing I can see is that it can repair dropped packets through parity information in the packets that did arrive. however thats not an issue that we really have.
So I guess what I'm asking is, does anyone use this stuff that can honestly tell me if it works as described who doesn't work for the company selling said product. Every review I've read that says it works all looks to be written by someone who works for the company of the product they are reviewing.
thanks in advance for anyone that has the time to comment.
Bought a router, Speeds over wireless abysmal, speedtest.net said something about port 8080
So, I'm assuming that port 8080 is somehow blocked, and to my knowledge port forwarding directs traffic to a specific computer.
I'm using this router, which I got for the new place, since it has to be in the main room, and it was attractive. So far I have to say I'm very unimpressed.
I'm not a network guru or anything, but I'm techy enough. This piece of shit is blocking 8080, which is basically option 2 for web traffic. 80 being the primary.
What gives? Is there a setting somewhere I can change? Port forwarding doesn't seem like the right choice. Only getting .29 of my 50 mb down right now. Getting full upload.
So confused.
Nat route-map question.
I'm trying to understand what the following command is doing:
ip nat inside source route-map MAP1 interface GigabitEthernet0 vrf INET overload
Here is route-map MAP1:
route-map MAP1 permit 10 match ip address NAT_LOCAL match interface GigabitEthernet0
Here's NAT_LOCAL ACL:
ip access-list extended NAT_LOCAL permit ip 192.168.1.0 0.0.0.255 any permit ip 10.0.0.0 0.0.0.255 any
And then there's also another route map:
route-map MAP2 permit 10 match ip address LOCAL set vrf INET
And LOCAL ACL:
(Bunch of (what looks like to me) random deny statements.) permit ip any any
And finally
VRF definition INET
and our Tunnel0 has "tunnel vrf INET"
So, my question is, are both route maps being applied? What I think is happening (please correct me if I'm wrong) is both route-maps are being applied, but the IP of the traffic depends on which map is applied? For example if a packet comes in that's not in the 192.168.1 subnet or the 10.0.0 subnet, the route map MAP1 will be applied?
Rant Wednesday!
It's Wednesday! Time to get that crap that's been bugging you off your chest! In the interests of spicing things up a bit around here, we're going to try out a Rant Wednesday thread for you all to vent your frustrations. Feel free to vent about vendors, co-workers, price of scotch or anything else network related.
There is no guiding question to help stir up some rage-feels, feel free to fire at will, ranting about anything and everything that's been pissing you off or getting on your nerves!
archive config from exec mode not working on Nexus 9k?
Working on a 9300 right now and I wanted to know how this works
The docs say that after you configure the archive, besides the periodic saves you can commit the config voluntarly with *archive config *
for me this is working only of I enter in the archvie config mode
switch(config)# archive config
^ % Invalid command at '' marker.
then this works
switch(config-archive)# archive config
switch(config-archive)#
here is my config
archive
path bootflash:
time-period 5
maximum 14
write-memory
Issue with Fiber Connection Between Dell N1548P and Dell 5548P
I have installed two new Dell N1548P switches and am running fiber back to my server room to a Dell 5548P. I am getting intermittent drops on both new switches, but one of them is really a problem child. It will lose connectivity completely unless I reboot it. The link on the 5548 end still shows good, and the optical diagnostic shows no loss of signal, but connectivity to it will just stop. I have tried switching the fiber connections with the other switch, which even though has intermittent drops, still works, and I get the same issue, no connectivity unless I reboot. I have not done any other configuration on these switches with the exception of getting their IP's on the network and joining them to a VLAN for our wireless. Is there anything I could be missing here? Some sort of loop I'm not seeing?
Aruba says it's the network: Wireless authentication timeouts
Hey, everyone, I've got a problem I've been working on for a bit and thought I'd toss it out here for any additional insight the community could provide. We have a basic hub-and-spoke network with all of our sites coming off the central data center across WAN links. All of the sites are set up the same way but I'm seeing an issue at one particular site. We are seeing wifi authentication timeouts from all client types at this site (chromebooks, iPads, iPhones, Windows 10 laptops) and the experience on the user side is it can take anywhere from 0 seconds to 5 minutes for a client to connect to wifi. We are using 802.11x certificate and PEAP authentication (to tie a user name to a client device). I've looked at our Clearpass (authentication server and seem timeouts occur at all sites but really only heard of complaints from this particular site. I've visited the site myself and it's the only site where I've been able to replicate the issue personally. If I try to connect, about half the time, I get a "network not available" and then I try to reconnect and it will work after one or several more tries.
I worked with Aruba (we have their wifi and Clearpass authentication server in production for wireless) tech support and we did a lot of troubleshooting. We compared configs of sites that work with the local controller at this site. I've replaced the local controller at the site. I've done iperf3 TCP and UDP tests across the WAN link to this site and compared those results to several of my other sites. I've compared switch and router configs from all sites. I've looked at routing tables, pings, MTRs, jitter, and latency. I've set up a simpler wifi SSID at the site that only uses PEAP to take certificates out of the mix and still have the issue on the simpler SSID. I've done simultaneous packet captures on the local router, the wireless lan controller, both routers in my data center (where the packets would need to travel to reach the authentication server) and finally, Clearpass (authentication server). After comparing these with Aruba support, we have been able to narrow down the problem to RADIUS UDP packets not getting back to the client and then that authentication session times out. From what I saw, the packets all reach the Clearpass server but when we see the timeout, the clearpass server just never sends the response back to the client. These packets go over UDP 1812 and what we should see is an access-request from the controller (on behalf of the client) and then an access-challenge from Clearpass. This goes back and forth until Clearpass either responds with an access-accept packet or an access-reject. When we see the timeout happen, Clearpass fails to send anything back during this process. So it might receive a access-request and then send an access-challenge back to the client and then another from each and then finally, the client will send an access-request and no access-challenge is sent back for that packet. Finally, that session times out and a log in Clearpass is generated for that session. Aruba just keeps saying this is a network issue (of course).
Finally, I did something to "fix" the issue, at least temporarily. What I did was fail all of the APs at this site over to our backup controller that is located in the data center. When I did this, we stop seeing the issue at the site and stop hearing complaints from users. This does nothing to change the topology but the only thing I can think of that changes is where the AP GRE tunnel drops the client traffic off. When the APs terminate to the local controller at the school, all wifi client traffic terminates there onto the local switch. When I fail the APs over to the WLC at the data center, wifi traffic gets dropped off there, they get a DHCP IP from the data center DHCP pool and then that authentication traffic goes straight from the WLC located in the data center over to the Clearpass server (in the same DC).
Here is a diagram showing the differences: DIAGRAM
This made me think our WAN provider might be dropping UDP traffic or something but again, I've done iperf3 tests on UDP 1812 and not dropped any traffic during those tests. The traffic would be tunneled through GRE across the WAN in the "working" configuration and just sent raw as UDP 1812 over the WAN link when I am seeing the issue. This theory contradicts what I'm seeing with Clearpass failing to send responses when I see requests on the packet capture hitting Clearpass, however.
I'm stumped of what to even try next. Any ideas? Sorry for the long post! Just wanted to include all of the details and thanks in advance for any replies to this thread!
"Modern" DHCP server?
Just wondering what you guys are using for your DHCP servers away from the corporate network (i.e. not Windows)?
It seems like a fairly trivial thing but we're deploying a new development environment and are coming up with custom provisioning tools for physical/virtual machines, iLOs, networking hardware etc yet can't find a DHCP server with any kind of database backend or API that can easily be managed via scripting tools/Ansible.
Anyone got any ideas?
I (briefly) looked at ISC's new Kea DHCP server but it doesn't seem very mature and has a lot of gotchas.
Subscribe to:
Posts (Atom)