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?
As Russell pointed out, stating your problem more clearly might be the first step to solving it. You need to learn something about dynamic host control protocol - DHCP - before you try to get the protocol working. You should not be passing any DHCP requests through OpenWRT, the OpenWRT router should be firewalling those off from the Hughes router, and running its own DHCP daemon on its internal ports. You should learn enough about the DCHP protocol to learn what ports to block on the OpenWRT firewall, and enough about OpenWRT to know how to do so. It may well be that the Hughes router/radio only responds to M$ DHCP request packets. I don't know the details of that, but I have seen this broken behavior in some airports. I'm sure there are folks who have figured out workarounds. I just avoid those airports. And communities without broadband optical fiber. Hughes may actively thwart your attempts by changing protocols. Satellite internet as currently implemented is fricking expensive, and they aren't likely to facilitate users with lots of machines; "If you have more than 5 devices, buy more service" is likely to be their policy. Keith -- Keith Lofstrom [email protected] _______________________________________________ PLUG mailing list [email protected] http://lists.pdxlinux.org/mailman/listinfo/plug
