Re: Point-to-Point interfaces regressions

John Hay wrote:
On Fri, Sep 25, 2009 at 12:27:04AM -0700, Li, Qing wrote:
Li, Qing wrote:
Me and many other people running net/mpd handling thousands of PtP
interfaces sharing local addresses with each other and with some
Ethernet interface. This change makes such setup inoperable, as mpd
will constantly receive errors while trying to set addresses and
drop connections.
I can revert to the old behavior. I asked for feedback and
received
none at the time ...
I would like to see it working, but working correctly. If it is not
possible to implement it correctly - then reverted, or at least
disabled
by default.

Asking for compatibility is reasonable but the existing packet
leaking behavior is incorrect.

After reviewing the previous thread on this topic back in July,
I see that Henri Hennebert requested this feature for IPv6.

I intend to introduce a sysctl variable to control whether loopback
route should be installed for the local end point. By default
the old behavior maintained.

Ok. Will it fixed for 8.0-RELEASE?

What about only adding the route if it does not exist yet? That should
handle the common case of reusing your ip address on the ethernet
interface on the local side of point-to-point links.

Special care should be taken then on address remove, to not remove route
while the same address is still present on another interface. Also care
should be taken for the case, when address assigned to Ethernet
interface after PtP.

--
Alexander Motin
_______________________________________________
freebsd-net@xxxxxxxxxxx mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-net
To unsubscribe, send any mail to "freebsd-net-unsubscribe@xxxxxxxxxxx"

Relevant Pages

  • Re: Thinkpad wireless masquerade
    ... > and the ethernet to an attached hub so I can hook PCs to ... > On configuring the interfaces individually they work fine, ... > neither interface can ping from outside or in. ... > So what should the default route be and is it my only issue? ...
    (comp.os.linux.networking)
  • kgdb 2.0.5
    ... When using the ethernet interface, ... KGDB: Linux Kernel Source Level Debugger ... the questions about Ethernet network cards. ... +static int xlockholdcount = 0; ...
    (Linux-Kernel)
  • Re: Smoke em if you got em [Buffalo, W98SE, and you]
    ... Does this mean that I can kick the board ethernet into a higher priority and negate the need for the wireless? ... Change the metric on the 119 interface to something bigger like 500. ... route to all outside networks is using the wrong interface. ...
    (comp.sys.ibm.ps2.hardware)
  • Re: kgdb 2.0.5
    ... When using the ethernet interface, ... ++static int bufnum; ... ++static void kgdbeth_holdxlock ...
    (Linux-Kernel)
  • Re: Cross-over connection between hosts
    ... No, when the "ifconfig" command brings the interface up, it will ... add a route to that network only based on the netmask, ... ethernet hardware. ... My advice is to just go get a gigabit switch. ...
    (comp.unix.solaris)