Linux - NetworkingThis forum is for any issue related to networks or networking.
Routing, network cards, OSI, etc. Anything is fair game.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I have a firewall Ubuntu 10.04 with 3 nic interface (Wan, Dmz, Lan with Vlan tagging 8021q).
I would configure this machine with static routing between Vlan on ethint and ethdmz but I don't figure out how to do this infact I can't ping from Vlan to dmz and viceversa. If I add a static routing on windows machine on vlan "route add -p 172.18.110.0 mask 255.255.255.248 172.18.120.1" I can ping the firewall 172.18.110.1 but I can't ping the server 172.18.110.5 for example.
Now I don't want to apply this routing rules on all windows machine but I want add static routing on firewall so I can ping from Vlan the Dmz zone and viceversa.
If I add a static routing on windows machine on vlan "route add -p 172.18.110.0 mask 255.255.255.248 172.18.120.1" I can ping the firewall 172.18.110.1 but I can't ping the server 172.18.110.5
ROUTING works one way. The above statement is shown in your route table as: 172.18.110.0 * 255.255.255.248 U 0 0 0 ethdmz
What ever machine you have entered this on, will route traffic destined for 172.18.110.0 to 172.18.110.7 via the ethdmz interface. Once it gets there, how does the returning machine know where to send it if ethdmz has a different routing domain?
This is where the NAT comes into play and why we suggested using Iptables to use the NAT table and recommended some really good material on how to configure Iptables.
I have just do it with iptables and nat and it works great!
My problem is that on copying big files from vlan to dmz windows goes in error about "The specified network name is no longer available" and so I would try to routing manually packets instead of natting.
Distribution: CentOS, RHEL, Fedora, Debian, Ubuntu, LinuxMint, Kali Linux, Raspbian
Posts: 166
Rep:
1. do you able to access internet through the router ?
2. Do you able to ping DMZ zone Server from Default VLAN ?
3. What is your gateway of both of the PC's in VLAN and DMZ ?
4. Did you allowed net forwarding ?
5. Do you have iptables rules to accept LAN to DMZ and DMZ to LAN traffic ?
My problem is that on copying big files from vlan to dmz windows goes in error about "The specified network name is no longer available"
My initial reaction is that this doesn't sound like a routing versus NAT error and makes me think that something else is going on. What kind of 'connection' are you using between your Ubuntu and Windows systems? Are you using Samba? What version of windows are you using?
Have you tried to google the error "The specified network name is no longer available"? I put this into google and it appears to be a common problem, with Samba, Windows server 2003, Windows, 7, etc. I did a search through some of the threads this seems to have a lot of varied suggestions with the solution ranging from new drivers to bad switches, and even a mis-configured DHCP.
One other important thing: look in your Windows even viewer. That will give you a lot more information about the cause of the error message!
Last edited by Noway2; 10-13-2010 at 04:22 AM.
Reason: additional question
1. do you able to access internet through the router ?
2. Do you able to ping DMZ zone Server from Default VLAN ?
3. What is your gateway of both of the PC's in VLAN and DMZ ?
4. Did you allowed net forwarding ?
5. Do you have iptables rules to accept LAN to DMZ and DMZ to LAN traffic ?
1) Yes, I can access internet
2) Yes, I can ping Dmz zone from vlan
3) Yes, My gateway is both of the PC's in VLAN and DMZ with 2 nic (one in trunking for VLAN and one for DMZ)
4) Yes, there are rules for masquerading
5) Yes, all ports are open in both ways
My initial reaction is that this doesn't sound like a routing versus NAT error and makes me think that something else is going on. What kind of 'connection' are you using between your Ubuntu and Windows systems? Are you using Samba? What version of windows are you using?
Have you tried to google the error "The specified network name is no longer available"? I put this into google and it appears to be a common problem, with Samba, Windows server 2003, Windows, 7, etc. I did a search through some of the threads this seems to have a lot of varied suggestions with the solution ranging from new drivers to bad switches, and even a mis-configured DHCP.
One other important thing: look in your Windows even viewer. That will give you a lot more information about the cause of the error message!
The connection is a patch cord cat6 between ubuntu (nic Dmz) and Windows server 2003 with active directory.
I have googled a lot but I haven't found a solution to my problem!
I have also try to copy by ftp and transfers works, I have changed switch and the problem permain.
What problem can be with dhcp? It's the only thinks that I don't try!
Can be a problem because I don't have a wins server? I configured only dns with bind and dhcp3 server.
If I recall correctly, the problem that someone experienced with the DHCP was that the leases were getting reset every few minutes and this caused the large(r) file transfer to abort. What error message are you getting in your Windows event logs? This should help point you (us) in the right direction.
I agree that something appears to be resetting and I suspect that this is causing your disconnection. Unfortunately, I am not knowledgeable enough with Windows networking to be able to make a suggestion, which is why I suggested the event logs. Granted, Windows tries to obfuscate all of the under workings, but somewhere there has to be a meaningful error message. By using the patch cable, you have ruled out a lot of potential hardware issues, which leaves configuration settings and protocol incompatibilities.
If you haven't already, perhaps you should post this on a Windows based forum or find an IRC channel for Windows networking as the problem is probably on the Windows side.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.