Date: Fri, 20 Oct 2000 12:44:19 -0600 (MDT) From: Nick Rogness <nick@rapidnet.com> To: Marko Ruban <marko@tellurian.com> Cc: FreeBSD questions <freebsd-questions@freebsd.org>, freebsd-hackers@freebsd.org Subject: Re: Routing issue with cable modem Message-ID: <Pine.BSF.4.21.0010201218360.55477-100000@rapidnet.com> In-Reply-To: <39F08B52.2E598CC5@tellurian.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Fri, 20 Oct 2000, Marko Ruban wrote: > I tried replicating my windows routing table in freebsd. > Only one entry didn't work... (guess) > "route add default 10.17.56.xx" > > I'm cursed ! My guess guess would be your DHCP client is not working right. Is it suppose to be using DHCP? Is it really something else like PPPoE? You see, the problem is not that the network is unreachable. It is that the default network is not DIRECTLY reachable. This is a violation of basic routing principles...although many devices work with that setup (Windows,Cisco,etc). FreeBSD does not allow you to add a default route to a network that is not directly connected. Why don't you dump your windows routing table `route -print` to the list and we could put together a routing table for you or see what is acutally going on. > read below .... > > > > > > Goal -- to add cable modem as the default gateway to internet. > > > > > Symptom -- "add net default: gateway 10.17.56.XXX: Network is > > > > > unreachable" > > > > > Problem -- I think modem gateway cannot be added because it's on a > > > > > different subnet then my NICs. > > > > > Attempted -- aliasing ed0 to modem subnet.... all 10.17.56 IPs seem to > > > > > be occupied. > > > > > > > > It does sound like routing- > > > > A gateway, by definition, has to be on the same network as your NIC. > > > > I'm guessing your cable modem is in bridging mode? (vs routing mode) > > > > > > What would that mean in terms of my config changes ?? > > > So is the cable modem in this computer, or is it some standalone device? > > The cable modem is an external device. It is connected to one of my two NICs. > The other NIC has been connected to a small LAN for a while (which worked > perfect with dialup PPP and NAT). And it is also connected to the TV cable and > a phone line. The uplink is handled automatically by the modem. > > > > > So it's presenting itself as some IP right? > > > > And you just have to use this IP as the default gateway for all your > > other > > > > machines- > > > > > > > What is the subnet masking in place here? > > > > > > The modem works fine on my windows machine, and I looked up the > > configuration > > > there (winipcfg). > > > Windows sets 10.17.56.XXX as the default gateway (and DHCP server), and > > assigns > > > 208.59.162.XXX (subnet 255.255.255.0) to me. DNS server is set to > > 207.172.3.9. > > > > > > Seems like should be no difficulty setting up unix in the same way... but > > unix > > > does like 10.17.56.XXX as gateway (because supposedly network is > > unreachable). > > > > > > So that's the story... any suggestions? > > > > Ok, so the machine is being given a 208.59.162.xxx IP address (via DHCP), > > and a default gateway of 10.17.56.xx. > > > > Ok I think I know what's going on- > > > > Try manually adding the default route, but specify the interface that you > > want to use. > > It's something like: > > > > "route add default 10.17.56.xx netmask 255.255.255.0 interface ed0" > > "route add default 10.17.56.xx -netmask 255.255.255.0 -interface ed0" did not > work, probably because 10.17.56.xx was specifying a gateway for the network > 0.0.0.0 and ed0 was trying to be a gateway as well. I can however "route add > default -interface ed0" which is actually the closest I've gotten to it working > (modem dials out when I ping 10.17.56.1). > > "route add default 10.17.56.xx" would not work under any circumstances :( > tells me "Network is unreachable". I just wonder how windows has no problem > adding it as gateway. > > > I think that because the machine doesnt have an interface on the 10.x.x.x > > network, it doesn't know how to get to the 10.x.x.0 network. > > > > I think you alternately could add a static route that looks like this: > > > > "route add 10.0.0.0 208.59.162.xx" > > When route to 10.0.0.0 is added, outgoing packets are corrupted (checked with > ethereal). I.E. the header of the packet has 4 bytes inserted between the > source and destination MACs. Those 4 bytes always seem to be part of the > destination MAC itself. > > > Following from another reply..... > >>>>>>>>>>>>>>>>>>>>>> > >> > > defaultrouter="10.17.56.12" #<-- fails with symptom previously > described > >> > > >> > DHCP will normally configure the default route for you -- try setting > >> > this to NO. > >> > >> Tried setting to NO... DHCP doesn't seem to add a default route, so in my > case it > >> makes no difference really. > >> Should it add default route? > > > >Normally, yes. You sort of need default route and netmask in order to > >make things work. This should happen with the stock dhclient.conf > >(which is empty). You could try to run dhclient by hand, something > >like: > > > > # killall dhclient > > # dhclient -dD ed0 > > > >Or whatever your interface is. Terminate it with Ctrl+C. You should > >get a bunch of files in /tmp, containing values received from the > >server. You may also get some interesting error messages. > > Tried "dhclient -d -D ed0".... no files are written to /tmp dir. > Do you think it could be a problem with my dhclient ? > I tried using wide-dhcp client earlier, with even less success. > > Marko > > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-hackers" in the body of the message > Nick Rogness - Drive defensively. Buy a tank. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-hackers" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.BSF.4.21.0010201218360.55477-100000>