Social Feed
Ever since getting the Hopper3 over a year ago, I've put up with a periodic loss of connection to the internet. So this past weekend I did some troubleshooting and found out some interesting facts, at least for my setup.
I have a Hopper3 with a hardwired ethernet connection to my router and 1 Joey with a MoCA connection to the Hopper3.
The symptoms are: approximately 1 out of every 3 or 4 days, I find my Hopper with no internet connection. The Settings / Internet screen shows its not connected to my router nor internet.
The reason it's not connected is because the Hopper isn't successful in getting a valid address from my router / DHCP Server. So the Hopper is falling back to an APIPA address. (APIPA is an obscure standard for LAN devices to connect when there's no DHCP server. An address in the range 169.254.*.* is generated by the device). For whatever reason, the Hopper gives up on the DHCP server and uses this APIPA address which places the Hopper in its own little world with nobody on the LAN to talk to except the Joey.
I found that I can simulate this 3 or 4 day cycle by doing a "Reset Network". Every 3rd or 4th Reset, the Hopper decides to use an APIPA address. Sometimes it stays in this state for a couple of resets, but overall it fails to get a real DHCP address around 30% of the time.
I believe that when my Hopper does it's automatic "Daily Reset", it is cycling through this same pattern. When I'm off on a trip and try to use Dish Anywhere to access my home setup and it fails because my Hopper isn't connected, it will reconnect automagically in the next day or two.
Hopper Fix:
My Ethernet cable was plugged into the Upper ethernet port. I changed it to the lower port, and now every "Reset Network" command results in a valid DHCP-assigned IP address and a valid router / internet connection. (I did about 20 in a row).
The lower Ethernet port has a logical (Client) name of Hopper3-ETH0; the upper port is Hopper3-ETH1.
Are these ports supposed to be interchangable, and why are there two of them - maybe for use as a pass-thru for a second device in the area which needs a LAN connection? I don't think this is a hardware problem with my upper Ethernet port. The pattern is too predictable. I think it has something to do with the lower port having a lower logical Client name of -ETH0 than the upper -ETH1. Perhaps the firmware first tries to establish a connection in the sequence of the Client name interfaces, so when the first port it tries isn't the one being used, something times out or sets an error condition by mistake and it gums up the works for the valid port.
Joey Problem:
Although this fixed the APIPA problem for my Hopper, not so for the Joey. Every other time I did a "Reset Network" for the Joey, it generated a APIPA address. Worse yet, when it didn't use an APIPA address, it would hang on to an old DHCP address previously assigned by the DHCP server, even when the router / server had been reset and that was no longer it's assigned address!
I could eventually "force" the Joey's valid DHCP-assigned address through the Hopper and on to the Joey with a number of resets of both boxes, power-downs, cable unplugs etc. but these boxes should be robust and self-configuring!
Final Solution:
I set up fixed IP addresses for the devices. It turns out there are four MAC addresses in my setup:
Hopper3-br
Hopper3-ETH0 (lower port)
Hopper3-ETH1 (upper port which I'm no longer using)
Joey_MoCA
I defined the three that I'm using in my router's setup, and after a few "Reset Network"s on both the Hopper and Joey, unplugging and plugging network cables, both the Hopper and Joey consistently come back to their assigned fixed IP LAN addresses.
For my setup, it took both actions to fix the problem:
- Avoiding use of the Hopper's top Ethernet port
- Assigning fixed IP addresses
Meanwhile through all of these router resets, the other dozen connected devices (wireless and wired) in my home were perfectly happy having an IP address assigned to them by my DHCP server and running with it.
BTW, I thought I read in these forums that there was a "hidden" dialog / screen on the Hopper3 setup whereby you could assign a fixed IP address on the Hopper side. The fixed addresses I've assigned were done on the router side with the corresponding MAC addresses pointing to the Hopper's devices, which seems to be working OK.
I have a Hopper3 with a hardwired ethernet connection to my router and 1 Joey with a MoCA connection to the Hopper3.
The symptoms are: approximately 1 out of every 3 or 4 days, I find my Hopper with no internet connection. The Settings / Internet screen shows its not connected to my router nor internet.
The reason it's not connected is because the Hopper isn't successful in getting a valid address from my router / DHCP Server. So the Hopper is falling back to an APIPA address. (APIPA is an obscure standard for LAN devices to connect when there's no DHCP server. An address in the range 169.254.*.* is generated by the device). For whatever reason, the Hopper gives up on the DHCP server and uses this APIPA address which places the Hopper in its own little world with nobody on the LAN to talk to except the Joey.
I found that I can simulate this 3 or 4 day cycle by doing a "Reset Network". Every 3rd or 4th Reset, the Hopper decides to use an APIPA address. Sometimes it stays in this state for a couple of resets, but overall it fails to get a real DHCP address around 30% of the time.
I believe that when my Hopper does it's automatic "Daily Reset", it is cycling through this same pattern. When I'm off on a trip and try to use Dish Anywhere to access my home setup and it fails because my Hopper isn't connected, it will reconnect automagically in the next day or two.
Hopper Fix:
My Ethernet cable was plugged into the Upper ethernet port. I changed it to the lower port, and now every "Reset Network" command results in a valid DHCP-assigned IP address and a valid router / internet connection. (I did about 20 in a row).
The lower Ethernet port has a logical (Client) name of Hopper3-ETH0; the upper port is Hopper3-ETH1.
Are these ports supposed to be interchangable, and why are there two of them - maybe for use as a pass-thru for a second device in the area which needs a LAN connection? I don't think this is a hardware problem with my upper Ethernet port. The pattern is too predictable. I think it has something to do with the lower port having a lower logical Client name of -ETH0 than the upper -ETH1. Perhaps the firmware first tries to establish a connection in the sequence of the Client name interfaces, so when the first port it tries isn't the one being used, something times out or sets an error condition by mistake and it gums up the works for the valid port.
Joey Problem:
Although this fixed the APIPA problem for my Hopper, not so for the Joey. Every other time I did a "Reset Network" for the Joey, it generated a APIPA address. Worse yet, when it didn't use an APIPA address, it would hang on to an old DHCP address previously assigned by the DHCP server, even when the router / server had been reset and that was no longer it's assigned address!
I could eventually "force" the Joey's valid DHCP-assigned address through the Hopper and on to the Joey with a number of resets of both boxes, power-downs, cable unplugs etc. but these boxes should be robust and self-configuring!
Final Solution:
I set up fixed IP addresses for the devices. It turns out there are four MAC addresses in my setup:
Hopper3-br
Hopper3-ETH0 (lower port)
Hopper3-ETH1 (upper port which I'm no longer using)
Joey_MoCA
I defined the three that I'm using in my router's setup, and after a few "Reset Network"s on both the Hopper and Joey, unplugging and plugging network cables, both the Hopper and Joey consistently come back to their assigned fixed IP LAN addresses.
For my setup, it took both actions to fix the problem:
- Avoiding use of the Hopper's top Ethernet port
- Assigning fixed IP addresses
Meanwhile through all of these router resets, the other dozen connected devices (wireless and wired) in my home were perfectly happy having an IP address assigned to them by my DHCP server and running with it.
BTW, I thought I read in these forums that there was a "hidden" dialog / screen on the Hopper3 setup whereby you could assign a fixed IP address on the Hopper side. The fixed addresses I've assigned were done on the router side with the corresponding MAC addresses pointing to the Hopper's devices, which seems to be working OK.
8 Replies
·
6614 views
Staff member
HERE TO HELP YOU!
Cutting Edge
Sometimes a thread gets so many posts in it that is can cause issues for the server so that why today we introduce The Song Name Game Part 3!
So let the game continue!
The last song was added by Bobby who posted...
One Meat Ball - Andrews Sisters
CONTINUE ON AND HAVE FUN! WELCOME HOME TO SATELLITEGUYS.US!
Here are the original rules for the game as posted by WebbyDude back in 2006. http://www.satelliteguys.us/threads/68645-Song-Name-Game
Just name a song title and the band who performed it. The next person does the same thing, but needs to list a song title or band name which includes a word from the previous entry. Pick songs from any genre.
Example:
Long Live Rock and Roll -- Rainbow
Rainbow in the Dark -- Dio
Another example:
Ride the Lightning -- Metallica
Lightning Strikes -- Ozzy Osbourne
Get it?
An additional note: we all know that song titles, sometimes, use profane words. Because this is a family friendly website it is advised that you clean up that title up a bit. This is accomplished by using something like sh!t instead of the real word. Thanks....
So let the game continue!
The last song was added by Bobby who posted...
One Meat Ball - Andrews Sisters
CONTINUE ON AND HAVE FUN! WELCOME HOME TO SATELLITEGUYS.US!
Here are the original rules for the game as posted by WebbyDude back in 2006. http://www.satelliteguys.us/threads/68645-Song-Name-Game
Just name a song title and the band who performed it. The next person does the same thing, but needs to list a song title or band name which includes a word from the previous entry. Pick songs from any genre.
Example:
Long Live Rock and Roll -- Rainbow
Rainbow in the Dark -- Dio
Another example:
Ride the Lightning -- Metallica
Lightning Strikes -- Ozzy Osbourne
Get it?
An additional note: we all know that song titles, sometimes, use profane words. Because this is a family friendly website it is advised that you clean up that title up a bit. This is accomplished by using something like sh!t instead of the real word. Thanks....
68639 Replies
·
2679373 views
TWiT Tech Podcast Network
Time for another AWESOME video from the TWIT Network!
View: https://www.youtube.com/watch?v=EtLJGwEtyT0
Direct YouTube Link - Apple's All-New iPad mini
TWIT's Website
TWIT Live Feed
View: https://www.youtube.com/watch?v=EtLJGwEtyT0
Direct YouTube Link - Apple's All-New iPad mini
TWIT's Website
TWIT Live Feed
0 Replies
·
10 views
Lifetime Supporter
I know HipKat said that they were working on conversions but we got the official news yesterday right from Dish that starting next month all DMA's will be on the western arc, and all customers will be assigned to that. That's gonna mean a lot of customers around here aren't gonna get Dish unless there are exceptions. Too many mountains and trees.
175 Replies
·
5074 views
Howdy folks long time no write.
Issue(s): Horizontal transponders (esp. Weigel mux) breakup/mosaic/sputtering audio, JTV less so (but received perfectly up until a month or so ago.
Vertical is fine (Daystar). Up until recently couldn't even get any signal on Weigel Mux but JTV was perfect.
What I did to improve things: A slight westward move improved reception but only slightly (approx 72 on the micro HD, sorry no dB to post). I removed the 3-way C-Band splitter and used a 2-way to get a 1-2 db signal gain ( the power port goes to the Startrak - the micro HD doesn't have enough juice ! (1st clue) even after swapping the switching power supply it came with with a heftier linear 12 V supply (less RFI too !).
I have had issues with the uHD before signal breaking up that a reboot would clear up (clue #2 = dying tuner?) - FYI, I reinforced the IF input and removed all flux from the pcb completely with a Flux Removal Pen (MG Chemicals Cat No. 4140-P) which definitely makes a huge difference.
I went outside and pushed and pulled reflector slightly and no improvement. Pole (actually tower in yard - the neighbours love me..NOT) is plumb, checked with carpenters level. Dish was last peaked in 2017 or so, after overhauling 24" Von Weise, new Acme, fresh grease, etc. Focal length, f/d ratio etc meticulously adjusted. One panel has a tear so planning to repair that this weekend when my cousin comes over ( to help me out (old guy here) forecast calls for sunshine.
What has changed: My utility company has installed new high tension line poles (one smack dab in the middle of 101°W target! But they put it in last year and reception (of JTV (HOR) at least) was fine, BUT when they came out to transfer the wires over this year from the old (sawed in half) pole that's about when the troubles started (coincidence?), but again Daystar (VER) was fine. I always had this pole in the light of sight of 101° before with no issues. (fyi my zenith sat 74° is unobstucted, but can't test)
In the meantime Weigel mux is trying to break in MOSTLY in LATE at night (less cell usage?) (audio not video except for a frame here or there) so don't know what has changed with this mux which suddenly "woke up". I have never had to fuss with dish moves on this satellite ( the slightest move +/- motor clicks loses lock, wheres normally on C-band I can go significantly wider east or west and still have a strong signal ( have these gone "spot beam" or narrower somehow and what is the slight difference in Az listed on Lyngsat to 100.9° affect things ( isn't that the declination i.e. requiring a tweak of declination?).
Long story short (too late, ha), if I had another DVB-S2 box to try and / or a newer more stable PLL lnb ( I have been meaning to upgrade many a time but never got arround to it) I could determine if it's my antiquated receiving equipment, or my dish/feed alignment ( doubtful as it tracks everything from 55 °W to 133 ° W nicely.) or the dreaded 5G! (BUT only on HOR and not VER?).
I read another post where the OP (with his smaller 7.5 footer) played around with the illumination to peak desired transponder and reduce qrm on interfering/ stronger xpndrs (even on 103° W). So will play with that too - and cut away the RG-6 a and pull up a fresh section with new PPC and coax Seal. Open the throat cap see if any cobwebs are there and check servo operation (also changed in last maintence 10 years ago).
Finally, this will probably be the last chance I get to play with the BUD from the looks of it (providers leaving, auctioning off rest of spectrum imminent above 4.0 Ghz, and to keep the peace with neighbours so it would be nice to have that mux back for the long, cold and dark winters to comfort this old man before I call it quits and buy a VHF/UHF/FM Yagi and get MeTV, H&I from my Vermont local stations (checked at a friends today and they come in nicely - except ABC) .
Only one guy in town (Montreal) I may be able to get a receiver or PLL lnb from to try (RPS Sat) so hopefully with elimnate that as a possible culprit. Be nice to pick up a cheap or used PLL lnb to try w/o 5G BPF (money is tight )
Like others I couldn't care less about "tv" (well maybe just a liitle or a lot) it's the challenge that excites me , I can get MeTV other ways OTA (no pirate crap).
So what do you guys (and gals) think ?. p.s. I don't have a spectrum analyzer and there are def/ cell towers nearby (half a Km or so away).
Oh and time permitting will hammer out dings too and wire damaged mesh on one section for an extra dB or two. Hesitate to touch Declination, Elevation and pole mount but will play around with those a little too... Why is this mux for finicky suddenly ?(8psk, 5/6 fec, beamwidthetc.. man wish they went back to VER I think everthing would be fine! For the engineers out here does 5G QRM affect one poliarization (HOR) more than another (VER)? I understand the strong interference swamps out the input mixer/local oscilator in the hapless old C-band lnb (I think it at time affect KU too esp. LPB on 101°W KU - incidentally thos were weak or "gone' but are back almost at the time MeTV improved..hmm Terrestrial interference?
Any thoughts or suggestions ( cheap or free solutions please) greatly appreciated. Cheers.
p.p.s. Micro HD can't display Decades and Toons but records them fine so I can watch on another box/media player (Ali chip set issue). Another reason to upgrade.
Anybody interested in a nice C/KU system free ? (for next Spring/Summer 2027)
[Sami 10' mesh, Corotor II+, Eagle Aspen (very old) C-band lnb, Norsat Ku lnb, Channel Master C/Ku (H/V) switch, Startrak 400 Analog receiver w/ motor control, Geosat uHD DVD-S2, CW600S for Mpeg-2]
Issue(s): Horizontal transponders (esp. Weigel mux) breakup/mosaic/sputtering audio, JTV less so (but received perfectly up until a month or so ago.
Vertical is fine (Daystar). Up until recently couldn't even get any signal on Weigel Mux but JTV was perfect.
What I did to improve things: A slight westward move improved reception but only slightly (approx 72 on the micro HD, sorry no dB to post). I removed the 3-way C-Band splitter and used a 2-way to get a 1-2 db signal gain ( the power port goes to the Startrak - the micro HD doesn't have enough juice ! (1st clue) even after swapping the switching power supply it came with with a heftier linear 12 V supply (less RFI too !).
I have had issues with the uHD before signal breaking up that a reboot would clear up (clue #2 = dying tuner?) - FYI, I reinforced the IF input and removed all flux from the pcb completely with a Flux Removal Pen (MG Chemicals Cat No. 4140-P) which definitely makes a huge difference.
I went outside and pushed and pulled reflector slightly and no improvement. Pole (actually tower in yard - the neighbours love me..NOT) is plumb, checked with carpenters level. Dish was last peaked in 2017 or so, after overhauling 24" Von Weise, new Acme, fresh grease, etc. Focal length, f/d ratio etc meticulously adjusted. One panel has a tear so planning to repair that this weekend when my cousin comes over ( to help me out (old guy here) forecast calls for sunshine.
What has changed: My utility company has installed new high tension line poles (one smack dab in the middle of 101°W target! But they put it in last year and reception (of JTV (HOR) at least) was fine, BUT when they came out to transfer the wires over this year from the old (sawed in half) pole that's about when the troubles started (coincidence?), but again Daystar (VER) was fine. I always had this pole in the light of sight of 101° before with no issues. (fyi my zenith sat 74° is unobstucted, but can't test)
In the meantime Weigel mux is trying to break in MOSTLY in LATE at night (less cell usage?) (audio not video except for a frame here or there) so don't know what has changed with this mux which suddenly "woke up". I have never had to fuss with dish moves on this satellite ( the slightest move +/- motor clicks loses lock, wheres normally on C-band I can go significantly wider east or west and still have a strong signal ( have these gone "spot beam" or narrower somehow and what is the slight difference in Az listed on Lyngsat to 100.9° affect things ( isn't that the declination i.e. requiring a tweak of declination?).
Long story short (too late, ha), if I had another DVB-S2 box to try and / or a newer more stable PLL lnb ( I have been meaning to upgrade many a time but never got arround to it) I could determine if it's my antiquated receiving equipment, or my dish/feed alignment ( doubtful as it tracks everything from 55 °W to 133 ° W nicely.) or the dreaded 5G! (BUT only on HOR and not VER?).
I read another post where the OP (with his smaller 7.5 footer) played around with the illumination to peak desired transponder and reduce qrm on interfering/ stronger xpndrs (even on 103° W). So will play with that too - and cut away the RG-6 a and pull up a fresh section with new PPC and coax Seal. Open the throat cap see if any cobwebs are there and check servo operation (also changed in last maintence 10 years ago).
Finally, this will probably be the last chance I get to play with the BUD from the looks of it (providers leaving, auctioning off rest of spectrum imminent above 4.0 Ghz, and to keep the peace with neighbours so it would be nice to have that mux back for the long, cold and dark winters to comfort this old man before I call it quits and buy a VHF/UHF/FM Yagi and get MeTV, H&I from my Vermont local stations (checked at a friends today and they come in nicely - except ABC) .
Only one guy in town (Montreal) I may be able to get a receiver or PLL lnb from to try (RPS Sat) so hopefully with elimnate that as a possible culprit. Be nice to pick up a cheap or used PLL lnb to try w/o 5G BPF (money is tight )
Like others I couldn't care less about "tv" (well maybe just a liitle or a lot) it's the challenge that excites me , I can get MeTV other ways OTA (no pirate crap).
So what do you guys (and gals) think ?. p.s. I don't have a spectrum analyzer and there are def/ cell towers nearby (half a Km or so away).
Oh and time permitting will hammer out dings too and wire damaged mesh on one section for an extra dB or two. Hesitate to touch Declination, Elevation and pole mount but will play around with those a little too... Why is this mux for finicky suddenly ?(8psk, 5/6 fec, beamwidthetc.. man wish they went back to VER I think everthing would be fine! For the engineers out here does 5G QRM affect one poliarization (HOR) more than another (VER)? I understand the strong interference swamps out the input mixer/local oscilator in the hapless old C-band lnb (I think it at time affect KU too esp. LPB on 101°W KU - incidentally thos were weak or "gone' but are back almost at the time MeTV improved..hmm Terrestrial interference?
Any thoughts or suggestions ( cheap or free solutions please) greatly appreciated. Cheers.
p.p.s. Micro HD can't display Decades and Toons but records them fine so I can watch on another box/media player (Ali chip set issue). Another reason to upgrade.
Anybody interested in a nice C/KU system free ? (for next Spring/Summer 2027)
[Sami 10' mesh, Corotor II+, Eagle Aspen (very old) C-band lnb, Norsat Ku lnb, Channel Master C/Ku (H/V) switch, Startrak 400 Analog receiver w/ motor control, Geosat uHD DVD-S2, CW600S for Mpeg-2]
17 Replies
·
654 views
Interesting article about the work being done to develope an ATSC 3 converter box. Yes it does mention affordable.
www.tvtechnology.com
Pearl TV Issues Progress Report on Low-Cost 3.0 Converters in Advance of NAB Show New York
Group has secured lower pricing from key tech players to make less costly boxes available
www.tvtechnology.com
11 Replies
·
590 views
It's dead, they just don't know it yet. They killed it by forcing DRM on it, and that TOTALLY botched implementing it.
There is absolutely NO compelling reason for anybody to switch to ATSC3.0. They only want it as a total and complete money grab.
S
WHAT ABOUT THE INTERNET PART OF IT. NO ONE WANTS A BOX CONNECTED TO THE INTERNET EITHER.
It's dead, they just don't know it yet. They killed it by forcing DRM on it, and that TOTALLY botched implementing it.
There is absolutely NO compelling reason for anybody to switch to ATSC3.0. They only want it as a total and complete money grab.
Pub Member / Supporter
Lifetime Supporter
Love this guy's channel. Looks like Walmart has thrown in the towel when it comes to conventional car batteries.
I bought a new AGM battery from Walmart about a year ago, it is already needing replacing. I thought about just buying a regular battery but from what I've read, that might not be a smart move. Might check my Forscan program and see if I can change the battery type from AGM.
View: https://www.youtube.com/watch?v=awe7kY5nvdU
I bought a new AGM battery from Walmart about a year ago, it is already needing replacing. I thought about just buying a regular battery but from what I've read, that might not be a smart move. Might check my Forscan program and see if I can change the battery type from AGM.
View: https://www.youtube.com/watch?v=awe7kY5nvdU
20 Replies
·
293 views
Pub Member / Supporter
Susan Saint James, Emmy-Winning Star of ‘Kate & Allie’ and ‘McMillan & Wife,’ Dies at 80
Susan Saint James, the Emmy-winning actress who starred in "Kate & Allie," died Monday after being diagnosed with pancreatic cancer. She was 80.
variety.com
3 Replies
·
48 views
Lon.TV
Time for another AWESOME video from Lon Seidman of LON.TV!
View: https://www.youtube.com/watch?v=CFY_gHuMhUU
Direct YouTube Link - I Used AI to Replace Apps I Was Paying For
The Official LON.TV Website
Lon on Facebook
View: https://www.youtube.com/watch?v=CFY_gHuMhUU
Direct YouTube Link - I Used AI to Replace Apps I Was Paying For
The Official LON.TV Website
Lon on Facebook
0 Replies
·
26 views
My OTA is not working anymore. This started after the latest update. I have the OTA dongle with a OTA antenna that I've been using for years. My hopper does not recognize the dongle anymore and when I go to the OTA setting, it has a screen that says to plug a dongle into the USB. I tried unplugging and plugging back, in the same usb port and other ports. The Hopper does not recognize it. Anyone have same issue?
204 Replies
·
5666 views
Hi all. If you were using a single tuner USB OTA adapter that is no longer working, please PM me. Thanks. 
I have the dual tuner OTA adapter currently connected, but I have 2 of the single tuner OTA adapters that I can quickly connect - neither is seen by my H3.Hi all. If you were using a single tuner USB OTA adapter that is no longer working, please PM me. Thanks.
TWiT Tech Podcast Network
Time for another AWESOME video from the TWIT Network!
View: https://www.youtube.com/watch?v=UK11O-VoMBU
Direct YouTube Link - Security Now 1102
TWIT's Website
TWIT Live Feed
View: https://www.youtube.com/watch?v=UK11O-VoMBU
Direct YouTube Link - Security Now 1102
TWIT's Website
TWIT Live Feed
0 Replies
·
28 views