[Bug 206012] jail(8): Cannot assign link-local IPv6 address to a jail

2016-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=206012

Jamie Gritton  changed:

   What|Removed |Added

 Status|New |Open

--- Comment #3 from Jamie Gritton  ---
It wouldn't be too hard to automate the transition between
fe80:ifnum::dead:beef and fe80::dead:beef%ifname.  Jail uses inet_pton and
inet_ntop which aren't aware of this, but it looks like it could use
getaddrinfo and getameinfo which use the scope ID, or if_nametoindex and
if_indextoname which give me the number directly.

I would have to move this scope ID to/from the second and third octets in the
inet6 address, which is rather non-standard but I assume a long-standing
FreeBSD way of doing things.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"


[Bug 208001] After turning off the jail does not remove network routes

2016-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208001

Jamie Gritton  changed:

   What|Removed |Added

 CC||ja...@freebsd.org
 Status|New |Closed
 Resolution|--- |Works As Intended

--- Comment #3 from Jamie Gritton  ---
I suspect the problem lies in the "/24" of "re0|10.0.0.22/24".  Jail aliases
are almost always going to use the /32 netmask, which is the default if one
isn't specified.  From what I see of your netstat output, your primary address
is on the 10.0.0.0/24 subnet.  The only time you'd want a non-/32 subnet on a
jail is if your set aside a separate subnet used only for that jail.

Note this instruction from the "alias" section of ifconfig(8):
"If the address is on the same subnet as the first network address for this
interface, a non-conflicting netmask must be given.  Usually 0x is most
appropriate."

In any case, I was unable to reproduce this behavior.  I don't know all the
parameters of your setup, but it looks like you should just remove those
netmasks.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"


[Bug 208001] After turning off the jail does not remove network routes

2016-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208001

Vladislav V. Prodan  changed:

   What|Removed |Added

 Status|Closed  |Open
 Resolution|Works As Intended   |---

--- Comment #4 from Vladislav V. Prodan  ---
The problem is not the creation of an IP address, network mask, other than /32.
I can give some examples of network topology, when the IP jail need to assign a
subnet mask for the correct operation of the network protocols. For example, a
DHCP-server or Samba services (nmbd and winbindd)
The problem is in the removal of a route to this IP when you turn off the jail.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"


[Bug 208001] After turning off the jail does not remove network routes

2016-05-28 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208001

--- Comment #5 from Jamie Gritton  ---
Yes, of course there are cases where something besides a /32 is appropriate -
that is why jail(8) allows that.  However, as I mentioned it did appear that
you had violated the specification that an alias should be on a non-conflicting
netmask.

The fact remains that I am unable to reproduce your problem.  Perhaps I could
if I had your entire configuration - all jails, all other network setup.

jail(8) simply calls ifconfig(8) with "alias" to add IP addresses, and with
"-alias" to remove them - see the output of "jail -vc" and "jail -vr".  The
jail will not be removed if the "ifconfig ... -alias" command fails, which
implies that the command is succeeding.  Unless of course there actually is a
bug in the way jail(8) is running this program.  My guess is the command is
succeeding, but isn't removing some arp entry because the alias when
incorrectly specified when it was created.

If it's clear (from "jail -v") that the correct ifconfig commands are being
run, then this might be considered an ifconfig bug.  If the correct commands
aren't being run, then it could be a jail bug.

-- 
You are receiving this mail because:
You are the assignee for the bug.
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"


Re: [Bug 208001] After turning off the jail does not remove network routes

2016-05-28 Thread Allan Jude
On 2016-05-28 20:30, bugzilla-nore...@freebsd.org wrote:
> https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=208001
> 
> --- Comment #5 from Jamie Gritton  ---
> Yes, of course there are cases where something besides a /32 is appropriate -
> that is why jail(8) allows that.  However, as I mentioned it did appear that
> you had violated the specification that an alias should be on a 
> non-conflicting
> netmask.
> 
> The fact remains that I am unable to reproduce your problem.  Perhaps I could
> if I had your entire configuration - all jails, all other network setup.
> 
> jail(8) simply calls ifconfig(8) with "alias" to add IP addresses, and with
> "-alias" to remove them - see the output of "jail -vc" and "jail -vr".  The
> jail will not be removed if the "ifconfig ... -alias" command fails, which
> implies that the command is succeeding.  Unless of course there actually is a
> bug in the way jail(8) is running this program.  My guess is the command is
> succeeding, but isn't removing some arp entry because the alias when
> incorrectly specified when it was created.
> 
> If it's clear (from "jail -v") that the correct ifconfig commands are being
> run, then this might be considered an ifconfig bug.  If the correct commands
> aren't being run, then it could be a jail bug.
> 


I think that is actually the problem

ifconfig -alias
only accepts the IP address, not with the CIDR.

#ifconfig lo0 alias 10.0.0.1/24
#ifconfig lo0 -alias 10.0.0.1/24
ifconfig: 10.0.0.1/24: bad value

you want to do just:
#ifconfig lo0 -alias 10.0.0.1

So jail(8) needs to strip the /24 off when passing it to ifconfig -alias

-- 
Allan Jude
___
freebsd-jail@freebsd.org mailing list
https://lists.freebsd.org/mailman/listinfo/freebsd-jail
To unsubscribe, send any mail to "freebsd-jail-unsubscr...@freebsd.org"