nwjr.co.uk Report : Visit Site

Technical data of the nwjr.co.uk

Geo IP provides you such as latitude, longitude and ISP (Internet Service Provider) etc. informations. Our GeoIP service found where is host nwjr.co.uk. Currently, hosted in United States and its service provider is Tumblr Inc. .

HTTP Header Analysis

HTTP Header information is a part of HTTP protocol that a user's browser sends to called GSE containing the details of what the browser wants and will accept back from the web server.

DNS

HtmlToText

ranging from completely pointless to pretty useful. but mostly pointless. wednesday, 23 december 2015 is this the shortest ios command? is this the shortest ios command? xxxxx887#r % no open connections posted by nicholas richardson at 05:33 no comments: email this blogthis! share to twitter share to facebook share to pinterest friday, 22 may 2015 ios conundrum i haven't posted anything in a long time, despite this i have oceans of pointless material i could well waste time sharing with the world. today however i have stumbled across some very epic pointlessness on the cisco ios cli that demands to be shared. behold (all usernames and passwords very slightly changed): hostnamex(config)#username aussiesrus priv 3 secret thr0sn@gs0nbbq replacing <username aussiesrus priv 3 secret thr0sn@gs0nbbq> with <username aussiesrus priv 3 secret thr0sn@gs0nbbq> dear cisco, why? posted by nicholas richardson at 02:47 no comments: email this blogthis! share to twitter share to facebook share to pinterest labels: cisco , cisco ios thursday, 19 june 2014 hsrp and static route i don't use hsrp often, but it does fill a very handy gap in certain situations. i had a strange scenario recently with mulitple hsrp groups and a static route which wouldn't behave. we have two gateways, both "inside" interfaces have two hsrp groups, so that the client can load-balance a bit more effectively. here's a bad picture: the scenario is actually a bit more complicated than this in reality, but for the rough and ready sake of this post it will do. here is r1 and r2 fa 0/1 "inside" configuration: r1 interface fastethernet0/1 ip address 10.1.1.1 255.255.255.0 ip nat inside standby use-bia standby 1 ip 10.1.1.254 standby 1 preempt standby 1 track fastethernet0/0 20 standby 2 ip 10.1.1.253 standby 2 priority 99 standby 2 preempt standby 2 track fastethernet0/0 20 r2 interface fastethernet0/1 ip address 10.1.1.2 255.255.255.0 ip nat inside standby use-bia standby 1 ip 10.1.1.254 standby 1 priority 99 standby 1 preempt standby 1 track fastethernet0/0 20 standby 2 ip 10.1.1.253 standby 2 preempt standby 2 track fastethernet0/0 20 so that's fine isn't, we have r1 as "priority" for group 1 and standby for group 2 - vice versa for r2. note the "use-bia" command, this is required when, as cisco say, " controllers in low-end products can only have a single unicast media access control (mac) address in their address filter. these platforms only permit a single hsrp group, and they change the interface address to the hsrp virtual mac address when the group becomes active. load sharing on platforms with this limitation is not possible with hsrp." which is exactly what was happening - despite hrsp being completely aware of changed priorities, without use-bia multiple groups did not function. anyway, blah, blah. to the point, if there is one. due to a multiple vpn issue where we'd have both gateways establishing a session back to head-office it was decided not to load-balance the subnets on the other side of the vpn, so all clients must use the active group 1 virtual gateway 10.1.1.254 when sending traffic via vpn. so how to achieve this? well, i thought, first i will put a static route on r2 pointing the vpn subnet at the group 1 address: ip route 10.10.10.0 255.255.255.0 10.1.1.254 this works, but what happens when r2 becomes active for group 1, this static route will then have a next-hop of itself. what would happen, would it ignore the static route? it tried it, the static route persisted, though note i could not add additional static routes due to next-hop error (also please ignore the next-hop fa 0/0 on the default route, i wouldn't normally...): *jun 19 22:59:54.587: %hsrp-5-statechange: fastethernet0/1 grp 1 state standby -> active r2#show ip route gateway of last resort is 0.0.0.0 to network 0.0.0.0 1.0.0.0/24 is subnetted, 1 subnets c 1.1.1.0 is directly connected, fastethernet0/0 10.0.0.0/24 is subnetted, 2 subnets s 10.255.255.0 [1/0] via 10.1.1.254 c 10.1.1.0 is directly connected, fastethernet0/1 s* 0.0.0.0/0 is directly connected, fastethernet0/0 r2(config)#ip route 4.4.4.4 255.255.255.255 10.1.1.254 %invalid next hop address (it's this router) crucially of course it breaks the routing, this static route kills the path, i really wanted ios to be clever and ignore the command. this was the whole point of the post however its not all that great a point i suppose, just a curio. so anyway, what to do? i wanted to resolve this with static routes, but this "faulty" static needs to be removed when r1 outside interface is down, some fairly basic stuff could solve this. so an ip sla job first with a static route on r2 for the r1 wan address: ip route 1.1.1.1 255.255.255.255 10.1.1.1 ip sla 1 icmp-echo 1.1.1.1 source-interface fastethernet0/1 ip sla schedule 1 life forever start-time now track 1 ip sla 1 now a new static route for the vpn subnet tracking this sla job: ip route 10.255.255.0 255.255.255.0 10.1.1.254 track 1 and this of course worked fine, the static route was added and removed as required. now i need to think of better ways to do this, or is this the ultimate? (hahaha) posted by nicholas richardson at 15:34 2 comments: email this blogthis! share to twitter share to facebook share to pinterest labels: cisco , hsrp , ip sla , use-bia tuesday, 11 march 2014 sip-ua registration alarm eem script thing today i had yet another instance of eem script saving the day - or at least proposing a solution which might one day save the day. i desperately want to monitor a sip-ua registration on a cisco gateway, something was up with one of my gateways and it would spontaneously stop registering. and not start again, which is deeply not funny when you are on call gmt-time and they are in australia. the only solution was to remove reapply the sip-ua config, which turned out to be an ios bug, i believe. however going forward and moving on to the brighter, less-buggy future how could we monitor the trunk going down if this happened again? as it stood we relied on irate punters to sound the alarm - as we all know being forewarned of an impending angry caller is far more preferable to ignorance as you can magic up brilliant sounding diagnostic measures in advance (reboot it). was there a mib to show this status however so we could beat them to it? i couldn't find one. enter eem. step1. use event manager to run the “show sip-ua register status” command and run over each line looking for a regex match. the output would be: xx-xx-2911#show sip-ua register status line peer expires(sec) reg survival p-associ-uri ================================ ========== ============ === ======== ============ 1xx437 -1 2194 yes normal so our script could look like this (if like me you have hashed it together from far more intelligent posts than this): event manager applet trunk event none action 100 cli command "en" action 200 cli command "show sip-ua register status" action 250 foreach line "$_cli_result" "\n" action 300 regexp "1xx437(.*) no " $line action 400 if $_regexp_result eq "1" action 600 syslog msg "the trunk is down" action 700 end action 800 end note the white spaces in action 300, unless you want to match the "no" of "normal" you are going to need them". i would change the event to a cron timer running every so often, 5 minutes or so should do it. to test the reverse, say the trunk is up, change action 300 to “yes” and see the result,: xx-xx-2911# mar 12 06:27:20.812 wst: %ha_em-6-log: trunk: the trunk is down ß really means up finally add in an action 601 to send the monitoring solution of your choice a custom trap, if the result is positive, and yes we have an alarm should sip trunk not be registered. happy days. posted by nicholas richardson at 16:04 no comments: email this blogthis! share to twitter share to facebook share to pinterest labels: cisco , embedded event manager , sip trunk sip-ua status snmp , sip-ua sunday, 29 december 2013 embedded event manager suicide i often use the cisco

