- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Windows Server 2003
- >
- ML350G4 + VLAN + VPN reply ping on wrong VLAN
Windows Server 2003
1753587
Members
6611
Online
108796
Solutions
Forums
Categories
Company
Local Language
back
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
back
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Blogs
Information
Community
Resources
Community Language
Language
Forums
Blogs
Topic Options
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2005 07:39 AM
10-11-2005 07:39 AM
ML350G4 + VLAN + VPN reply ping on wrong VLAN
We have enabled VLAN on our ML350. Så we have VLAN 1, VLAN 100 - VLAN 128. VLAN 1 is the default VLAN.
The server is connected to a ProCurve 2524 on port 22. Port 22 is TAGGED on all VLAN.
For internet access there is an InGate 1450 connected with fw 4.3 (VLAN-capabilities) on port 16 whivh is TAGGED member of all VLAN.
VLAN 1 has IP 192.168.1.1, subnet 255.255.255.0 and dg 192.168.1.254.
The other VLAN has IP 192.168.x.1 and subnet 255.255.255.0 and NO dg.
If we ping internal from a client the server respond ok but if we connect to the server with VPN (IPSec handled by Ingate FW) we can ping 192.168.x.254 (dg) and clients on that VLAN but not the server UNLESS we connect to VLAN 1.
Checking the firewall log tells us that traffic comes in on the firewall on IPSec0 and goes out from fw to LAN on eth0.x, the server replies on eth0.1 and the firewall discards the package due to spoofed adress.
Thats why it only works for VLAN1.
So, why does the server respond on VLAN1 when the ping comes in on VLAN x???
The server is connected to a ProCurve 2524 on port 22. Port 22 is TAGGED on all VLAN.
For internet access there is an InGate 1450 connected with fw 4.3 (VLAN-capabilities) on port 16 whivh is TAGGED member of all VLAN.
VLAN 1 has IP 192.168.1.1, subnet 255.255.255.0 and dg 192.168.1.254.
The other VLAN has IP 192.168.x.1 and subnet 255.255.255.0 and NO dg.
If we ping internal from a client the server respond ok but if we connect to the server with VPN (IPSec handled by Ingate FW) we can ping 192.168.x.254 (dg) and clients on that VLAN but not the server UNLESS we connect to VLAN 1.
Checking the firewall log tells us that traffic comes in on the firewall on IPSec0 and goes out from fw to LAN on eth0.x, the server replies on eth0.1 and the firewall discards the package due to spoofed adress.
Thats why it only works for VLAN1.
So, why does the server respond on VLAN1 when the ping comes in on VLAN x???
2 REPLIES 2
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-11-2005 07:25 PM
10-11-2005 07:25 PM
Re: ML350G4 + VLAN + VPN reply ping on wrong VLAN
What is doing the routing between the subnets?
Where there is a will there is a way...
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
10-12-2005 08:39 PM
10-12-2005 08:39 PM
Re: ML350G4 + VLAN + VPN reply ping on wrong VLAN
What need to route?
It works fine locally but not with VPN.
It works fine locally but not with VPN.
The opinions expressed above are the personal opinions of the authors, not of Hewlett Packard Enterprise. By using this site, you accept the Terms of Use and Rules of Participation.
News and Events
Support
© Copyright 2024 Hewlett Packard Enterprise Development LP