Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NAT failure with 16.1 on Hyper-V #734

Closed
andreas-p opened this issue Feb 1, 2016 · 12 comments
Closed

NAT failure with 16.1 on Hyper-V #734

andreas-p opened this issue Feb 1, 2016 · 12 comments
Assignees
Labels
upstream Third party issue
Milestone

Comments

@andreas-p
Copy link

I've upgraded a working 15.7.25 opnsense installation hosted on Hyper-V 2012R2 to 16.1. After that, a workstation located on the LAN segment didn't NAT to the outside world any more as expected. ICMP did work, but other traffic (http, ssh) didn't reach the target. Disabling checksum offload and hardware vlan didn't solve the problem, suricata is disabled, LAN has full access.
.
Symptoms are quite strange: accessing a remote test server from the firewall does work, tcp packets receive the destination. When the workstation initiates the traffic, I can see via tcpdump on the WAN interface that NAT is performed as expected, the outgoing packet is virtually identical to a SYNC packet initiated from the firewall itself (specifically, the source address is the outgoing interface ip). Still, the packets won't arrive if initiated by the client. Apparently, the packets are dropped after passing the tcpdump tap point.
I re-checked the situation, installing a fresh 15.7.25, everything working fine; cloning it and upgrading to 16.1, bummer. I now can switch back and forth between both versions, switching on and of the symptom.

@fichtner
Copy link
Member

fichtner commented Feb 1, 2016

Can you try the following base/kernel on a 16.1 system?

 # opnsense-update -bkr 791bdab10f3cfbed0b6a62d89d9168fb66d3eafe && /usr/local/etc/rc.reboot

@andreas-p
Copy link
Author

Jup, that apparently patch did the trick. Thanks!

@fichtner
Copy link
Member

fichtner commented Feb 1, 2016

Unfortunately, that's a stock FreeBSD 10-STABLE version. We've been unable to find the cause of this yet, but we are trying to pin this down. Use with care. :)

@andreas-p
Copy link
Author

From your reply, I was wondering what the problem might be with the stock stable kernel, but uname shows me it's 10.3-PRERELEASE, so consider that question retracted ;-)

@fichtner
Copy link
Member

fichtner commented Feb 1, 2016

some patches are missing (nat+traffic shaping, pf match keyword, pptp filter glue) we want to pin down the issue, then merge the single commit responsible into our 16.1 :)

@fichtner fichtner self-assigned this Feb 1, 2016
@fichtner fichtner added the bug Production bug label Feb 1, 2016
@fichtner fichtner added this to the 16.7 milestone Feb 1, 2016
@gitdevmod
Copy link
Contributor

Maybe this is the same issue https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=203630 ?

@fichtner
Copy link
Member

fichtner commented Feb 1, 2016

@gitdevmod thanks, looks promising... providing a new build soon.

@fichtner
Copy link
Member

fichtner commented Feb 1, 2016

How is this one then?

# opnsense-update -bkr 16.1-hyperv && /usr/local/etc/rc.reboot

@andreas-p
Copy link
Author

That's no different from comment 2..

@fichtner
Copy link
Member

fichtner commented Feb 2, 2016

@andreas-p So it works? Just to be clear :)

@andreas-p
Copy link
Author

Yes, that kernel does fix the problem on Hyper-V.

@fichtner
Copy link
Member

fichtner commented Feb 2, 2016

I'll take two "okays" out of three, thanks guys, will be shipped in 16.1.2 on Friday and also try to push FreeBSD to add that to 10.2 errata.

@fichtner fichtner closed this as completed Feb 2, 2016
@fichtner fichtner added upstream Third party issue and removed bug Production bug labels Feb 4, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
upstream Third party issue
Development

No branches or pull requests

3 participants