| |
| |
| |
|
Page: 1 2 3 4
Comments:
<0> between those is a bsd gateway (has been there for like 3 years, nothing has changed on it, so it shouldn't be part of the problem
<0> on the 192.168.0.x network we have our servers (sort of like a DMZ
<0> on the 192.168.1.x network we have all our PCs (this is also where the PDC lives)
<0> at the top of the 192.168.0.x network (at 192.168.0.254) we have another router, which connects out to the net for the servers
<0> all the servers in 192.168.0.x have their default gateway set to 192.168.0.254, on 192.168.0.254 I have a static route for all traffic to 192.168.1.x to go to 192.168.0.1
<0> (it forwards it to the internal router which gets it to the right subnet)
<0> this setup worked perfectly for years with a crappy little dlink as the 192.168.0.254 router
<0> we needed a radius enabled vpn endpoint on the serverside, so we replaced the dlink with a pfsense box, so that it can serve this purpose
<0> immediately after replacing it, now windows sharing, and remote desktop traffic from pcs in 192.168.1.x to servers in 192.168.0.x intermittently times out with "The network name is no longer available"
<0> and at the same time traffic from 192.168.0.x machines and servers on 192.168.1.x are having the same problem
<1> if i understand correctly, the new router doesn't sit between the subnets right
<0> but the wierd part is that machines in 192.168.0.x when connecting to other machines within 192.168.0.x (not crossing the router) they experiencing the same problem
<0> killfr0g: correct
<0> it sits between 192.168.0.x and the internet
<0> the second router at 192.168.0.1 and 192.168.1.1 sits between the subnets (that router is unchanged in years)
<1> interesting :p
<0> and because the servers in 192.168.0.x have their default gateway set to go to the router at 192.168.0.254 (so they can get onto the net) I had to setup a static route in 192.168.0.254 to route internal (192.168.x.x) traffic to 192.168.0.1 so that the internal router can handle traffic
<0> which as I said, with the ****ty little dlink router at 192.168.0.254 it worked fine
<0> now that I went up to pfsense, it still works fine, but I get intermittent timeouts, and extreme slowness, but only on smb/cifs traffic and remote desktop, ftp,web, and other traffic is good and fast/stable
<1> right but from subnet to subnet the new router isn't used
<0> not entirely true
<0> traffic going from 192.168.1.x to 192.168.0.x goes through routerA (192.168.0.1)
<0> traffic coming back from 192.168.0.x to 192.168.1.x goes first through routerB (the new one at 192.168.0.254) then goes through routerA
<0> this is because of the default route setup on the servers in the 192.168.0.x subnet
<1> hmm so it must be something with the new router.. i dont know much about pfsense though :/
<0> (sorry I was so... verbose... in my stuff above, but it is a pretty complex setup/problem)
<0> well pfsense is basically a pretty gui on top of pf on freebsd
<1> did you set up the new router to forward on the appropriate ports?
<0> yeah
<0> communication works fine, it is just intermittent
<0> (more precisely I created a firewall rule that as long as traffic both originates and is destined to 192.168.0.0/16 then allow it through no matter what)
<0> combined with the static route, that should allow normal routing
<1> right
<0> the other wird part though that has me, is my IT workstation is plugged into the server subnet (192.168.0.x)
<0> and from my machine browsing shares on the PDC (in 192.168.1.x) has the intermittent/hanging problem
<0> but browsing shares on a server in 192.168.0.x ALSO has the same problem
<0> however for a PC in 192.168.1.x browsing the PDC is perfectly fine, no problems at all, but browsing across to 192.168.0.x has problems
<0> figure that out
<0> lol
<1> hmm do you have the old dlink? perhaps throw it in for a day and see if it still works fine with that. just to make sure that the new router is causing all the trouble
<0> lol no I don't :)
<0> we were deploying a branch office, and rather than buy a new router we sent that router down to them
<0> (it was a $200 dlink, still crappy but worked fine, so didn't want to throw money away)
<0> so it's at the branch office (just arrived there today). the branch office is in jamaica :) and I am in canada, so I can't go get it to test lol
<1> hah nevermind then
<0> (I really wish I was the one deploying the branch office instead of staying up here to troubleshoot this, considering it is friggin freezing up here and snow everywhere, and those bastards are right near the beach in jamaica right now on company time lol)
<0> I just can't think of what is causing it
<0> I know DNS issues can be a problem, but I checked and all servers and all pcs are resolving one another in dns just fine
<1> hang out here till someone with a bit more experience is around, perhaps they've used pf before.. i haven't hehe, most i've used are your average $100 home routers :)
<0> lol fair enough :)
<0> lol
<1> damn jamaica sounds good right now
<1> i'm stuck here studying :(
<0> lol
<1> well i should be studying :p
<0> the sad thing is I am the IT Manager, and they ended up sending down just a couple random employees, because they needed me here more right now...
<0> (the jamaica deployment was supposed to be me, but it got bumped ahead, and I was in the middle of a bunch of crazy stuff up here so I couldn't leave lol)
<1> ****s for you ;)
<2> What is a tree? :)
<3> a carbon based life form
<2> same answer than everyone gave me, you are so funny
<3> and a forest has lots of trees
<2> and if you start a fire in the forest?
Return to
#networking
or
Go to some related
logs:
#AllNiteCafe
#linux
t
gbajt
#chatzone
Valerie Bertaneli
#linuxhelp
oake undernet
#chatzone
#php
|
|