Re: rpc.statd already ipv6 clean?

2019-09-27 Thread Rick Macklem
Bjoern A. Zeeb wrote: >On 27 Sep 2019, at 21:52, Rick Macklem wrote: > >> Mihir Luthra wrote: >>> Hi Rick, >>> Rick wrote: Although I'll admit it isn't something I am particularily fond of, FreeBSD likes utilities to build/work with only one of ipv4/ipv6. To do this, "#ifdef INE

公司整套资料出售，带对公账户银行账户能直接使用,Q546一68一663

2019-09-27 Thread midnightdreamer--- via freebsd-net
飘 ___ freebsd-net@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-net To unsubscribe, send any mail to "freebsd-net-unsubscr...@freebsd.org"

Re: rpc.statd already ipv6 clean?

2019-09-27 Thread Bjoern A. Zeeb
On 27 Sep 2019, at 21:52, Rick Macklem wrote: Mihir Luthra wrote: Hi Rick, Rick wrote: Although I'll admit it isn't something I am particularily fond of, FreeBSD likes utilities to build/work with only one of ipv4/ipv6. To do this, "#ifdef INET" and "#ifdef INET6" is applied to the code and

Re: rpc.statd already ipv6 clean?

2019-09-27 Thread Rick Macklem
Mihir Luthra wrote: >Hi Rick, >Rick wrote: >>Although I'll admit it isn't something I am particularily fond of, FreeBSD >>likes >>utilities to build/work with only one of ipv4/ipv6. >>To do this, "#ifdef INET" and "#ifdef INET6" is applied to the code and the >>Makefile is tweaked to define one or

Re: rpc.statd already ipv6 clean?

2019-09-27 Thread Mihir Luthra
> > > clnt_create() checks /etc/netconfig and tries all of the transport > protocols with the specified class which are listed there, and then > chooses the first usable one. So if IPv6 is available, "udp6" will > be used because it is before "udp". > > statd.c handles the bind addresses on t

Re: rpc.statd already ipv6 clean?

2019-09-27 Thread Mihir Luthra
Hi Rick, > Although I'll admit it isn't something I am particularily fond of, FreeBSD > likes > utilities to build/work with only one of ipv4/ipv6. > To do this, "#ifdef INET" and "#ifdef INET6" is applied to the code and the > Makefile is tweaked to define one or both of these. > (You can look a

Re: no network between jails and host with VNET on same interface

2019-09-27 Thread alexander lunev via freebsd-net
I have to add: if i configure same network (10.14.14.0/24) on jail0 interfaces in jails and igb1 on host, then host and jails can ping addresses in this network. But vlan interfaces in jail and on host (10.1.1.0/24) can't ping each other. ===  host =     [igb1

no network between jails and host with VNET on same interface

2019-09-27 Thread Alexander N. Lunev via freebsd-net
Hello everyone! I have a strange connectivity problem on jails with VNET networking. I've deployed a jail system with VNET networking on a server with FreeBSD 12.0-RELEASE-p10. Jails are working fine, can reach out outer network and each other, but there's no connectivity between host and jail

[Bug 239240] igb: TX(2) desc avail = 1024, pidx = 0 messages appear when the network card (igb/ixgbe/em) loses ethernet link

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=239240 --- Comment #20 from 76nem...@gmx.ch --- I am a little busy this week. I will apply the patches and test the system probably next week. Against what sources (FreeBSD 12_1?) should the patches be applied? Thanks -- You are receiving this

[Bug 240787] netgraph/ng_bridge: Replace NG_BRIDGE_MAX_LINKS with auto-incrementing (Unlimited) links

2019-09-27 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=240787 --- Comment #6 from l...@donnerhacke.de --- manpages review is "green" What are the next steps @Phabricator? -- You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug. ___