URL analysis for nwjr.co.uk

http://www.nwjr.co.uk/2013/
http://www.nwjr.co.uk/2015/12/is-this-shortest-ios-command.html
http://www.nwjr.co.uk/search/label/python
http://www.nwjr.co.uk/2013/10/
https://add.my.yahoo.com/content?url=http%3a%2f%2fwww.nwjr.co.uk%2ffeeds%2fposts%2fdefault
http://www.nwjr.co.uk/search/label/bgp
http://www.nwjr.co.uk/search/label/hsrp
http://www.nwjr.co.uk/search/label/ccnp
http://www.nwjr.co.uk/2013/02/how-to-get-ppp-subscribers-into-mpls.html
http://www.nwjr.co.uk/search/label/linux
http://www.nwjr.co.uk/search/label/gns3
http://www.nwjr.co.uk/search/label/serverlove
https://www.netvibes.com/subscribe.php?url=http%3a%2f%2fwww.nwjr.co.uk%2ffeeds%2fposts%2fdefault
http://www.nwjr.co.uk/search/label/vrf
http://www.nwjr.co.uk/2014/

Whois Information

Whois is a protocol that is access to registering information. You can reach when the website was registered, when it will be expire, what is contact details of the site with the following informations. In a nutshell, it includes these informations;

Domain name:
nwjr.co.uk

Data validation:
Nominet was able to match the registrant's name and address against a 3rd party data source on 10-Dec-2012

Registrar:
123-Reg Limited t/a 123-reg [Tag = 123-REG]
URL: http://www.123-reg.co.uk

Relevant dates:
Registered on: 19-Sep-2009
Expiry date: 19-Sep-2019
Last updated: 12-Sep-2018

Registration status:
Registered until expiry date.

Name servers:
ns.123-reg.co.uk 212.67.202.2
ns2.123-reg.co.uk 62.138.132.21

WHOIS lookup made at 04:45:08 28-Nov-2018

--
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:

Copyright Nominet UK 1996 - 2018.

You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REFERRER http://www.nominet.org.uk

  REGISTRAR Nominet UK

SERVERS

  SERVER co.uk.whois-servers.net

  ARGS nwjr.co.uk

  PORT 43

  TYPE domain

DOMAIN

SPONSOR
123-Reg Limited t/a 123-reg [Tag = 123-REG]
URL: http://www.123-reg.co.uk
Relevant dates:

  CREATED 19-Sep-2009

  CHANGED 12-Sep-2018

STATUS
Registered until expiry date.

NSERVER

  NS.123-REG.CO.UK 212.67.202.2

  NS2.123-REG.CO.UK 62.138.132.21

  NAME nwjr.co.uk

DISCLAIMER
This WHOIS information is provided for free by Nominet UK the central registry
for .uk domain names. This information and the .uk WHOIS are:
Copyright Nominet UK 1996 - 2018.
You may not access the .uk WHOIS or use any data from it except as permitted
by the terms of use available in full at https://www.nominet.uk/whoisterms,
which includes restrictions on: (A) use of the data for advertising, or its
repackaging, recompilation, redistribution or reuse (B) obscuring, removing
or hiding any or all of this notice and (C) exceeding query rate or volume
limits. The data is provided on an 'as-is' basis and may lag behind the
register. Access may be withdrawn or restricted at any time.

  REGISTERED no

Mistakes

The following list shows you to spelling mistakes possible of the internet users for the website searched .