Skip site navigation (1)Skip section navigation (2)
Date:      Mon, 12 Jun 2000 02:09:54 -0400
From:      Ben Williams <williamsl@home.com>
To:        "Raymundo M. Vega" <RaymundoVega@home.com>
Cc:        FreeBSD-Questions@freebsd.org, Jahanur R Subedar <jahanur@jjsoft.com>
Subject:   Re[2]: network setup
Message-ID:  <1590.000612@home.com>
In-Reply-To: <39412435.671FB8C1@home.com>
References:  <39412435.671FB8C1@home.com>

next in thread | previous in thread | raw e-mail | index | archive | help
   Hrm ... the problem here is my ISP gave me those (CCC.DDD.78.61 = gw,
CCC.DDD.78.62 = my_host, 255.255.255.252 netmask) numbers. That part
of the setup actually went pretty well when I got a supported NIC in
the box. While I found drivers for the dm NIC (the one C|Net's
selling) apparently either the card didn't want to co-exist with two
pn's or the driver was/is buggy. I actually have the .62 machine
talking to .61 and the rest of the world through it. My next problem
is the 64 IP block I got that starts on 144 and runs to 207 .. my
FreeBSD boxes want a /26 to end on 209, though if I specify '...
broadcast CCC.DDD.72.207' it will let me set up an apparently non-CIDR
block of IP's.
   The current situation is basically "it was a bad/unsupported NIC,
my gw problem is fixed now."  I am still interested in learning how
to route traffic in & out of each NIC based on something like OSPF or
BGP or the like. Any clues there?

Thanks to Jahanur R Subedar and Raymundo M. Vega for sending me
pointers and helping me get this fixed.

--Ben Williams
mailto:received@email dot com

Quoting Raymundo M. Vega                                Monday, June 12, 2000
> Ben Williams wrote:
>> 
>>    I tried this last week when I was on-site and I couldn't get out
>> when I had .61 as the default route. Here's a copy of what I did (from
>> memory):
>> # ifconfig pn0 down
>> # route delete default (the old ccc.ddd.25.1 route)
>> # ifconfig dm0 ccc.ddd.78.62 netmask 255.255.255.252 media 100baseTX mediaopt full-duplex up
>> # route add default ccc.ddd.78.61
>> ( I actually `script /var/tmp/ifconfig_script`ed this but I lost it
>> and wont be able to redo it till I get back up on-site)
>> # ping -c10 ccc.ddd.78.61
>> 100% Packet loss.
>> # ping -c10 w.x.y.z  (an IP outside the network I'm working at)
>> 100% Packet loss.
>> # route delete default
>> # ifconfig pn0 aaa.bbb.25.2 netmask 255.255.255.248 up
>> # route add default aaa.bbb.25.1
>> and here things work and so they sit.
>> 
>>    Can anyone see something I did wrong? To recap my goal is to have
>> two links to the net (aaa.bbb.25.1 and ccc.ddd.78.61) on their own
>> NIC's (pn0 and dm0) with a "third" NIC (pn1) pointing the the
>> "internal" (real IP's, not FUA) hosts on the network.
>> 
>> --
>> Ben.
>> Quoting Raymundo M. Vega                                Sunday, June 04, 2000
>> RMV> Ben Williams wrote:
>> >>
>> >> This is from one of my ISP's:
>> >>
>> >> > aaa.bbb.78.62 netmask 255.255.255.252
>> >> > gateway should be aaa.bbb.78.61
>> >>
>> >> Is this possible? If so how? AFAIK .61 is the network address for that
>> >> subnet...
>> 
>> RMV> no .61 is the address of the default gateway, login as root and give
>> RMV> the commands:
>> 
>> RMV> ifconfig <int_name> aaa.bbb.78.62 netmask 255.255.255.252
>> RMV> route add default aaa.bbb.78.61

> My mistake, netmask should be 250 on the last byte.

> sorry

> raymundo.

>> 
>> 1. This didn't work for me. (See above)
>> 2. You can only have one default route and I want to keep both lines
>> connected...
>> RMV> good luck
>> 
>> RMV> raymundo
>> 
>> --Ben Williams
>> mailto:received@email dot com


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




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?1590.000612>