This website uses cookies essential to its operation, for analytics, and for personalized content. By continuing to browse this site, you acknowledge the use of cookies.
For details on cookie usage on our site, read our Privacy Policy
For details on cookie usage on our site, read our Privacy Policy
About AmeriNet-TK
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- LIVEcommunity
- About AmeriNet-TK
09-22-2023
5Posts
2Likes
2Solutions
Sep 22, 2023Last Visited
User
Activity
User
Profile
Latest posts by AmeriNet-TK
| Subject | Views | Posted |
|---|---|---|
| 59601 | 01-24-2020 08:33 AM | |
| 7036 | 01-17-2013 01:29 PM | |
| 7251 | 01-17-2013 12:57 PM | |
| 5335 | 09-11-2012 01:22 PM |
My Liked Posts
| Subject | Likes | Posted |
|---|---|---|
| 1 Like | 01-24-2020 08:33 AM | |
| 1 Like | 01-17-2013 01:29 PM |
User Badges
Community Statistics
| Member Since | 04-12-2010 10:22 AM |
| Date Last Visited | 09-22-2023 10:16 AM |
| Posts | 5 |
| Total Likes Received | 2 |
01-24-2020
08:33 AM
1 Kudo
Had same error- "bind: Cannot assign requested address" on firewall when sourcing ping from ethernet 1/5 (not Panorama). Found that after we had done a load saved config snapshot to restore a config, one of the physical interfaces had the "untagged subinterface" checkbox checked. We undid this checkbox and everything was back to normal. Hope this can help someone else.
... View more
01-17-2013
01:29 PM
1 Kudo
You are welcome. You have VLANs so you can use sub interfaces rather than using a physical interface, you can do PBF to direct traffic from the guest LAN to their ISP, now with version 5.0.1 you can direct traffic recieved on one interface (ISP) to return traffic to that same ISP, before you could not do that. If you have the physical interfaces the dual VR route is fine. Good luck.
... View more
01-17-2013
12:57 PM
Hello, you are essentially correct. There are several ways to do this, but in keeping as close to your proposed solution here is what I would suggest- Create two new zones, untrust-b and trust-b, create an L3 interface for each zone with an IP address (I would use the Sonicwall's LAN and Sonicwall WAN IP). Create new virtual router, put both interfaces in that VR, config default gateway in that VR pointing to same Default gateway as sonicwall had) Create security policy to allow inbound and outbound traffic, create NAT rules, configure DHCP on new trust L3 interface. Move cables from Sonicwall LAN and WAN interfaces to your newly configured PA trust and untrust interfaces, Commit.
... View more
09-11-2012
01:22 PM
Shabeer, Did you ever resolve this? I just ran into the exact same problem with a 2050 running 4.1.7, old polycom vsx7000. Thanks, Tim
... View more
Contact Me
| Online Status |
Offline
|
| Date Last Visited |
09-22-2023
10:16 AM
|
LEGAL NOTICES
Copyright 2007 - 2023 - Palo Alto Networks