Re: one way network issue
On 10/19/05, Mohan Singh [EMAIL PROTECTED] wrote: On 10/18/05, Mohan Singh [EMAIL PROTECTED] wrote: To answer my own question, I didn't add a gateway for the subnet in question from this machine. Added it and everything is working now! Strange that it could go out into the subnet, but nothing could come in. *shrugs* That's not strange at all. The default gateway for your other subnet was obviously set, so you could get in. You had not set a default gateway for that one, so you could not get out. It just means that packets addressed to a subnet which doesn't match it's own, it doesn't know what to do with it. This won't affect packets coming in. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
one way network issue
I recently upgraded a FreeBSD box from 4.10 to 4.11 (nuke and install method). The settings in /etc are identical to the way it was (I went over it with vim -d to double check). Externally (router/firewall, etc.), nothing has changed. But on the new install of the machine, I cannot ping or access it from a different subnet. There is no firewall enable anywhere, and like I said, externally, nothing has changed in terms of routing or anything like that. What could be the matter? I can get on from a different subnet by ssh'ing into a machine on the same subnet of the upgraded box and then ssh'ing into the same box, but I'd like to figure out what is the problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: one way network issue
At 03:47 PM 10/18/2005, Mohan Singh wrote: I recently upgraded a FreeBSD box from 4.10 to 4.11 (nuke and install method). The settings in /etc are identical to the way it was (I went over it with vim -d to double check). Externally (router/firewall, etc.), nothing has changed. But on the new install of the machine, I cannot ping or access it from a different subnet. There is no firewall enable anywhere, and like I said, externally, nothing has changed in terms of routing or anything like that. What could be the matter? Sounds like it doesn't know what it's default route is. -Glenn I can get on from a different subnet by ssh'ing into a machine on the same subnet of the upgraded box and then ssh'ing into the same box, but I'd like to figure out what is the problem. ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED] ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
Re: one way network issue
On 10/18/05, Mohan Singh [EMAIL PROTECTED] wrote: But on the new install of the machine, I cannot ping or access it from a different subnet. To answer my own question, I didn't add a gateway for the subnet in question from this machine. Added it and everything is working now! Strange that it could go out into the subnet, but nothing could come in. *shrugs* ___ freebsd-questions@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-questions To unsubscribe, send any mail to [EMAIL PROTECTED]
