Do you receive packets from 192.168.2.0/24 and 192.168.3.0/24 on igb1.2
and igb1.3 respectively?
Do you really need NAT? As far as I can see, you're looking for basic
static inter-VLAN routing.
Could you check the communication between 2.0/24 and 3.0/24 with
unloaded ipfw module (just to exclude ipfw from the investigation)?
I have a lot of installations of such scheme on em(4) and re(4) devices
-- no problems at all. Even maybe there was igb(4) devices too.
Sergey <KorG> Zhmylove
17.07.2017 0:31, O. Hartmann пишет:
Am Sun, 16 Jul 2017 23:14:41 +0200
Frank Steinborn <stei...@nognu.de> schrieb:
O. Hartmann <ohartm...@walstatt.org> wrote:
I have not have any success on this and I must ask now, to not make a fool out
self, whether the concept of having several vlan over one single NIC is
FreeBSD (12-CURRENT, as of today, r321055.
Since it is even not possible to "route" from a non-tagged igb1 to a tagged vlan
igb1.2 or igb1.66 (for instance) on the same NIC, I have a faint suspect that
doing something terribly wrong.
I think everyone working with vlan should have those problems, but since I can
find anything on the list, I must do something wrong - my simple conclusion.
What is it?
Do you have enabled net.inet.ip.forwarding?
Of course I have. As I stated earlier, ICMP pings from on VLAN to another over
router works, but any IP (UDP, TCP) is vanishing into thin air.
I don't have a FBSD-11-STABLE reference system at hand, so that I can check
revision/major release of the OS, but I work on that.
email@example.com mailing list
To unsubscribe, send any mail to "freebsd-current-unsubscr...@freebsd.org"