DragonFly BSD
DragonFly users List (threaded) for 2005-03
[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]

Re: DragonFlyBSD not in compliance with RFC 1122

From: Gary Allan <dragonfly@xxxxxxxxxxxxxxx>
Date: Wed, 16 Mar 2005 20:35:38 +0000

Matthew Dillon wrote:
:I ran into a problem today. I administer a machine that needs to sit on :two separate networks and The network :card is configured as:
: inet netmask 0xffffff00 broadcast
: inet netmask 0xffffff00 broadcast
: ether 00:10:5a:f7:6e:71
: media: Ethernet autoselect (100baseTX <full-duplex>)
: status: active
:The machine has a default route of
:(Public IP addresses replaced with private.)
:All is well except that is inaccessible from the Internet. A :quick RTFM reveals that I need to add a second default gateway but it :appears that this is not supported under FreeBSD 4 or DragonFly.

We definitely do not support multiple default gateways, but having two
internet-routable nets on the same interface ought to work as long as
your default router can deal with it. Make sure that net.inet.ip.forwarding is set to 1 (via sysctl) and then you need to
run some tcpdump's on that interface and check:

    (1) that the machine is receiving the ARP request to resolve
    (2) that the machine is responding to the ARP request.
    (3) that the machine is receiving the packet meant for
    (4) then see if the machine is replying to it (e.g. assuming it's a ping
	or something).  The reply should be going out your default route.
	(tell tcpdump to dump the MAC header too so you can be sure it is
	being sent to the box defined by your default route).

There are several issues involved here.

Matthew Dillon <dillon@xxxxxxxxxxxxx>

The router in question is a Cisco and is dropping the packets from that arrive on due to anti-spoofing rules. I was just hoping for an elegant solution. As I've mentioned I added a work-around with IPFW but I'm not pleased with it.

I was quite surprised that FreeBSD doesn't support this even in 5.3. I would have thought that the Zebra problem alone would be reason enough to implement it. DragonFly is obviously affected too.

(The Debian machines I administer would just require a "route add gw" to add the second default route.)

It's a problem that has gone unresolved in FreeBSD for over 18 months so I guess it doesn't affect enough people to be a priority. I was just wondering if it was planned for the ongoing DragonFly routing overhaul.



[Date Prev][Date Next]  [Thread Prev][Thread Next]  [Date Index][Thread Index]