Do you need the whole configuration? On the switch end, we have the relevant VLAN (VLAN 48) with the assigned IP address of 192.168.48.101 and the range of ports (Gi1/0/1 - Gi1/0/8) assigned to that VLAN.
Seems - and acts - like a legitimate setup and works fine, except for this particular instance.
Thanks.
Boris.
On Fri, Jan 23, 2015 at 8:54 PM, Dennis Jacobfeuerborn < dennisml@conversis.de> wrote:
We have lots of servers with a similar setup (i.e. tagged vlans and no ip on eth0) and this works just fine.
What is the actual vlan configuration on your switchport?
Regards, Dennis
On 24.01.2015 01:34, Boris Epstein wrote:
Steve,
Thanks, makes sense.
I just don't see why I have to effectively waste an extra IP address to
get
my connection established.
Boris.
On Fri, Jan 23, 2015 at 7:16 PM, Stephen Harris lists@spuddy.org
wrote:
On Fri, Jan 23, 2015 at 07:10:57PM -0500, Boris Epstein wrote:
This makes two of us. I've done everything as you have described and it simply does not work.
Are you actually seeing VLAN tagged traffic, or is the cisco switch just providing a normal stream?
At work we have hundreds of VLANs, but the servers don't get configured for this; we just configure them as normal; ie eth0. The network infrastructure does the VLAN decoding, the server doesn't have to.
Try configuring the machine as if it was a real LAN and forget about the VLAN.
If that doesn't work then what does 'tcpdump -i eth0' show you?
--
rgds Stephen _______________________________________________ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos