Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 20 Oct 2000 21:34:35 -0400
From:      Paul Murphy <pnmurphy@home.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:  <39F0F2AB.C50E0E8D@home.com>
References:  <39EF5505.7B7C2BFD@tellurian.com> <04c701c03a0f$716181f0$6d0a280a@speedera.com> <39EF8AAD.94739B2B@tellurian.com> <06ba01c03a2e$f66625d0$6d0a280a@speedera.com> <39F08B52.2E598CC5@tellurian.com>

next in thread | previous in thread | raw e-mail | index | archive | help
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 !
> 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-questions" in the body of the message

 I could never manually config my cable modem for @home; it works if you
let DHCP config it. [ifconfig_ep0="DHCP" <- in rc.conf]
-- 
P. Murphy
Home: Lat 43.5584 Long -79.6502
Work: Lat 43.4277 Long -79.7077


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-questions" in the body of the message




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?39F0F2AB.C50E0E8D>