Displaying 4 results from an estimated 4 matches for "basiclaly".
Did you mean:
basically
2008 Sep 25
3
[LLVMdev] Generating instruction bundles ?
Hi,
I'm retargetting llvm for a new architecture, basiclaly a target that
has v4f32 registers and a few operations, so it's mostly common stuff.
However, it also has some kind of options on top of the operations,
kinda like VLIW. For example, there is an addition operation, but
there is also a source operand negation bit which you can set. So you
can im...
2005 Jan 22
4
chan_skinny and firmware upgrade
Hello all,
I am trying to upgrade the firmware on my cisco 7910 without using CCM. I was told that
chan skinny is possibly capable of doing that and would like to make
sure.
I have P00405000600 firmware which I have put in version in
skinny.conf. the phone basiclaly stops at verifying load. tcpdump
shows nothing happening apart from small amount of traffic to port
2000 (skinny).
Does anyone have any ideas on how to get the new firmware into the
phone? cisco instructions arent very helpful.
PS> unlike the bigger brother of the phone, this one does not requ...
2003 Apr 02
0
[Bug 72] New: ICMPs sent by REJECT are not getting SNAT'd
...irrelevant]
|
+------------+
| DSL router |
+------------+ = 10.1.1.2
|
| [10.1.1.0/30]
|
+------------------+ eth1 = 10.1.1.1
| Firewall machine |
+------------------+ eth0 = 200.1.1.1
|
| [200.1.1.0/29]
|
[INSIDE]
For right now, my firewall rules are basiclaly nothing - I pass everything
thru the firewall machine.
I soon realised that since I'm using a non-routed address for the "outside"
interface of the firewall, I run into issues trying to initiate any
connection from the fw machine, so I added:
iptables -t nat -A POSTROUTING -o eth1...
2003 Apr 02
0
[Bug 73] New: ICMPs sent by REJECT are not getting SNAT'd
...irrelevant]
|
+------------+
| DSL router |
+------------+ = 10.1.1.2
|
| [10.1.1.0/30]
|
+------------------+ eth1 = 10.1.1.1
| Firewall machine |
+------------------+ eth0 = 200.1.1.1
|
| [200.1.1.0/29]
|
[INSIDE]
For right now, my firewall rules are basiclaly nothing - I pass everything
thru the firewall machine.
I soon realised that since I'm using a non-routed address for the "outside"
interface of the firewall, I run into issues trying to initiate any
connection from the fw machine, so I added:
iptables -t nat -A POSTROUTING -o eth1...