The documentation on HughesNet was not real clear, the fix was just to set back and watch it and when the field service guy came out to re-align the antenna I saw more.
Here is what I saw, not sure why it works that way but after looking a bit more and following some other trails it appears that the following happens: If you use a windows machine plugged into the HughesNet modem/router it assigns the machine a address from the 192.168.0.x block. But if you plug in a router it gives it a address in my case in the range of 100.119.x.x. If I plug a Linux box into it, it does the same thing, but if I spin up a Windows 7 VM on my ThinkPad X200 and plug it directly into the port on the modem AND allow windows to grab the nic, again it gives the windows box a 192.168.0.x address, if I let the linux host grab the nic card it gives it a 100.119.x.x addresss. As to DHCP, I thought I knew something about it, my router and other devices were NOT offering addresses, they were REQUESTING them from the HN modem. On the WAN side the router plugged into the HN modem still has to request a IP address using DHCP (static IP addresses are expensive on HN). I find it interesting that if it is a Windows device the HN box gives it a 192. 168.0.x address, but if it is a router plugged into the HN modem it gives out a 100.119.x.x address, same goes if it is a Linux box. Maybe they think that if you are at a level high enough to run Linux you get a routable address or assume that if it reports that it is Linux it is some variant of a router run- ning some variant of Linux, so the HN modem (of whatever DHCP server) gives out a public address rather than a 192.168.x.x address. The router needs to run the DHCP client and request a IP assignment from the HN box, or it will not talk, unless of course you have the info to set up a static IP. Yes, the OpenWRT router is only offering DHCP assignments on the LAN side of the house, on the WAN side it is asking for one. I am sorry if I was not clear on that. I had sat for 5 hours waiting for someone to appear the day before and was probably at a pretty good level of frustration with them, but that is not excuse for bad descriptions and clear information. So in summary, it appears that the HN modem will offer a 192.168.0.x address to a windows or windows like machine, if it smells like router (Linux in this case) it gets a 100.119.x.x address. Ahh yes, if you are using the 192.168.0.x block it will give you up to 5 assignments. Not sure why the limitation, so HN recommends that you run a separate router if you need more addresses. But the document- ation says that you must make sure that the LAN side uses a different subnet than 192.168.0.x because a address in that range will be given to the WAN port, that is why the 100.119.x.x assignment threw me for a loop. Thanks for the info guys and hope I have made it a bit less cloudy. I do not believe I have seen anything like that before, I do recall that my cable modem would hand out 192.168.x.x addresses, if you used it as the router, but if you plugged your router into it, you first had to go in and tell it that you were plugging a router into it, then you would get a public IP assigned to your router once you plugged the router in and rebooted the whole thing, perhaps they have made these a wee bit smarter. On Sun, Jun 29, 2014 at 1:40 PM, Mike C. <[email protected]> wrote: > > Message: 1 > > Date: Sat, 28 Jun 2014 18:21:41 -0700 > > From: Keith Lofstrom <[email protected]> > > Subject: Re: [PLUG] Hughes net > > To: Portland Linux/Unix Group <[email protected]> > > Message-ID: <[email protected]> > > Content-Type: text/plain; charset=us-ascii > > > > On Fri, Jun 27, 2014 at 12:07:49PM -0700, Chuck Hast wrote: > > > The new place I have moved to only has internet access via Huges > > > Net (ugh!) I am using a router behind their router/radio. According > > > to the info I have googled, this thing is supposed to assign addresses > > > in the 192.168.0.x address range with the router being 192.168.0.1 > > > It only allows for 5 IP assignments, so I have put a router running > > > OpenWRT behind it, I notice that it gives out a IP assignment of > > > 100.119.170.x with the GW being 100.119.170.1, also when I plug > > > a linux box into the device it gets a assignment in that block of > > > addresses. BUT when the field service guy plugged his windows > > > box into the Huges box it gave him a 192.168.0.x address, what > > > goes here? I googled this and all indicates that the box is supposed > > > to hand out 192.168.0.x addresses, there are several admonitions > > > that you need to make sure (for obvious reasons) that your local > > > router does not use the 192.168.0.x subnet due to the HughesNet > > > device using it as the default (I always change those things to some > > > other subnet because .0.x and .1.x are the most common defaults. > > > > > > Why does this device hand out 100.119.170.x addresses (looks like > > > routable addresses) to the linux box or the router but 192.168.0.x > > > addresses to the windows box? > > > > Have you worked through the steps in the "How to configure your home > network" article? http://customer.kb.hughesnet.com/Pages/1189.aspx > > Because until you do that there really isn't much help the PLUG mailing > list can offer you. Although many of us here, including myself have a lot > of experience with wired/wireless networks and OpenWrt, we're not Hughesnet > tech support and do not know the particulars of how they do things. > _______________________________________________ > PLUG mailing list > [email protected] > http://lists.pdxlinux.org/mailman/listinfo/plug > -- Chuck Hast -- KP4DJT -- Glass, five thousand years of history and getting better. The only container material that the USDA gives blanket approval on. _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
