search for: inernal

...router with two external and one internal interfaces and it doesn''t work as we''d like to. We need it to route all the trafic through one of the external interfaces and to access a few networks through the other. Currently it seems that all the packets with source address from the inernal network are routed correctly. The problem is with the packets that originate from the router. For some reason they are routed through the default interface. Does anybody know why does that happen? # ip rule ls 0: from all lookup local 200: from 192.168.1.0/24 to a.b.c.0/24 lookup 202 201:...

Hi ! I have setup a complete shorewall now with DMZ, and Private zones and masq, rules, port-forwarding etc. worx like expected. BUT I have a wish to use a couple of more public IP''s and relate those to inernal servers on the DMZ zone and i am now so confused about it. I have searched this archive for SNAT port allow Setup: 3 public adresses on the WAN nic. lets call them 80.80.80.80 - 80.80.80.81 - 80.80.80.82 .80 is the default adress now, used for masq etc. Lets asume i setup SNAT on .81 and .82 and...

...the external domain name, e.g. ohprs.org. Here's where I'm confused. If I use ohprs.org as the AD domain and e.g. DC1.ohprs.org is my AD/DC, how does name resolution work with other domain members? For example, webserver.ohprs.org is a current, public FDQN which resolves to 98.102.63.106. Inernally this host's IP within the domain is 192.168.0.3. This host also has an SSL certificate for external access to webpages (https). If I am on domain member "joe" how will accessing host "webserver" resolve? Will it refer to the public IP (98.102.63.106) or the local domain I...

..., e.g. ohprs.org. > > Here's where I'm confused. If I use ohprs.org as the AD domain and e.g. > DC1.ohprs.org is my AD/DC, how does name resolution work with other domain > members? For example, webserver.ohprs.org is a current, public FDQN which > resolves to 98.102.63.106. Inernally this host's IP within the domain is > 192.168.0.3. This host also has an SSL certificate for external access to > webpages (https). > Not surprised you are confused, that section of the wikipage seemed to say it was okay to use your external dns name, it isn't and never has b...

...legacy program written in Fortran. My package has been rejected by CRAN due to this Write statement with the message "As 'Writing R Extensions' warns you against including Fortran I/O, this will not be allowed." The issue is that this Write statement does not involve I/O it is inernally writing an integer to a character which is then placed in an appropriate message (character string) passed to the error handling function recommened in writing R extensions rexit(message). I'm working with a very large legacy program which was developed over 16 years and I am reluctant to re...

Hi Guys This has been discussed a little in the list before so my apologies for sendig it again but I have done what others have done in the list but to no avail. I have configured Asterisk to send the callerID of extension phones as "firstname lastname" and that seems to work well and extensions show calls originating on other extensions in this format. I set the following in

...e's where I'm confused. If I use ohprs.org as the AD domain and e.g. >> DC1.ohprs.org is my AD/DC, how does name resolution work with other >> domain >> members? For example, webserver.ohprs.org is a current, public FDQN >> which >> resolves to 98.102.63.106. Inernally this host's IP within the domain is >> 192.168.0.3. This host also has an SSL certificate for external >> access to >> webpages (https). >> > > Not surprised you are confused, that section of the wikipage seemed to > say it was okay to use your external dns...

Overnight I was running a zfs send | zfs receive (both within the same system / zpool). The system ran out of space, a drive went off line, and the system is degraded. This is a raidz2 array running on FreeBSD 8.1-STABLE #0: Sat Sep 18 23:43:48 EDT 2010. The following logs are also available at http://www.langille.org/tmp/zfs-space.txt <- no line wrapping This is what was running: #