Both of my feeds are on audio3.radioreference.com.
Feed goes down same time every night
- Thread starter squadman
- Start date
- Status
Yep, seriously!Everything is plugged into an Ethernet jack - TV, Blu-ray player, all PCs, etc. I prefer hard-wired Ethernet for a number of reasons. I do have a laptop, but I just connect it to an Ethernet jack when I need it on the network. Being single, there's no 'significant other' to gripe about Ethernet cables running across the room! :lol: And I rarely use a laptop outside ... I do have a smartphone, but I use my carrier's data connection since I never exceed the monthly data limit. No tablets. My main computer in the house is a custom-built tower.
LOL whatever floats your boat man.. Like I said I am definitely pro-hardwire for anything not designed to be portable.. I'm a computer tech and I have this in my basement..
But WiFi is definitely a necessary evil - even in commercial/enterprise situations.. I did the ethernet/laptop thing back in the day before WiFi (back when you were the man if you had a dual-channel 128k ISDN line, lol!), and it sucked. Plus there's tablets and phones - which while I also have unlimited carrier data, the wifi connection is better 99% of the time. And I happen to like sitting outside to work.
It just needs to be implemented properly and securely.Methinks me sees a pattern emerging here............
Last edited:
But WiFi is definitely a necessary evil - even in commercial/enterprise situations.. I did the ethernet/laptop thing back in the day before WiFi (back when you were the man if you had a dual-channel 128k ISDN line, lol!), and it sucked. Plus there's tablets and phones - which while I also have unlimited carrier data, the wifi connection is better 99% of the time. And I happen to like sitting outside to work.
There's no question that WiFi is a necessary evil and most people don't implement it properly/securely. I could implement it correctly, but at this point I just don't want to mess with it.
To keep this on topic, I didn't have any feed drops last night. I will keep at it with PingPlotter until something shows up. I agree that a pattern with audio3.radioreference.com is starting to emerge ... hopefully, more evidence of something will appear in the coming days.
Same here, no drops since 0909 yesterday. I've also started PingPlotter, so if something goes awry in the coming days we can see if there's any common denominators.
Well, woke up this morning and had another email saying my 1 feed went down again at 12:12am. First tims since Wednesday night that it was down. Checked feed PC, feed was still showing as running but was offline, rebooted PC and for now it's back online.
- Joined
- Dec 18, 2002
- Messages
- 575
FYI, you can go to RadioReference.com Broadcast Server to see if the encoding program on your computer is indeed connected to the incoming audio server for your feed (you can do the same for audio1 and audio9, the other two incoming servers).
Mine is still up with no further errors since 0909 Saturday. PingPlotter is showing a backbone hop in Denver (ae-21-52.car1.Denver1.Level3.net) with growing latency over 200ms since about 0900 this morning. It's had a bunch of pings over 400ms in the past few hours.. Not sure if there's anything to see there, but tbird does yours ping through that same hop by chance?
Last edited:
putterizer
Member
I've noticed some drops on my feed too. It dropped out long enough to trigger emails on 2/10, 2/15, and again early this morning.
My feed is on audio3.radioreference.com as well.
My feed is on audio3.radioreference.com as well.
Last edited:
Do me a favor.. Open a command prompt (Windows key+R, then type CMD and hit enter) and type TRACERT AUDIO3.RADIOREFERENCE.COM. It'll run a bunch of lines then say Trace Complete..
Right click in the command box and click Mark, then use the mouse to highlight the trace results. Press Enter to copy them, then paste them (CTRL+V) in a reply here. It should look like this (if you have any personally identifiable info in the result, such as an internal hostname or an IP that ends with anything but 1 in the first or second line, just edit it out, as it's not important)..
Code:
C:\Users\me>tracert audio3.radioreference.com
Tracing route to audio3.radioreference.com [174.37.110.68]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms pfsense.internal.foo.biz [10.9.8.1]
2 <1 ms <1 ms <1 ms 1.165.208.192.ruraltel.net [192.208.165.1]
3 1 ms 1 ms 1 ms p17n1.ruraltel.net [24.225.1.17]
4 9 ms 9 ms 9 ms 4.34.44.21
5 54 ms 51 ms 9 ms ae-21-52.car1.Denver1.Level3.net [4.69.147.99]
6 21 ms 21 ms 21 ms te1-5.bbr01.cf01.den01.networklayer.com [4.53.12
.22]
7 19 ms 19 ms 19 ms ae7.bbr01.cs01.den01.networklayer.com [173.192.1
8.168]
8 28 ms 28 ms 29 ms ae12.bbr02.eq01.dal03.networklayer.com [173.192.
18.138]
9 25 ms 25 ms 27 ms ae1.dar02.sr01.dal01.networklayer.com [173.192.1
8.213]
10 29 ms 28 ms 29 ms po2.fcr05.sr06.dal01.networklayer.com [66.228.11
8.223]
11 24 ms 24 ms 25 ms 174.37.110.68-static.reverse.softlayer.com [174.
37.110.68]
Trace complete.Thanks
Squadman and Chronic - and anyone else who has had this issue lately if you could also do this and post your results it would be great
Last edited:
putterizer
Member
Here is the result of me doing that.
Code:
Tracing route to AUDIO3.RADIOREFERENCE.COM [174.37.110.68]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms DD-WRT [192.168.1.1]
2 * * * Request timed out.
3 8 ms 12 ms 24 ms dtr01onlswi-tge-0-1-0-2.onls.wi.charter.com [96.
34.30.10]
4 9 ms 64 ms 10 ms crr01onlswi-bue-3.onls.wi.charter.com [96.34.19.
168]
5 16 ms 14 ms 18 ms crr01euclwi-bue-2.eucl.wi.charter.com [96.34.16.
145]
6 15 ms 16 ms 20 ms bbr01euclwi-bue-4.eucl.wi.charter.com [96.34.2.4
]
7 24 ms 13 ms 15 ms bbr02euclwi-bue-5.eucl.wi.charter.com [96.34.0.7
]
8 25 ms 30 ms 23 ms bbr01chcgil-bue-1.chcg.il.charter.com [96.34.0.9
]
9 29 ms 31 ms 30 ms prr01chcgil-bue-2.chcg.il.charter.com [96.34.3.9
]
10 27 ms 25 ms 24 ms xe-0-1-0.bbr02.eq01.chi01.networklayer.com [50.9
7.16.26]
11 33 ms 29 ms 35 ms ae7.bbr01.eq01.chi01.networklayer.com [173.192.1
8.170]
12 49 ms 53 ms 53 ms ae20.bbr01.eq01.dal03.networklayer.com [173.192.
18.136]
13 50 ms 48 ms 47 ms ae0.dar01.sr01.dal01.networklayer.com [173.192.1
8.211]
14 63 ms 76 ms 76 ms po1.fcr05.sr06.dal01.networklayer.com [66.228.11
8.221]
15 52 ms 53 ms 53 ms 174.37.110.68-static.reverse.softlayer.com [174.
37.110.68]
Trace complete.
My feed is showing on audio1.radioreference.com
Afraid not. Here's what PingPlotter caught for me overnight:
- less than 5 seconds of packet loss at po1.fcr05.sr06.dal01.networklayer.com (appears to be in Dallas, TX) at 3:07am this morning.
- less than 5 seconds packet loss at ae1.dar01.sr01.dal01.networklayer.com (appears to be in Dallas, TX) at both 8:28am and 8:48am this morning.
Like you, not much to see. RadioFeed says my feed stayed up the entire night.
A little bit of digging on these hostnames shows that other people have had issues with them too - especially gamers.
More monitoring will be done. We will get this figured out.
Yeah I've seen random packet drops at pretty much every hop over the course of the day, but nothing that has spanned more than one cycle or knocked me offline. I see you have one hop in common with putterizer.. But neither of what you listed are common to my route, and nothing in my route matches putterizer's either... You didn't post your entire route though, are there any others in common?
That hop in Denver is still showing high latency for me though, 3 pings over 450ms in the past hour.
I doubt there will be anything incriminating until one or both of our feeds goes awol again and we can match up timestamps in the log with the PingPlotter results..
That hop in Denver is still showing high latency for me though, 3 pings over 450ms in the past hour.
I doubt there will be anything incriminating until one or both of our feeds goes awol again and we can match up timestamps in the log with the PingPlotter results..
Last edited:
Has your feed been going offline? If so is it long enough to trigger emails? Is it going through long timeout-reconnect cycles like ours?
- Joined
- Dec 18, 2002
- Messages
- 575
Typically an encoder (RadioFeed, ScannerCast, etc) will report a timeout after the connection to our server has been interrupted for at least 30 seconds, shorter interruptions usually don't cause an issue.
Also, regarding feed offline e-mails, our servers check the online/offline status for feeds every 5 minutes, an e-mail will be sent only if a feed is offline for three consecutive checks. This means that if a feed goes offline only briefly (like for only a minute or two) or even if it goes offline for 12 minutes and then comes back online no e-mail notification will be sent.
Also, regarding feed offline e-mails, our servers check the online/offline status for feeds every 5 minutes, an e-mail will be sent only if a feed is offline for three consecutive checks. This means that if a feed goes offline only briefly (like for only a minute or two) or even if it goes offline for 12 minutes and then comes back online no e-mail notification will be sent.
Yeah we know how it works. The question is WHY are we getting these long strings of timeouts and reconnects, followed by long periods of uninterrupted streaming. It's definitely nothing at our end, and it seems to be unique to the audio3 server.
KD0TAZ, I apologize for not posting this earlier. Here's the entire route. The 'request timed out' is my cable modem:
Code:
[FONT=Courier New]1 <1 ms <1 ms <1 ms 192.168.1.1
2 * * * Request timed out.
3 9 ms 8 ms 9 ms 173-219-232-173-link.sta.suddenlink.net [173.219.232.173]
4 24 ms 25 ms 25 ms 173-219-232-143-link.sta.suddenlink.net [173.219.232.143]
5 25 ms 25 ms 26 ms te3-5.bbr01.eq01.wdc01.networklayer.com [206.126.236.185]
6 38 ms 44 ms 38 ms ae0.bbr01.tl01.atl01.networklayer.com [173.192.18.153]
7 60 ms 66 ms 58 ms ae13.bbr02.eq01.dal03.networklayer.com [173.192.18.134]
8 57 ms 63 ms 63 ms ae1.dar01.sr01.dal01.networklayer.com [173.192.18.255]
9 59 ms 55 ms 64 ms po1.fcr05.sr06.dal01.networklayer.com [66.228.118.221]
10 59 ms 59 ms 59 ms 174.37.110.68-static.reverse.softlayer.com [174.37.110.68][/FONT]N0YFE
Member
Network issues
The only thing I can think of is to assign each wired device it's own IP address that is outside of the DHCP pool. (My DHCP pool is .100 to .200 and all my wired devices have fixed ip below .100
For my wireless devices that stay in the house, I have reserved IP addresses though my router so they always get assigned the same IP address and it is tied to the devices MAC address.
I also have my DNS settings in the router set to use Google 8.8.8.8 and 208.67.222.222 instead of the DNS of my ISP.
I found most of this out when I added my NEST Thermostat and it would drop off the network for no reason at odd times and I could never figure out the exact cause, but these changes have kept it on line.
The only thing I can think of is to assign each wired device it's own IP address that is outside of the DHCP pool. (My DHCP pool is .100 to .200 and all my wired devices have fixed ip below .100
For my wireless devices that stay in the house, I have reserved IP addresses though my router so they always get assigned the same IP address and it is tied to the devices MAC address.
I also have my DNS settings in the router set to use Google 8.8.8.8 and 208.67.222.222 instead of the DNS of my ISP.
I found most of this out when I added my NEST Thermostat and it would drop off the network for no reason at odd times and I could never figure out the exact cause, but these changes have kept it on line.
Last edited:
jparks29
John McClane
DHCP or ISP dynamic IP renewal
- Status
