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

[BUG] Polycube source nat can not upload from internal ip #410

Closed
Polaris0112 opened this issue May 27, 2022 · 1 comment
Closed

[BUG] Polycube source nat can not upload from internal ip #410

Polaris0112 opened this issue May 27, 2022 · 1 comment
Labels
bug Something isn't working

Comments

@Polaris0112
Copy link

Polaris0112 commented May 27, 2022

Describe the bug

I have some internal ips and use one share public ip.
So I need snat for our internal ips to access websites throught that public ip
And it can work with internal ips to access public and download file, but failed with upload files

To Reproduce

Steps to reproduce the behavior:

  1. One Server with a static public ip and have a few internal ips
  2. Update polycube rules like
    polycubectl nat add nat1
    polycubectl attach nat1 eth0
    polycubectl nat1 rule snat append internal-net=10.0.0.0/8 external-ip={public ip}
  3. After step 2, the internal ips can access website and download files from public, but failed with upload
  4. Upload Speedtest show no speed on it. And can not upload file/photo from some online drive website

Expected behavior

Throught SNAT rule can use also with upload

Please tell us about your environment:

  1. OS details: 18.04.6 LTS (Bionic Beaver)
  2. Kernel details: Linux test-20220517 5.17.5 pcn_log cannot be split in multiple lines #1 SMP PREEMPT Thu Apr 28 11:05:12 CST 2022 x86_64 x86_64 x86_64 GNU/Linux
  3. Polycube Version:
    polycubectl:
    version: v0.9.0+ [git: (branch/commit): master/49834b6f]
    polycubed:
    version: v0.9.0+ [git: (branch/commit): master/49834b6f]
  4. Polycube Log: Attach the log from /var/log/polycube/polycubed.log
    [2022-05-27 10:03:51.975] [polycubed] [info] configuration parameters:
    [2022-05-27 10:03:51.975] [polycubed] [info] loglevel: info
    [2022-05-27 10:03:51.975] [polycubed] [info] daemon: true
    [2022-05-27 10:03:51.975] [polycubed] [info] pidfile: /var/run/polycube.pid
    [2022-05-27 10:03:51.975] [polycubed] [info] port: 9000
    [2022-05-27 10:03:51.975] [polycubed] [info] addr: localhost
    [2022-05-27 10:03:51.975] [polycubed] [info] logfile: /var/log/polycube/polycubed.log
    [2022-05-27 10:03:51.975] [polycubed] [info] cubes-dump-file: /etc/polycube/cubes.yaml
    [2022-05-27 10:03:51.975] [polycubed] [info] cubes-dump-clean-init: false
    [2022-05-27 10:03:51.975] [polycubed] [info] cubes-dump-enable: false
    [2022-05-27 10:03:51.975] [polycubed] [info] polycubed starting...
    [2022-05-27 10:03:51.975] [polycubed] [info] version v0.9.0+ [git: (branch/commit): master/49834b6f]
    [2022-05-27 10:03:51.975] [polycubed] [info] running as daemon
    [2022-05-27 10:05:12.927] [Nat] [nat1] [info] Creating Nat instance
    [2022-05-27 10:05:12.927] [Nat] [nat1] [info] Adding rule
    [2022-05-27 10:05:55.725] [Nat] [nat1] [info] Creating RuleSnatEntry instance: 10.0.0.0/8 -> 209.97.171.16
    [2022-05-27 10:08:03.944] [Nat] [nat1] [info] Dropping packet
    [2022-05-27 10:08:03.944] [Nat] [nat1] [info] Dropping packet
    [2022-05-27 10:08:03.944] [Nat] [nat1] [info] Dropping packet
    [2022-05-27 10:08:03.945] [Nat] [nat1] [info] Dropping packet
    [2022-05-27 10:08:03.945] [Nat] [nat1] [info] Dropping packet
    [2022-05-27 10:08:03.945] [Nat] [nat1] [info] Dropping packet
    [2022-05-27 10:08:03.945] [Nat] [nat1] [info] Dropping packet
    [2022-05-27 10:08:03.945] [Nat] [nat1] [info] Dropping packet
    [2022-05-27 10:08:03.945] [Nat] [nat1] [info] Dropping packet
    [2022-05-27 10:08:04.241] [Nat] [nat1] [info] Dropping packet
    [2022-05-27 10:08:04.241] [Nat] [nat1] [info] Dropping packet
    [2022-05-27 10:08:04.509] [Nat] [nat1] [info] Dropping packet

Additional context

Add any other context about the problem here.

@Polaris0112 Polaris0112 added the bug Something isn't working label May 27, 2022
@Polaris0112
Copy link
Author

#406 like this issue, I reinstall the kernel v5.4.x and it can work now.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant