net/mpd5, ppp, proxy-arp issues

[Li, Qing]

Hi,

Recently there have been several reports regarding issues with ppp, mpd5
and proxy-arp configuration over the ppp links. I read through the
various postings and the problems seem to be:

1. Unable to add proxy-arp entries for the remote ppp clients.

2. Log showing "ifa_add_loopback_route: insertion failed" causing
some userland applications to fail.

May I ask that you try applying patch

http://people.freebsd.org/~qingli/ppp-proxy-arp-patch-121515.diff

and report back if the patch fixes your problems. And if not,
please describe what additional issues you are having.

Thanks,

-- Qing

_______________________________________________
freebsd...@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-current
To unsubscribe, send any mail to "freebsd-curre...@freebsd.org"

[Prokofiev S.P.]

Thank you !
The problem with proxy-arp has disappeared (FreeBSD 8-STABLE amd64 with
mpd5).

Please, somebody fix the bug kern/141285...

Li, Qing wrote:
> Hi,
>
> Recently there have been several reports regarding issues with ppp, mpd5
> and proxy-arp configuration over the ppp links. I read through the
> various postings and the problems seem to be:
>
> 1. Unable to add proxy-arp entries for the remote ppp clients.
>
> 2. Log showing "ifa_add_loopback_route: insertion failed" causing
> some userland applications to fail.
>
> May I ask that you try applying patch
>
> http://people.freebsd.org/~qingli/ppp-proxy-arp-patch-121515.diff
>
> and report back if the patch fixes your problems. And if not,
> please describe what additional issues you are having.
>
> Thanks,
>
> -- Qing
>
>
> _______________________________________________

> freeb...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net
> To unsubscribe, send any mail to "freebsd-net...@freebsd.org"

[Qing Li]

Have you seen this thread?

http://lists.freebsd.org/pipermail/freebsd-net/2010-April/025128.html

Quite a few fixes have gone into the -current and RELENG_8 branches.
Please try sync-up to the latest code before applying the patch.

-- Qing

On Sun, Apr 18, 2010 at 11:53 PM, Marin Atanasov <dna...@gmail.com> wrote:
> Hi,
>
> I was setting up mpd5 from ports, but this proxy-arp issue still exists in
> 8.0.
>
>> uname -r
> 8.0-RELEASE-p2
>
> I've attached the output from the mpd5 daemon, where you can still see that
> the issue is relevant.
>
> I've also tried to apply the patch, but it's no longer on that location.
> Something else to add - I've a dns server running on the same machine that
> mpd5 was set up. I'm not sure if this is caused by mpd5 daemon or the arp
> issue, but after a couple of start/stops of mpd5 the name resolving from the
> gateway machine is not possible, all other systems from the internal network
> are able to use the dns server on the gateway, but the gateway itself
> cannot.
>
> Restart of named, doesn't help either, so I had to completely reboot the
> machine, so that arp entries are flushed as well.
>
> Could you please have a look at the issue? If you need some additional
> information, please let me know.
>
> Regards,
> Marin

>> http://lists.freebsd.org/mailman/listinfo/freebsd-stable
>> To unsubscribe, send any mail to "freebsd-stabl...@freebsd.org"
>
>
>
> --
> Marin Atanasov Nikolov
> dnaeon AT gmail DOT com
> daemon AT unix-heaven DOT org

[Qing Li]

>
> I was using csup to track RELEN_8_0 branch. Currently I'm syncing to
> RELENG_8.
>
> If I understood you right, after getting the sources for RELENG_8, I need to
> apply the patch and then rebuild world?
>

You only need to rebuild the kernel.

-- Qing

[Stefan Esser]

Am 22.04.2010 20:43, schrieb Marin Atanasov:
> Hello,
>
> Thanks a lot for the patch, Qing!
>
> It works fine. However I've noticed one thing, after I start mpd5 and
> connect to my home network:
>
> kernel: WARNING: attempt to domain_add(netgraph) after domainfinalize()
>
> Not very sure if this is something to worry about or not?

There was a problem with the initialization order of network "domains",
which caused kernel crashes with ISDN+INET6 some two years ago. The
reason was, that there was an implicit assumption, that all domains
were initialized when the network interfaces are initialized, with
NULL dereferences if domains are added (and relevant to a device)
after the device has been initialized.

I debugged this problem and prepared a patch for discussion, which
later was committed by Max Laier (if memory serves me right). The
message was added in order to identify further situations, where
network domains are added after network interfaces have been
initialized. This message ought to be informational right now, since
the interface init is repeated whenever a network domain is added
as part of above mentioned patch. Init order should be fixed, if
this message is printed for compiled in drivers, but in case of a
kernel module (like netgraph) that adds a domain, it is unadvoidable
that the init order is reversed.

Perhaps the message should be made conditional on the start-up of
the kernel not having finished, or it should be completely removed,
since time has shown, that the init order is correct in general.

I'll remove that message (or make it conditional on "bootverbose")
unless there is opposition to this change ...

Regards, STefan

[Julian Elischer]

please do..

it's an unavoidable thing that domains added after boot
are done after boot completes :-)

> Regards, STefan

> _______________________________________________
> freeb...@freebsd.org mailing list
> http://lists.freebsd.org/mailman/listinfo/freebsd-net

> To unsubscribe, send any mail to "freebsd-net...@freebsd.org"