Very Computer

by **TribeGuy1** » Sun, 21 May 2000 04:00:00

Hi,
I'm a system administrator of an ISP and have a network
consisting of various Window (98,NT) and BSDI Unix (running primary
DNS dns.ispnet.com 205.200.200.2) machines all connected to a 10baseT
hub. Attached to this hub is a Cisco router (205.200.200.1) to
connect the network to the Internet.
Recently, a customer brought his own FreeBSD4.0 server to join
our network (co-location service). He also has his own class C
address (ex. 204.100.100.xxx) and has set up his server to IP address
204.100.100.2 (server.domain.com) The server boots up fine and we can
ping its IP address and name successfully from the server itself but
that's it. Ping responds with "ping: sendto: No route to host"
whenever we try to ping an address outside his class C address and
therefore his server can't see our router on the network (different
class C address)
I've setup defaultrouter="205.200.200.1" in rc.conf but the
error "Network unreachable" is displayed on boot up of server. I've
also added our name servers to his /etc/hosts file but that didn't
help.
Can someone please tell me what I have to do in order to get
this FreeBSD4.0 server to be able to forward packets destined for the
Internet to our router on our class C.

Thanks for your help,
Shane

by **David Malo** » Sun, 21 May 2000 04:00:00

> Can someone please tell me what I have to do in order to get
>this FreeBSD4.0 server to be able to forward packets destined for the
>Internet to our router on our class C.

The FreeBSD machine needs an IP address on the same network as the
router, otherwise it has no way to know what interfact to try to
use. You could give the interface correct interface a second IP
address on your network - look for the bit about "alias" in
/etc/defaults/rc.conf

David.

by **r j huntingt** » Sun, 21 May 2000 04:00:00

: I'm a system administrator of an ISP and have a network
: consisting of various Window (98,NT) and BSDI Unix (running primary
: DNS dns.ispnet.com 205.200.200.2) machines all connected to a 10baseT
: hub. Attached to this hub is a Cisco router (205.200.200.1) to
: connect the network to the Internet.
: Recently, a customer brought his own FreeBSD4.0 server to join
: our network (co-location service). He also has his own class C
: address (ex. 204.100.100.xxx) and has set up his server to IP address
: 204.100.100.2 (server.domain.com) The server boots up fine and we can
: ping its IP address and name successfully from the server itself but
: that's it. Ping responds with "ping: sendto: No route to host"
: whenever we try to ping an address outside his class C address and
: therefore his server can't see our router on the network (different
: class C address)

It is highly unlikely that your customer's class C addresses are portable.
They are assigned to the County of Riverside (California) and there is
probably no way to route any portion of the allocation to Canada.

In other words, it won't work. You'll need to assign addresses from your
own netblock.

by **Raymond Doetje** » Thu, 25 May 2000 04:00:00

I'm sorry to have to say this: "Damn for an ISP you are *ing STUPID"

You see that both are on a different network and you never even thought
about advertising the routes!!! When he bought his IP addresses directly
from IANA then the ISP (YOU IN THIS CASE) is responsible for setting up
the routing for that network!!! If he has bought his subnet from an
ISP the routing has already been setup and requests will flow to that
ISP.

I can't beleive that an ISP doesn't even have any knowledge of routing
I'm sorry to say it this blund but perhaps you should go on a IP training
and also do a Cisco training.

Raymond

> Hi,
> I'm a system administrator of an ISP and have a network
> consisting of various Window (98,NT) and BSDI Unix (running primary
> DNS dns.ispnet.com 205.200.200.2) machines all connected to a 10baseT
> hub. Attached to this hub is a Cisco router (205.200.200.1) to
> connect the network to the Internet.
> Recently, a customer brought his own FreeBSD4.0 server to join
> our network (co-location service). He also has his own class C
> address (ex. 204.100.100.xxx) and has set up his server to IP address
> 204.100.100.2 (server.domain.com) The server boots up fine and we can
> ping its IP address and name successfully from the server itself but
> that's it. Ping responds with "ping: sendto: No route to host"
> whenever we try to ping an address outside his class C address and
> therefore his server can't see our router on the network (different
> class C address)
> I've setup defaultrouter="205.200.200.1" in rc.conf but the
> error "Network unreachable" is displayed on boot up of server. I've
> also added our name servers to his /etc/hosts file but that didn't
> help.
> Can someone please tell me what I have to do in order to get
> this FreeBSD4.0 server to be able to forward packets destined for the
> Internet to our router on our class C.

> Thanks for your help,
> Shane

by **TribeGuy1** » Sat, 27 May 2000 04:00:00

Thanks David. That's all it took to get the packets flowing out onto
the Internet.

Shane

>> Can someone please tell me what I have to do in order to get
>>this FreeBSD4.0 server to be able to forward packets destined for the
>>Internet to our router on our class C.

>The FreeBSD machine needs an IP address on the same network as the
>router, otherwise it has no way to know what interfact to try to
>use. You could give the interface correct interface a second IP
>address on your network - look for the bit about "alias" in
>/etc/defaults/rc.conf

> David.

Very Computer

router/gateway help needed

router/gateway help needed

router/gateway help needed

router/gateway help needed

router/gateway help needed

router/gateway help needed